Giganews is, indeed, in the habit of speed-limiting very old files. But this was something from a few days ago.hugbug wrote:Some (older) nzbs may be slow on provider side. Have you tried different nzbs including recent ones?
How many news servers do you have configured and how many connections for each? Please make tests with one connection, with 2, 8, 16 and post results.
Newsbin pro ran on Windows, of course. Sabnzbd on the same Synology machine.hugbug wrote:When you mean SAB and newsbin they run not on the same computer where nzbget? If not - can you test with nzbget on that same computer?
I was starting to smell a rat when the connection kept getting slower and slower. Then I remembered I had my (newly installed) DSM 6 LAN configured to use Jumbo Frames (with an MTU of 2,000). Guess that started to cause a slow network congestion of sorts. Either that, or simply because I restarted the network services (I'll find out later, I reckon).hugbug wrote:It's weird that the number of connections doesn't change a thing.
Can you check cpu usage via top to ensure there is plenty of free cpu power. Maybe some other process eats cpu.
Do you use QoS on your router?
Yes, it is. But even nzbget, when it started up, briefly ran at full speed. So I probably tested sabnzbd too shortly. For now the slowdown seems to have subsided, though.hugbug wrote:Still strange why SAB could download much faster on the same system at the same time.
Users browsing this forum: Google [Bot] and 61 guests