From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Memory use analysis
Date: Mon, 19 Aug 2013 16:09:54 +0200 [thread overview]
Message-ID: <87eh9p22ml.fsf@gnu.org> (raw)
In-Reply-To: 877gfpxxf7.fsf@markwitmer.com
Hi,
mark@markwitmer.com skribis:
> Is there some kind of tool or method for getting Guile to enumerate what
> objects in the heap are considered "live" by the GC? I guess the
> conservative GC Guile uses doesn't explicitly keep track of every
> object, but I wouldn't mind just being able to see what stuff in the
> heap it *thinks* it needs to keep, and then query what kind of SCM
> objects they represent.
Not exactly what you’re asking for, but very useful: the (statprof)
module comes with ‘gcprof’, which samples the stack each time the GC
runs (info "(guile) Statprof"). It allows you to see which part of the
programs are allocating the most, roughly.
HTH,
Ludo’.
next prev parent reply other threads:[~2013-08-19 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 18:23 Memory use analysis mark
2013-08-19 14:09 ` Ludovic Courtès [this message]
2013-09-07 9:46 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eh9p22ml.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).