Feed problem
Brennon Church
ctsbac at cts.com
Tue Oct 17 16:53:05 UTC 2000
On Tue, Oct 17, 2000 at 12:48:20AM +0200, Anonymous Coward wrote:
>
> On 47 Sep 19100, Brennon Church wrote:
>
> > indicate to me that the local system (my machine) isn't able to pick up the
> > data fast enough. I'm thinking this would have to do with one of three
> > things, processor, ram, or hard disk.
>
> Turn on the innd timer. You'll see where things are being maxxed
> out even when the processor shows idleness.
Thanks. I just turned it on.
>
>
> > There are two drives in the system, one 4gig boot drive, and a 50gig spool
> > drive. The system is transit only, so retention isn't an issue. Watching
>
> Where's your history? Recent INN k0deZ are murder on the history,
> and seem to trash the spool more than it should too.
The history (and logs) are kept on the 1st drive, while the spool is on the
second drive.
>
> I've just barely kept up with a binariez feed on a single slow 9GB spool
> drive with stock k0deZ, but having dug into the k0deZ, I wouldn't
> recommend it unless you do some serious C surgery. History was on a
> separate drive, though. At least, I think this was with the INN 2.4
> family. I Could Be Wrong.
>
>
> > On a side note... What is about the average size for a full news feed
> > nowadays. I've managed to get up to 152Gigs in a day, but I'm usually
> > hovering around 140 or so.
>
> Our binariez machine is maxxxed out for most of the morning, but we've
> regularly seen ~160+GB recently. We have run out of CPU on that box
> while innd still has small amounts of idle time, so we should have better
> numbers after replacing it and upgrading its spool.
>
Thanks for the help.
-- Brennon Church
More information about the inn-workers
mailing list