newsbin.com

So I start up Newsbin and my cpu usage immediately goes to 50% (on a dual core system, Athlon 64 X2).
Within 20 seconds there are 15000 IO reads and writes.

If I watch it in taskmgr it occasionally drops down to 10% usage and the hard drive sounds like it has activity but then Newsbin runs right
back up to 50%.

I have no tabs open and nothing in my download list.

Is there some background activity going on in Newsbin? Is there some log I can turn on to see what?
I let it run for a couple of hours assuming this was the case but it just keeps going at 50%.

If so, the activity may be background to Newsbin but Windows shows it at NORMAL priority and it is interfering with the rest of the system performance.

Of course my interpretation could be totally wrong still all I see is Newsbin doing nothing and taking 50% of my cpu power to do it.

How much to you have queued up for download? If nothing, you might want to try deleting the downloads.db3 file. This will wipe the download, wish and failed lists.

If you look down at the status bar near the "Cache" section, do you see a number in parens "(XX)" if yes and it's greater than zero, then Newsbin is importing header data into the database. It'll do that until it's done.

Thanks,
I deleted downloads.db3 before I posted. No help.
My cache says "300/300 (187)". I took 4 minutes to go from 188 to 187. Is it really going to take 12 hours to clear this?
Is that normal?

Until the value in brackets goes to zero then Newsbin is busy processing already downloaded headers into the database. The number in brackets represents the number of .gz files containing headers that are on the hard disk waiting to be processed.

I do appreciate the responses.

It took 5 hours to clear the backlog. Is this new behavior from 6.42?

Newsbin can download headers far faster than they can be inserted into the database so, they backlog and get imported at quickly as your PC permits. Even my machine will backlog when the headers are downloading at 600 Mbps from Astra. I don't believe it's new behavior though. You might want to try 6.50 and see if it works faster.