From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] awk: hex numbers? (and leak(1))
Date: Fri, 22 Sep 2006 00:41:22 +0200 [thread overview]
Message-ID: <200609212241.k8LMfMp09871@demeter.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Wed, 20 Sep 2006 22:29:15 +0200." <82c890d00609201329u640b15f9xc6782c1c216528c7@mail.gmail.com>
thanks all who helped.
I fiddled a bit more with my leak
(updated my sources contrib).
it helped me get more insight in
programs memory usage.
as a sidenote: one thing i learned is that
using lib9p with filetrees when having
'lots' of files 'lots' of strings get
stored (partly (largely?) duplicated)
due to the estrdup9p in createfile
(for uid, guid, muid, and name).
(I think for 25000 files this 'cost' 2 Mb or so)
would sharing those strings be an option?
(or just make things more complicated?)
(in this case I rewrote my code to no longer
use filetrees - as suggested in 9p(2) -
my file hierarchy was very regular indeed)
Axel.
next prev parent reply other threads:[~2006-09-21 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 10:33 Axel Belinfante
2006-09-20 13:34 ` Gabriel Diaz
2006-09-20 13:58 ` Axel Belinfante
2006-09-20 20:20 ` Russ Cox
2006-09-20 20:29 ` Gabriel Diaz
2006-09-21 22:41 ` Axel Belinfante [this message]
2006-09-21 23:02 ` Russ Cox
2006-09-22 9:57 ` Axel Belinfante
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=200609212241.k8LMfMp09871@demeter.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).