On Sun, 11 Feb 2001, Chuck Pierce wrote:
> well, the first thing you can do is not keep your logs compressed. By
> having analog uncompressed the log files eats up a TON of memory.
This isn't true. Uncompressing is CPU intensive, but not memory intensive.
And analog's own memory usage is the sa
--Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of The Hermit Hacker
Sent: Sunday, February 11, 2001 9:32 AM
To: [EMAIL PROTECTED]
Subject: [analog-help] Processing large (>1.95g compressed) logs ...
I've got a site that generates ~200Meg of logs per
well, the first thing you can do is not keep your logs compressed. By
having analog uncompressed the log files eats up a TON of memory. Also,
analog is very memory intensive. I would suggest that you check out
http://www.analog.cx/docs/lowmem.html. Especially if you are hitting
swap.
- Chuck
I've got a site that generates ~200Meg of logs per day, and is up to
almost 2gig compressed ... not porn, they supply e-cards for Yahoo and
other sites like that ... if I try and run analog against them, it takes
days, and then, it appears, it crashes, cause no results are generated ...
I'm runn
