--On Friday, October 19, 2001 12:03 PM -0400 Lawrence Greenfield
<[EMAIL PROTECTED]> wrote:
> Most operating systems don't release memory from a process after
> free() is called, so process sizes only climb---they never drop.
> However, what's far more important is the working set size of each
>
Date: Fri, 19 Oct 2001 12:20:58 -0400
From: Scott Adkins <[EMAIL PROTECTED]>
> I also don't remember whether Tru64 has good mmap() semantics or not.
> Does Cyrus's configure complain about mmap()?
It does. They had problems in earlier releases of Tru64, but we in 5.0+,
mmap()
Date: Fri, 19 Oct 2001 11:03:23 -0400
From: Scott Adkins <[EMAIL PROTECTED]>
Actually, we have made the same obvservation here after upgrading to
2.0.16 from 1.5.14. Many of our imap processes climb up to 14MB in size
(though, I have never seen one bigger than that) and stay there
--On Friday, October 19, 2001 4:08 PM +0200 Jan Moravec <[EMAIL PROTECTED]>
wrote:
>
> On my FreeBSD 4.4 machine running Cyrus imapd 2.0.16 (installed from the
> ports collection), I see that each imapd process eats up around 2500K of
> memory (RES - resident portion of the process) and its tota
Date: Fri, 19 Oct 2001 16:08:09 +0200 (CEST)
From: Jan Moravec <[EMAIL PROTECTED]>
On my FreeBSD 4.4 machine running Cyrus imapd 2.0.16 (installed from the
ports collection), I see that each imapd process eats up around 2500K of
memory (RES - resident portion of the process) and i
