Perform check on next download.

[yakaman]

Hi,

Since the 'Check before download' doesn't use a lot of bandwidth, it would seem to be a good idea to launch it automatically on the next task of the queue (while the item before that is downloading).

Thanks for this great piece of software btw

[shypike]

Since pre-download check uses the same server connections as the actual download (it has to),
there would be no real gain.
The result would be that your download job would become slower.

[yakaman]

Ah sorry, I got misled by the fact that the interface showed a slow download speed while checking the job.
NVM then

[shypike]

The factor here is that it takes time for the server to determine whether an article exists.
So the limiting factor here is not bandwidth but latency.
If you have servers with a high number of allowed connections, not all of which are needed to
reach the maximum bandwidth, then we could do more in parallel.
However this is just too complex for a feature we're not actively promoting anymore.

The better alternative is "abort when job cannot be completed".
It can cost you some more bandwidth, but nowadays almost complete jobs are rare.
The biggest issue are jobs that have been removed altogether.

BTW: the next release will also use the "abort" principle for pre-download checks.
Meaning that SABnzbd will no longer check all articles when it becomes clear that this is useless.

[yakaman]

Thanks, I disabled the check and used "abort when job cannot be completed".

[rmh400]

Yes but if you were to use a single connection for checking until all downloads in the queue have been checked, then you could open that connection back up to the downloads just an idea an I would love to see this implemented even as a switch that a user could toggle

[shypike]

That would be even slower.
Besides it would effectively mean a second queue. That's just not worth the investment.