Speed up failed articles
Posted: 19 Nov 2017, 11:07
What about let NZBGet ask for a STAT msg just before asking for ARTICLE / BODY (dont know what NZBget uses to get the actual article)? If the STAT responds as a failure, skip the ARTICLE / BODY request.
the STAT request is very very fast, and if that one returns a 430 instead of the 223, the article does not need to be requested. This because when articles don't exist, NZBGet seems to be rather slow in noticing that each article is gone. I guess thats because of the BODY request?
Downside, not all servers do respond correct to STAT, so if its worth the effort, it should be made a server specific option.
(You could also use it to check if the PAR articles will actually be there (not if they are intact of course), before downloading the RARs, so the maximum failure % can be adjusted to reduce download volume.
the STAT request is very very fast, and if that one returns a 430 instead of the 223, the article does not need to be requested. This because when articles don't exist, NZBGet seems to be rather slow in noticing that each article is gone. I guess thats because of the BODY request?
Downside, not all servers do respond correct to STAT, so if its worth the effort, it should be made a server specific option.
(You could also use it to check if the PAR articles will actually be there (not if they are intact of course), before downloading the RARs, so the maximum failure % can be adjusted to reduce download volume.