Pre-processing NZB and downloading at the same time?
Posted: March 26th, 2014, 12:17 pm
Hi guys,
I was wondering if there is a way to have some threads doing the NZB pre-processing (i.e. checking for availability of the articles) independently of other threads doing the actual downloading? The reason I ask is that pre-processing can take a long time for me (several minutes for a movie), and only starts once that particular item of the queue has been reached. That means that time is wasted on pre-processing before before the actual download starts, and also that you won't be able to tell whether an NZB will actually download before you get to that place in the queue.
I normally only use 2 connections when downloading which is enough to max out my 10mbit connection. If I use more (like 30, for instance) the pre-processing will finish considerably quicker, but my internet connection will become totally flooded, latency will skyrocket and even surfing the web will become an unbearable pain not to mention playing online games that depend on latency which will be impossible.
So my thought was that if 2 threads could be used for downloading, and an additional 28 could be reserved for pre-processing (and if possible running independently so that all items could be processed as soon as they were queued), it would make for a considerably smoother experience overall. I seem to recall one of the older versions performing all of the pre-processing before actually downloading anything (in reality it would check one post at a time and then move it to the bottom of the queue, then start downloading once it reached a post which had already been checked).
Any thoughts on this idea?
Cheers
Symple
I was wondering if there is a way to have some threads doing the NZB pre-processing (i.e. checking for availability of the articles) independently of other threads doing the actual downloading? The reason I ask is that pre-processing can take a long time for me (several minutes for a movie), and only starts once that particular item of the queue has been reached. That means that time is wasted on pre-processing before before the actual download starts, and also that you won't be able to tell whether an NZB will actually download before you get to that place in the queue.
I normally only use 2 connections when downloading which is enough to max out my 10mbit connection. If I use more (like 30, for instance) the pre-processing will finish considerably quicker, but my internet connection will become totally flooded, latency will skyrocket and even surfing the web will become an unbearable pain not to mention playing online games that depend on latency which will be impossible.
So my thought was that if 2 threads could be used for downloading, and an additional 28 could be reserved for pre-processing (and if possible running independently so that all items could be processed as soon as they were queued), it would make for a considerably smoother experience overall. I seem to recall one of the older versions performing all of the pre-processing before actually downloading anything (in reality it would check one post at a time and then move it to the bottom of the queue, then start downloading once it reached a post which had already been checked).
Any thoughts on this idea?
Cheers
Symple