From: Pietro Abate <Pietro.Abate@pps.jussieu.fr>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Tracking memory usage: GC output not same order as unix top command
Date: Mon, 30 Aug 2010 16:12:56 +0200 [thread overview]
Message-ID: <20100830141256.GA23765@uranium.pps.jussieu.fr> (raw)
In-Reply-To: <4C7B7D4E.4020500@inescporto.pt>
On Mon, Aug 30, 2010 at 10:43:42AM +0100, Hugo Ferreira wrote:
> I have a problem trying to identify where my algorithm consumes
> so much memory. I have created a set of functions (see end of message)
> that uses the GC module to obtain the memory used in the heap and print
> that out to determine where memory is being consumed.
have you tried ocamlviz ?
http://ocamlviz.forge.ocamlcore.org/
--
----
http://en.wikipedia.org/wiki/Posting_style
next prev parent reply other threads:[~2010-08-30 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 9:43 Hugo Ferreira
2010-08-30 10:02 ` [Caml-list] " Richard Jones
2010-08-30 10:06 ` Richard Jones
2010-08-30 10:33 ` Hugo Ferreira
2010-08-30 13:53 ` Richard Jones
2010-08-30 14:12 ` Pietro Abate [this message]
2010-08-30 14:17 ` Hugo Ferreira
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=20100830141256.GA23765@uranium.pps.jussieu.fr \
--to=pietro.abate@pps.jussieu.fr \
--cc=caml-list@yquem.inria.fr \
/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).