imapd mem exhausted
Patrick Welche
prlw1 at newn.cam.ac.uk
Wed Sep 24 11:33:56 EDT 2003
On Wed, Sep 24, 2003 at 10:58:46AM -0400, Rob Siemborski wrote:
> On Wed, 24 Sep 2003, Scott Adkins wrote:
>
> > 3) The problem was characterized as an mmap() problem on Tru64 because
> > our mailboxes.db file is about 27MB in size. However, we are seeing
> > the sizes jump to 30-32MB in size, and our mailboxes.db file is still
> > only about 27MB in size. *shrugs*
>
> mailboxes.db + cyrus.index and cyrus.cache file for some large mailboxes?
Hmm.. Starting from a totally empty user, not even an inbox in sight, and
using that 1 imapd process which grew to 37Mb to CREATE and APPEND repeatedly,
Oh!
# du -ck . (Inside /var/spool/user/userid)
514 ./Sent/2003/08-Aug
...
38104 .
38104 total
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
19526 cyrus 2 0 35M 37M select 0:10 0.93% 0.93% imapd
(I killed it just after)
Now, why would the total quantity of data written to disk in that session
magically tally with the process' size.. I'd better try again in case this
is coincidence.. That figure obviously includes not only the message
files, but also cyrus.index & cyrus.cache for each mailbox, the biggest
being
-rw------- 1 cyrus mail 409268 Sep 24 11:55 ./Sent/2003/03-Mar/cyrus.cache
which isn't much..
Cheers,
Patrick
More information about the Info-cyrus
mailing list