Page 1 of 1

50% CPU usage with speed limiter on

PostPosted: Sat Mar 26, 2011 6:47 pm
by slushee
Windows 7 64 home premium with Service Pack 1 installed
AMD Phenom II X2 550
Newsbin Build 876
3.0Mbps DSL
Trying out the Version 6 beta for the first time

If I activate the speed limiter and set the slider to 1.6Mbps, the Windows Task Manager shows the Newsbinpro64.exe process to be using around 50% of the CPU. It dips down a bit momentarily, but mostly stays right up at around 50%. CPU usage goes immediately down to 1-2% if I turn off the speed limiter. This is with the computer not doing much of anything else, other than having Firefox open.

Never experienced this with Version 5.

Re: 50% CPU usage with speed limiter on

PostPosted: Sat Mar 26, 2011 9:13 pm
by Quade
It's a different limiter so, I'm not really surprised it acts differently. I'll try to think of some way to test this.

Re: 50% CPU usage with speed limiter on

PostPosted: Tue Apr 12, 2011 2:30 am
by slushee
Still happening in Beta 9.

Re: 50% CPU usage with speed limiter on

PostPosted: Tue Apr 12, 2011 5:30 am
by richy99
slushee wrote:Still happening in Beta 9.


probably due to the limiter not being worked on between those builds

probably needs more input from other users to see if they are getting
whats your setup?

Re: 50% CPU usage with speed limiter on

PostPosted: Tue Apr 12, 2011 8:18 am
by DThor
Wondering if it's in the realm of possibility that the limiter is colliding with an antivirus or firewall?

DT

Re: 50% CPU usage with speed limiter on

PostPosted: Tue Apr 12, 2011 8:24 am
by Quade
I think Dex said he see's this. It's probably just the way the current limiter works. Not saying it's going to stay that way but, I haven't had a chance to look at it.

Re: 50% CPU usage with speed limiter on

PostPosted: Fri Apr 29, 2011 7:52 pm
by Arkman
I also get 50% cpu usage when speed limiter is on. No antivirus running.
V6 beta 11.

Re: 50% CPU usage with speed limiter on

PostPosted: Sat Apr 30, 2011 7:46 am
by DThor
Yes, I believe that's been noticed by others, too. To my knowledge, I don't think Quade has had a chance to look at this part of the code yet. Something will be mentioned in the release notes when he has.

DT