Since I started playing around with virtualization (currently running 3 physical servers with about 4-5 Virtual Servers on each of them), I am having an issue with the (Virtual) machine (assigned 4GB Ram, 4-core CPU) running Windows Server 2016 Standard) I use for NZBGet (version 21.0, also tried the testing build but the issue is the same). I'm not sure if the issue I'll be describing also happened prior to the virtualization with the bare metal installation (which used NZBGet 19.0, also on Windows Server 2016 Standard), but still...
The bottleneck in this case isn't the hardware, as RAM usage hardly goes above 2GB and CPU-usage is within the 25-50% usage range on average.
So here goes...
I notice terrible download speeds (<2 megabyte per second, on a 200mbit line) when NZBGet is downloading certain NZB's. This seems to be the case ONLY when the NZB consists of several .partXXXX.rar files.
When monitoring the queue, I see it hopping from "Downloading" to "Queued" every other second or so.
It appears as if NZBGet is trying to extract the (part.)rar-file as soon as it's downloaded.
I do not believe this to be a bug in NZBGet, but it working as expected due to some setting somewhere.
Unfortunately, the only setting I could find that might have any influence on this is the "directunpack" feature. I disabled this and restarted NZBGet, yet the issue remains the same.
What I do believe that could solve the issue (where older formats of archiving were used) is that NZBGet downloads the ENTIRE NZB (thus all files + par-files) BEFORE attempting ANY repair/extract actions.
Does anyone of you guys have a clue on how to achieve this?
Thanks in advance
Worth mentioning: I have already tried disabling the FlushQueue option (as explained here
), but this didn't solve the issue.