SABnzbd Forums

I think there is a problem with pre-check. it seems that it uses just one thread.

Here are my test results:

AW, 20 connections, EU server, 4.5 Gb release(100% healthy)

1) nzb completion checker:

HEAD: ~28 seconds.
STAT: ~28 seconds.

2) SABnzbd Version: 0.7.17 :

4 minutes 3 seconds

That's a huge difference.

I recall sabnzbd checker was way faster than this. Now it is only 1KB speed max,but it used to be 15-20 KB back then.

Could it be so that pre-check uses just one thread now?

Pre-check hasn't changed.
However, we no longer recommend using it.
Instead use the "Abort if download cannot be completed".
Much more effective.

If it hasn't changed why it has become so ineffective as if only running one thread?

I have to say although "Abort if download cannot be completed" is a nice feature, having ability to see exactly how many articles are missing could come in handy too.

semel wrote:If it hasn't changed why it has become so ineffective as if only running one thread?

It hasn't changed. The execution is just like a regular download.
It can be your Usenet provider too. SABnzbd uses a specific code to check for presence of an article.
Possibly something in the server setup has changed, that specific code isn't used often.
I see no difference when I test it.