sab unresponsive when fetching a remote nzb

[merriweather]

Hi

I find that when sab is fetching an nzb from a remote address (via newznab's sab integration or sickbeard, for example), it becomes extremely unresponsive. If there are any downloads in progress they slow right down, almost to a stop, and while the nzb is being fetched, most third party apps (sickbeard, sabconnect) are unable to reach it. The web UI is barely useable and just shows "trying to fetch NZB from ...." for the nzb in question. This can often result in an NZB being downloaded a couple of times if SickBeard deems that it was unsuccessful the first time. Eventually it queues up all the nzbs and starts operating again, but it generally takes a few minutes per nzb.

This is in 0.7.11 running on Ubuntu 13.04, but I've actually had this problem for a long time, over multiple versions of Ubuntu and multiple versions of Sab.


Any ideas? Would love to get this solved.

[shypike]

Are these NZB very large?
Is it a slow link?
Is the same NZB coming froma local source faster to load?

[merriweather]

- nzbs files are standard size (200KB-ish), the content would be between 500mb to 10gb
- if i just grab the nzb myself from the same computer, it takes about a second
- instant.

but the "fetching" process for some reason slows everything to a halt.

[shypike]

Weird.
Processing of the NZB takes CPU time at the expense of downloading.
But that happens after the file has been completely read.
The only other thing I can imagine is that the file is uploaded in very small pieces.
All that is going on inside the third-party web server that lives inside SABnzbd.
We're doing a major upgrade of that server with SABnzbd 0.8.0,
so maybe that will solve things.

[merriweather]

strange, i've had the problem for so long now i assumed it must've been something common, it was only chatting with some mates the other day that i realised i'm the only that seems to have it...