DragonFly BSD
DragonFly kernel List (threaded) for 2004-06
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: one of recent commits seems to cure memory leak in modlogan (same problem present in freebsd 5.2.1)

To: Toma_ Bor_tnar <tomaz.borstnar@xxxxxxxx>
From: Alexander Leidinger <reject@xxxxxxxxxxxxx>
Date: Tue, 1 Jun 2004 12:26:40 +0200

On Mon, 31 May 2004 20:50:46 +0200
Toma_ Bor_tnar <tomaz.borstnar@xxxxxxxx> wrote:

[posted & mailed, please let us continue off-list]

> > A recent modlogan is more memory friendly, and since it uses expat2 it
> > also depends on changes in expat. Are you sure you haven't noticed some
> > change in modlogan/expat2?
> I use modlogan for some time, but every now and then I use it to process 
> big (historical) files. Since production machines were running FreeBSD I 
> used Dfly test machine which was killing modlogan with "out of memory" 
> (with almost 30 000 000 lines of log). I tried the same on FreeBSD 5.2.1 
> and with same results. Then I recompiled kernel to let apps use up to 
> 768MB of memory and modlogan was able to finish most of logfiles. With 
> one of recent commits these same logfiles take less than 50 megs of RAM 
> when running. I used same 0.8.11 (from same ports system!) on both systems.

Since there are some fixes in the FreeBSD VM too, can you test with a
recent -current too? If not, can you provide a "bzip2 -9" version of
your large logfile?


           I'm available to get hired (preferred in .lu).

http://www.Leidinger.net                       Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]