caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Pascal Brisset <brisset@recherche.enac.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Memory Profiler
Date: Mon, 12 Mar 2001 11:59:48 +0100	[thread overview]
Message-ID: <20010312115948.A29585@pauillac.inria.fr> (raw)
In-Reply-To: <E14aLDF-0001j0-00@sepia.recherche.enac.fr>; from brisset@recherche.enac.fr on Tue, Mar 06, 2001 at 06:25:29PM +0100

> I am looking for a memory profiler à la gprof for the native OCaml compiler.
> I would be interested by the memory consumption (let's say in bytes) of
> each function, something similar to gprof results but for memory. On your
> shelf ?

We do not have any such tools currently, but I agreee we need a memory
profiler!

There are two ways to go about it.  One is to count allocations, as
you propose.  This might be feasible by inserting counters (like
ocamlprof does) at allocation sites.

However, a point can be made that this is not what you want to know:
short-lived allocations consume time, but do not consume memory.  So,
the other direction os to profile live heap data (as a function of
time) and be able to trace it back to its allocation sites.  This is a
lot harder to do, and we currently do not know how to do this.
However, there has been interesting work in this direction for Haskell
(the work of Colin Runciman and colleagues) and also for Scheme
(Manuel Serrano's memory debugger for the Bigloo system).

- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr.  Archives: http://caml.inria.fr


      reply	other threads:[~2001-03-12 11:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-06 17:25 Pascal Brisset
2001-03-12 10:59 ` Xavier Leroy [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=20010312115948.A29585@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=brisset@recherche.enac.fr \
    --cc=caml-list@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).