![]() ![]() I agree that this should take precedence over any other NZB. If I understand you correctly, the main concern here is that you intend for the top priority NZB to get all of the available bandwidth so that it finishes as soon as possible. If there is significant support, I am willing to contribute the code to make it happen and submit a pull request on GitHub. ![]() ![]() The alternative solution (multiple instances of NZBGet) is cumbersome, feels wrong at a philosophical level and seemingly proves out the need for such a feature. NZBGet has the potential to lead the market in this respect by adding support for the concurrent download of multiple NZBs. While we cannot do much to influence how Usenet providers store their binaries, the remainder of unused bandwidth could be put towards the completion of other binaries on other, similarly slow storage tiers as consolation. This problem will continue to be exacerbated for perhaps the next 5-10 years due to the confluence of four factors: increasing binary sizes, increasing binary retention, increasing internet bandwidth, and HDD price per GB being lower than SSD. This behavior causes old binaries to download very slowly relative to the available bandwidth (15MB/sec connection). The nature of rotational disk is that its capacity scales exponentially in relation to the time to store and retrieve files. Usenet providers move old binaries (>1000 days) to "cold" storage tiers, which are typically high-capacity, rotational disks. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |