Speed drops substantially after a few minutes...

[wapkaplet]

So I'm downloading a bunch of stuff, and it's been humming along fine since Friday at 1200KB/s. However, sometime over the night or early in the morning, something happened, because when I checked it the speed was only 70KB/s.

I paused and resumed the queue, and full speed returned, but after a few minutes (two, or maybe three), it was back to 70KB/s. Rebooting the machine did not resolve the problem.

I'm running a test now using another NZB client, and I'm not seeing similar behavior. Speed there is rock solid.

Are there log files that I need to clear out? Should I wipe the download history? Can't figure out what's going on...

[wapkaplet]

Rogers, in Canada. That was my first thought, but were that the case I'd expect to see speed drops no matter which client I'm using. It only happens with SABnzbd though.

[wapkaplet]

Also, I'm sure that it's not an ISP issue, because what SABnzbd does is drop to about 25KB/s per connection. If I add more connections, I can up the dropped speed.

Typically I use 3 connections to the server, which drops to around 70-75KB/s. If I use 20 connections, when the speed drops it goes to around 500KB/s. Can't imagine why that would be the case if it was something the isp was doing.

Also, for reference sake I should mention I'm running SABnzbd under OSX Leopard.

[wapkaplet]

Interestingly, this issue seems to have progressed. Now once the speed drop occurs, each connection maxes out at 12KB/s, half of what it used to.

Is there somewhere that SABnzbd hides files other that the configurable folders and the .sabnzbd directory? I feel like I'm not doing a complete wipe when I remove and reinstall the program.

[shypike]

All files are in ~/.sabnzbd, the most interesting one is the sub-folder cache.
I cannot explain the speed drop, never seen it this way.

[joopster]

I've got exactly the same problem. Only my speed drops down to 25kb/s per connection. I'll reinstall sabnzbd and see what happens.

[wapkaplet]

Shortly after my last post, I started seeing the same behavior in other clients, and on other machines. This, to me, rules out SABnzbd as the source of the problem. My apologies for not posting sooner, but I wound up out of town and without network access.

In the intervening time, my ISP and NNTP billing periods have rolled over, and now the problem is gone. Because of this I think it must have been some sort of throttling issue.

However, I do not believe that it was ISP throttling. I say this for two reasons. First, I only saw the speed drop on newsgroup downloads. It never happened on anything else. Second, the throttling, as discussed, was per connection. I could still up my speed considerably by simply adding more connections. It seems to me (and I may be wrong) that if my ISP was going to throttle me, it would be an overriding throttle on my total speed.

Because of this, I think it was my newsgroup provider, which is Newsdemon. I had wanted to borrow a friend's newsgroup account to test with. Were my theory correct, I would've been able to download at full speed on that account. Unfortunately I ran out of time before heading out of town, and now the problem has stopped.

Hey joopster, out of curiosity, who's your newsgroup service provider? Is it Newsdemon?

[icetear]

I have exactly the same problem.
My ISP is Unitymedia in Germany (Cable) - but I am using newsdemon as well.

[mollydog]

Try disabling the SPI Firewall in your router.

[rAf]

Or maybe this thread is relevant : http://forums.sabnzbd.org/http://forums ... 690#p18690

[nzbcrook]

I have this problem as well. Have anyone found a verified solution?

[minimeh]

ISPs may throttle on a specific port access for an account. I ran into that with Comcast. All of a sudden, dl speeds started to be a nice round (and low) number. When I changed to access with a different port, suddenly speeds were back up to, well, speed.

Another tip I've heard but haven't verified is change to your newsgroup server's encrypted port. The theory is that your ISP can't profile the traffic and evaluate that you are doing something they deem at least low priority. But I don't know.

Try changing either your port that you access with or your ISP. Ultimately changing ISP was the best solution for me.