9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] aux/acidleak pool pathology
Date: Thu, 21 May 2009 22:13:28 -0400	[thread overview]
Message-ID: <266b188ce4dfc166c788bd97d218a8d6@quanstro.net> (raw)
In-Reply-To: <dd6fe68a0905211149u1cd2ffe8t4d25bbe78173a5d0@mail.gmail.com>

!/bin/upas/marshal -s 'Re: [9fans] aux/acidleak pool pathology' -R /mail/fs/mbox/272 9fans@9fans.net
> >> if upas/fs is allocating arbitrarily large buffers,
> >> then its allocation behavior is broken too.
> >
> > there are a fixed number of large buffers.  up to 15 messages
> > and mdir uses dirreadall so it can qsort.  the qsort is easy enough
> > to eliminate, but it's more difficult to bound message buffers.
>
> i never said fixing it was easy.  ;-)

from the embarrassing bugs department....

going to all that trouble might not be worth it at
~10000 message mailboxes.  it turns out that a bug i
introduced earlier in the week in imap4d was causing all
mailboxes to remain open.  so the 400mb process had grown
from a 50mb process due to a few esoteric leaks and having
1.5gb in 203 mailboxes open all at once.  it's suprising that
upas/fs did as well as it did.

combining the tricks from the week shrinks this process to
a slightly more manageable 12mb.

unfortunately, i think this will just encourage users to
aim for 100000 messages in their inbox.

☺

- erik



  reply	other threads:[~2009-05-22  2:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 16:06 erik quanstrom
2009-05-21 16:35 ` Russ Cox
2009-05-21 16:54   ` erik quanstrom
2009-05-21 16:57     ` erik quanstrom
2009-05-21 17:19     ` Russ Cox
2009-05-21 18:04       ` erik quanstrom
2009-05-21 18:49         ` Russ Cox
2009-05-22  2:13           ` erik quanstrom [this message]
2009-05-22 16:52             ` Joel C. Salomon
2009-05-22 17:13               ` erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=266b188ce4dfc166c788bd97d218a8d6@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).