by RayMark » Wed Dec 18, 2019 7:58 am
Yes, I have disabled download during unrar. Still, significant backlog occurs when downloading to an external usb drive. But then, there is always enough free space.
If I download to an internal sata drive, there is no significant backlog, but sometimes I ran out of free space.
A disadvantage - I need to move the downloaded files to an external usb drive anyway.
I guess, it would be faster to use less download threads to reduce the download speed, and thus, to reduce the backlog, and to download directly to an external usb drive after all.
Both the internal and external drives I use are 4 TB drives. I don't even consider downloading to a tiny solid state drive.
Another thing - a speed limiter. Not exactly a pause, but a semi-pause.
I get consistently download speeds over 500 Mbps. Sometimes over 600 Mbps, approaching 700 Mbps. For example, I just saw 673 Mbps. Never noticed over 700, but I am not looking at the speed indicator all the time. Maybe Newsbin is able to record and update the peak value?
Anyway, so I wish to have a speed limiter button - useful for managing backlogs. There is one, but it does not allow to set the limit at hundreds of megabits, unfortunately. For example, at 100 Mbps, 200 Mbps, 300 Mbps, 400 Mbps, 500 Mbps.
I guess, I can experiment with the number of threads, but it is not a one button solution, and experimenting is actually required. Besides, I am using 5 different servers simultaneously.
A speed limiter would be much more convenient. If there is a way to implement one for such a speed range.
And when I asked to implement another, more complete pause, a pause button or a stop button to stop all the activity, I did not mean to stop an unrar that already began.
And perhaps not to stop the repair that already began - if it is done by launching an external repair tool. Just not to begin any new repairs or unrars, or decodings from the Chunks.
I am speaking about the scenario where there is a backlog in the download list. A backlog of already downloaded posts. The current pause does not pause working on that backlog.
So two-level pause would be helpful:
Level 1 = pause (as it is currently) - to pause downloading only, useful for reducing the backlog.
Level 2 = stop - to pause everything (except the unrar (or perhaps the repair) that is already in progress) - not to reduce the backlog, but to stop using cpu and the hard drive - when they are needed for other time-critical things outside NewsBin.