From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: [9fans] leak/umem question
Date: Fri, 20 Jun 2008 16:00:34 -0400 [thread overview]
Message-ID: <d0bf6bc6b96d8ccada0be8ea90cf5885@coraid.com> (raw)
i have a process (modified upas/fs) that has quite a large amount
of allocation churn. on startup, its memory footprint looks like this:
quanstro 6305 0:00 0:00 6264K Pread 8.out
umem reports this
73023 4673712 henter+0x8e
2435 702224 newmessage+0x16
2434 405776 badd+0x24
900 60000 strdup+0x20
868 94176 parseunix+0x27
4 384 newfid+0x5a
3 91200 erealloc+0x25
1 480 newmbox+0x15
1 224 dirfstat+0x29
1 32 mdirmbox+0x7d
after churning through the whole mail box, the image now looks like
this
quanstro 6305 0:17 0:10 32468K Pread 8.out
leak says no blocks are leaked and umem gives an identical report to
the first:
73023 4673712 henter+0x8e
2435 702224 newmessage+0x16
2434 405776 badd+0x24
900 60000 strdup+0x20
868 94176 parseunix+0x27
4 384 newfid+0x5a
3 91200 erealloc+0x25
1 480 newmbox+0x15
1 224 dirfstat+0x29
1 32 mdirmbox+0x7d
if i use leak -b, the image generated is all light/dark blue with just a
few white pixels at the beginning and end. there is no apparent free space.
the image is at www.quanstro.net / leak.png.
where is the "missing" 28mb going to?
- erik
next reply other threads:[~2008-06-20 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 20:00 erik quanstrom [this message]
2008-06-22 0:57 ` Russ Cox
2008-06-22 12:43 ` 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=d0bf6bc6b96d8ccada0be8ea90cf5885@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/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).