SABnzbd Forums

Version: 0.5.6
OS: Win 7 Ult, Windows Home Server
Install-type: Windows Installer
Skin (if applicable): Plush
Firewall Software:None
Are you using IPV6? no
Is the issue reproducible? yes


I've been using SABNZBD for around a year now, and recently I've noticed that as a file finishes downloading my speed will start to drop off pretty steeply, reducing from 5mb/s down to 0.01kb/s (over time, not an instant drop. Like it's decelerating) and pushing the completed download time off the scale for that file. Then it'll sit there for about 5 minutes before jumping to the next file in the list and accelerating the speed again. It's almost as though the program is locking up the downloads while it unpacks and checks the just-finished file.

This is a new behaviour, and I've tried a clean install which hasn't fixed it. The strange thing is it's happening on 3 different machines in exactly the same way, and it doesn't seem to be tied to my connection because it happens on a laptop that I use at multiple sites with different providers.

Any ideas?

I have one idea.  I know some ISP's have a cap speed on the individual connections (verizon does it here in MA).  So lets say you have 8 connections, which allows your full bandwidth speed to be used.  As the files start to complete, and you have lets say only 3 files left, the three connections at their cap speed is lower than your total speed.  For example if I only have two connections running, its about 1/3 slower than if I have say 8 connections.  Just an idea! Hope you figure it out.

My guess is that you have the setting "Config->Switches->Only Get Articles for Top of Queue" set to "on".
The result is that at the end of the job, not all server threads
will request new articles, because there aren't any for the job.
This results in a temporary dip in speed.

It's OK to set the option off, unless you have a memory-constrained system.

Or it might be just a batch of bad articles which are hard/slow to download from your news server. Maybe even badly uploaded, assuming you did all three tests on different pc's with the same news server and the same file(s)

Well if it was a bad batch, it would constantly be slow, not just at the end.

Thanks for the input so far guys. I've changed the settings suggested and when I get home I'll check in on it and see how it's doing.