SABnzbd Forums

Do you have a article cache set in Config->General and if so how large?

shypike wrote:Do you have a article cache set in Config->General and if so how large?

It is set to 128.

It should be 128M or bigger.
Just "128" is 128 bytes, which is essentially 0.

128M. Still no difference.

Just guessing here.
Does it help to set a speed limit in SABnzbd?
It's counter-intuitive, but it will influence timing.
I cannot really think of any explanation why the SSD would make any difference.
Re-install SABnzbd and reconfigure it?
(After erasing ~/LIbrary/Application Support/SABnzbd).
Did you install from scratch or did you copy the disk content?

The SSL did it. Turned it off, and now all is well. I guess my provider has some issues with the ports or something.

Interesting.
Usenet providers often offer multiple ports per protocol, so maybe you can try SSL with different ports?
It also suggests that your ISP is using a very crude form of traffic control...

They had several port-options when not using SSL. Only three with SSL. Only two of them were not already in use. Both with the same slow speeds. Im guessing my ISP is throttling what they can't see, which seems weird.

Bumping my problem and original posters problem.

Setting a transfer speed had no effect on the overall transmission rate. Only "fix" thus far, is restarting sabnzbd until it transfers un-throttled.

Just wanting it more isn't going to solve the issue.
I cannot reproduce this in any way, so I cannot get any closer to a solution.
What happens of you don't start SABnzbd automatically, but manually after startup?

shypike wrote: What happens of you don't start SABnzbd automatically, but manually after startup?

I always start manually and have the problem.

Btw the problem seems to have gone since changing to 0.7.2. So it's only in .3 and .4

perstranger wrote:
I always start manually and have the problem.

Btw the problem seems to have gone since changing to 0.7.2. So it's only in .3 and .4

This problem is about slow speed just after startup and that this is fixed with a restart of SABnzbd.
Does the same happen when you start SABnzbd manually soon after the system has started?
Is it fixed after a restart of SABnzbd?
Is it always slow? In the latter case, it's not the same problem.
Which OSX are you using? Are you using the right SABnzbd build for your OSX version?

One possible explanation could be that the latest SABnzbd versions are built a bit different.
At least the Mountain Lion build is different from previous ones.

Much like perstranger, I get no difference starting manually or using init.d scripts.

The problem is like limiting of the transfer speed is going on. Restarting sabnzbd through the web gui will work, but sometimes it requires 1-4 restarts before un-throttling the speed. As I'm running on a dedicated server, I restart the system very infrequently. After restarting sabnzbd, and getting no throttling, it will start limiting transfer rates after a period of inactivity. It usually throttles at 2.5 MB/s, for whatever reason.

I'm using sabnzbd 0.7.4 on Ubuntu Linux 12.04 and perstranger is using Windows 7 - 64 bit.

Which Usenet provider are you using?

shypike wrote: Does the same happen when you start SABnzbd manually soon after the system has started? --YES--
Is it fixed after a restart of SABnzbd? --YES--
Is it always slow? --NO--
Which OSX are you using? --I'm on windows 7, yes I am installing the right build--

My provider is Newshosting.