0.3.1 uses 100% CPU also if nothing is downloaded/verified/unpacked

[mcka]

Hi!

I have a performance problem with SABnzbd+ 0.3.1. I'm running it on a DiskStation (DS207 PPC, 128MB), and it often uses 100% CPU, also if I don't download anything (downloads paused), and nothing else is done (extracting, verifying...). I'm currently waiting for 10 minutes until it shuts down after I clicked the button. I use Plush template. Most other things like ftp, ssh become so slow because of SABnzbd. What is it calculating all the time?
There is allways one process or thread allways using 30-70% CPU,  most of the others need 3-10% and some of them 0%. Since it uses so much CPU, I don't think it has to do with little swap/smallRAM.

And I have a lot more processes/threads than number of conncection, is this OK?

best regards
mcka

[shypike]

Do you use a "black-hole" dir (dirscan dir)?
If so, what is its scan rate?
Do you have many non-NZB files in this "black-hole" directory?

What was the behaviour of previous SABnzbd versions?

There are about 6 threads running.

[neilt0]

FYI, I changed my directory scan from 1 second to 30 seconds on my NAS. Not sure how this has impacted performance, but I figure the less CPU time spent on this, the better.

[mcka]

Do you use a "black-hole" dir (dirscan dir)?
If so, what is its scan rate?

10 seconds.

Do you have many non-NZB files in this "black-hole" directory?

No, only nzb, and the directory is empty when nzb is loaded.

What was the behaviour of previous SABnzbd versions?

I'll test that. AFAIR 0.3.0 worked more efficient. Not tested anything older yet.

There are about 6 threads running.

I have 10 connections and exactly 21 threads.

Another strange thing is, that deleting of several files in the temporary "incomplete directory" failed. But not all, only about 5% of the files. But perhaps this had somethig to do with timeouts...

After finishing my downloads, SABnzbd behaves a lot better. If I don't open the web interface, it does not need any CPU time (0%). Once I start the webinteface (Plush) in one Browser, SABnzbd threads create a more or less constant CPU usage of about 20% on the system. No connections are established at the moment, top still shows 21 threads. Shutdown works in 1-2 seconds now, not several minutes as before. When I restart, at once 21 threads are created. Changing to smpl templates results in a lower cpu usage when the browser is opened, but still constant 10%. Only the Default Template is completely diffrent. Also on queue and history pages it uses 0% CPU between refreshs. Really strange. Perhaps an issue with Ajax?

[shypike]

Plush and smpl do constant requests (depending on their refresh rate setting).
"Default" does not (except when setting the optional refresh for the queue screen).

Sounds like there may be some corruption in the cache dir.
Have you tried starting with --clean ?

There were very few changes between 0.3.0 and 0.3.1 in behaviour.
Main difference is in the dirscan code, supporting nzb.gz and skipping irrelevant files.

The Plush and smpl template sets did have major changes.

I haven't kept track of the amount of threads.
SAbnzbd itself has about 6 internal tasks. Temporary threads are used to startup connections.
And then there is CherryPy web-framework which has it's own set of threads.

I'll have a look at it, but 21 does not seem outrageous.