From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] leak/umem question
Date: Sun, 22 Jun 2008 08:43:59 -0400 [thread overview]
Message-ID: <f2be55a63b54b09bd688edc96db0f144@quanstro.net> (raw)
In-Reply-To: <20080622005550.161191E8C22@holo.morphisms.net>
> You didn't tell us much about your memory usage patterns.
> Do you allocate large lots of large objects and then
> free them? That would explain the larger footprint
> and the identical umem. Do you agree with the second
> allocation profile?
i should have included this information.
the way i have things set up, the overhead is about ~6mb
and the additional cache goal is 512k. the cache is very
small at this point to stress the cache. although the
goal is 1/2mb, whole messages need to be cached and
the largest message is 11mb.
i found a bug late last night that prevented the cache
from being as aggressively managed as i intended. the
image now gets up to "only" 19mb.
(on the other hand, before caching it took 150mb,
a size ~proportional to the mb size, not the largest message.)
> It is easily possible that aux/acidleak's bitmap code
> is not quite right, and that the 28MB is in fact free.
>
> Try running
>
> pid=12345
> echo 'leakdump({'$pid'})' | acid -lpool -lleak $pid |
> grep '^(block|free) ' >/tmp/a
>
> and then you can paw through /tmp/a to see what
> is reported for the last 28MB of address space.
; grep free /tmp/a | sumit
13291456
; grep block /tmp/a | sumit
6329424
grand total is 19161k.
the image total is
quanstro 11483 0:18 0:01 19464K Pread 8.out
so 19161k + 296 (executable size) = 19457. this seems
reasonable given the 11mb message.
many thanks for the hint, russ.
- erik
prev parent reply other threads:[~2008-06-22 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 20:00 erik quanstrom
2008-06-22 0:57 ` Russ Cox
2008-06-22 12:43 ` erik quanstrom [this message]
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=f2be55a63b54b09bd688edc96db0f144@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).