Thanks for your reply, the past days I have been mainly working on increasing the speed of the script, so it has become faster . Your version already contains a speed improvement compared to the other because it only creates the necessary sockets, instead of all for each news server.Crowley wrote:No errors, but the check seems to be slower than before.
Or it might be my main news server, the speed have gone randomly up and down the last few days.
It will soon include 80% faster analysis of the nzb, ignoring a check for servers outside the retention limit as specified in NZBget, a max number of articles that will be checked (usefull for files of like 20 GB +).
Note that each socket creation has a time-out of 2 sec, so when 1 of your connections fail, it add an additional 2 sec per failed connection. Checking about 5% (what i use) takes for me like 2.5 sec in total for a file of 1.5 Gb, without any issues on the news-server end. There might be a news server specific optimum for the specified number of connections available in the NZBget settings, as the script uses those to build the sockets for the script. More sockets take more time to create, more sockets cost less time to check the headers , so it is a bit of trade. Note that my general experience with NZBget and downloading, is that more sockets don't always speed up the download, also there is an optimum.