Quade wrote:What do you see in the "Cache" line in the status bar? A number in parens represents number of records waiting to be imported. If you hammer away at header downloads and don't let that number go to zero, you'll never get all the headers fed into the database. The issue is that headers download much faster than they can be imported so, Newsbin imports them in the background.
If the number in parens never goes down then it suggests and import is stuck.
The cache numbers drop about 100 to 200 per minute. I see the "New Records" counts for the groups going up. Very slow considering the cache status shows "Cache: 92/100 (107653)"
I've only been on version 6.42 for a few days, but I don't think your problem is with version 6.42 because I just downloaded the same group from the same server, and on the download tab headers were coming in at the rate of about a million a minute. The "new records" count seems like a less reliable measure, I would guess because maybe the new records are different sizes? But it was at least 1500 a minute.Traveler2530 wrote:The cache numbers drop about 100 to 200 per minute. I see the "New Records" counts for the groups going up. Very slow considering the cache status shows "Cache: 92/100 (107653)"
How can this be sped up?
My cache status showed 90/100 during the download, though sometimes there was a (1) and very rarely a (2) after it, so I have no idea how you get (107653)? I never saw it go above (2). I built that computer in 2006 which is pretty ancient by now I suppose, so hopefully you have a newer computer. I do, but I haven't used it for Newsbin yet since the old one still works so well.
Maybe Astra is better than supernews at delivering headers then?Quade wrote:It's mostly a function of your download speed. I get header downloads in the 400-500 Mbps range from Astra ..
Thanks for the tip, I didn't know I could do that. I got an error when I did it but it seems to be working anyway.Quade wrote: Typically, if you have a slow header server, you can update them all at once
I think the newer versions of Newsbin are choking on fast downloads of large groups. These header problems began happening ONLY when I updated to the more efficient download/decompress/store in 6.4x?? versions a few months ago. Is this related to a new storage and/downloading compression routine?
Quade wrote:I think the newer versions of Newsbin are choking on fast downloads of large groups. These header problems began happening ONLY when I updated to the more efficient download/decompress/store in 6.4x?? versions a few months ago. Is this related to a new storage and/downloading compression routine?
Not really enough data to know.
In 6.42:
-snip-
If you want to trouble-shoot this. Try one group. Download all headers, watch the import line. And when they all import, load the group and see what you can see.
Later today for my final try with 6.42, I'll disconnect ALL HDDs containing anything to do with Newsbin(except the user profile directory on c:\). This is easy to do because I have the entire Newsbin application, .nbi, spool, downloads etc... on the e:\ drive. Next, I'll install a dust-collecting 150GB VRaptor as e:\, then do a complete new install of Newsbin 6.42 to the e:\ drive. Next, I'll download ONLY teevee headers from Supernews.
Quade wrote:Later today for my final try with 6.42, I'll disconnect ALL HDDs containing anything to do with Newsbin(except the user profile directory on c:\). This is easy to do because I have the entire Newsbin application, .nbi, spool, downloads etc... on the e:\ drive. Next, I'll install a dust-collecting 150GB VRaptor as e:\, then do a complete new install of Newsbin 6.42 to the e:\ drive. Next, I'll download ONLY teevee headers from Supernews.
Most of the time trouble-shooting like this fails when people can't do things in discrete steps. Click click clickity click is what I call it. When people can't just sit back and watch what's going on without messing with the process. I don't think you need to do anything other than what I suggested above. You can watch the process, look in the teevee folder for instance but, I'd just let it run and see what happens.
The only thing you should probably check before "Download All" is what your "Storage Age" is set to. If it's too short, Newsbin will simply delete the headers you're downloading till you hit the download age range. I'd set it to 2000 before the "Download all". If you have numbers in parens in the status bar (next to cache), don't start till they're gone. Either that or wipe spool_v6 before you start.
Wiping spool_v6 directory is not an option. It will take several weeks to rebuild the thousands of binary groups on it. I have already tried deleting the teevee directory within spool_v6 and all references to it in newsbin.nbi and then re-downloaded the entire 485+ million headers several times this week. Using 6.42, always the same problem! Doing either a display(last few days) or searching yield zero headers! This is even though the teevee directory shows over 5 GBs of storage.
Return to V6 Technical Support
Users browsing this forum: Google [Bot] and 3 guests