Page 1 of 1
2.2.1 uses much more cpu than 2.2.0
Posted: September 2nd, 2017, 3:48 am
by Puzzled
I'm using two usenet servers, one is IPv4 and one is IPv6. I get a total of about 1 MB/s, limited by the usenet servers and not my connection. Without bandwidth limiting the CPU usage is about 30% on a 4 core CPU in Windows 10 64 bit (1 core is running 100%), and about the same when I run SABnzbd in a virtual Debian machine. If I put the bandwidth limit at 20% less than the top speed (0.8 MB/s) the CPU usage falls to about 10% in both Windows and Debian. After downgrading to 2.2.0 the CPU usage is about 3% without bandwidth limit in Windows. I haven't tried downgrading in Debian.
Re: 2.2.1 uses much more cpu than 2.2.0
Posted: September 2nd, 2017, 4:09 am
by safihre
It's a bit more complicated:
When you do not set a speedlimit, SABnzbd will indeed use too much CPU because it constantly checks if more articles are available.
Therefore we introduced a throttle mechanism in 1.1.0, but this killed download-speed on some VM's or VPNs. Because of that, during the first ~15 seconds of the downloading we measure the speed, we enable the throttling (reducing CPU usage) and then check if the speed stays the same. If the speed starts to fluctuate, we disable the throttle and CPU usage will be higher but at least on those VM's and VPN's it will work fine. We introduced this in some 1.1.x version.
So if the speed fluctuates during the first 15 seconds, we play it safe and CPU usage will be higher.
If you always want low CPU usage, just set your download-limit to 95% of your connection speed
Re: 2.2.1 uses much more cpu than 2.2.0
Posted: September 2nd, 2017, 4:45 am
by Puzzled
Thanks for your reply, but that doesn't explain why 2.2.1 uses 10x more CPU when I'm not setting a bandwidth limit manually. It does so permanently and every time, not just for a few seconds.
Re: 2.2.1 uses much more cpu than 2.2.0
Posted: September 2nd, 2017, 5:36 am
by safihre
I can't explain 10x..
Re: 2.2.1 uses much more cpu than 2.2.0
Posted: September 4th, 2017, 2:11 pm
by Temujin
I'm seeing a marked decreases in performance as well;r especially in my browser since the latest upgrade. Lag across my tabs in chrome even before the quickpar repair or extraction process begins which did not occur before the upgrade. No settings changed in quite some time other than the upgrade.
I can try setting that throttle down to 95 as you mentioned although not sure if that will resolve. Will advise.
Re: 2.2.1 uses much more cpu than 2.2.0
Posted: September 4th, 2017, 2:18 pm
by safihre
2.3.0Alpha1 should resolve this hopefully, let me know if it doesn't.
Re: 2.2.1 uses much more cpu than 2.2.0
Posted: September 4th, 2017, 2:26 pm
by Temujin
Oh great news, thanks for the suggestion - will grab that later today or tomorrow and let you know.
Re: 2.2.1 uses much more cpu than 2.2.0
Posted: September 5th, 2017, 4:36 pm
by Puzzled
I just installed 2.3.0 Alpha 2, and the CPU usage is back to being neglible. Thanks. I tried installing 2.2.1 first just to make sure and it used 25%+ on the same file, so the new version definitely fixed it for me. I have multiple servers but only one was active on the file I was testing.
Re: 2.2.1 uses much more cpu than 2.2.0
Posted: September 6th, 2017, 12:01 am
by safihre
Good
Re: 2.2.1 uses much more cpu than 2.2.0
Posted: September 10th, 2017, 10:37 am
by Temujin
Installed Alpha 2 today and tested with a small 1gb download, seems better - will advise again after a larger download to confirm issue is either better or resolved.
Thanks!
EDIT: Confirmed after grabbing larger and multiple files, performance seems to be increased and not seeing lag in browser while large downloads or file extracts occur.
Thanks again