Hi all.
Im having some performance issues when using Sabnzbd 0.6.
I have a 100mb connection but have been unable to get stable transfers anywhere near the maximum speed.
Sabnzbd fluctuates between 11MB/s and 5MB/s giving an average of around 7MB/s.
I have run through the setup guide and allocated a 2GB article cache (the machine running Sabnzbd is a Phenom X4 3Ghz with 8GB RAM and a WD500AAKS drive dedicated to it on WHS 2011)but this made no difference.
I have tested with Newsleecher and this maxes out my connection, downloading at around 10.5 and 11MB/s. I am using Supernews with 15 connections.
Frustrated I downloaded an old 0.5 version of Sab and lo and behold this also maxes out my connection.
Does anyone have any idea what changed between 0.5 and 0.6 that might be causing this? Disk time and CPU usage rarely go above 45%.
Thanks
Spiky downloads using .06
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Spiky downloads using .06
There are no obvious causes.
For most people nothing much has changed in the performance, for some it has.
The only true difference is that the disk-based article cache is now
stored in each job's incomplete folder.
However, that makes little difference when you have an ample memory cache for articles, like you have.
Did you measure with an independent program or SABnzbd's own meter?
What kind of pattern do you see in the speed?
For most people nothing much has changed in the performance, for some it has.
The only true difference is that the disk-based article cache is now
stored in each job's incomplete folder.
However, that makes little difference when you have an ample memory cache for articles, like you have.
Did you measure with an independent program or SABnzbd's own meter?
What kind of pattern do you see in the speed?