From: ygrek <ygrekheretix@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] What is triggering a lot of GC work?
Date: Mon, 25 Feb 2013 18:32:22 +0800 [thread overview]
Message-ID: <20130225183222.8f7eda023079e8ddf31e3f5f@gmail.com> (raw)
In-Reply-To: <CAM3Ki75oGj2Y+55mHzGA5YKZ0bcxAENmMf6qrfM52PecRU82XQ@mail.gmail.com>
On Mon, 25 Feb 2013 08:02:54 +0000
Mark Shinwell <mshinwell@janestreet.com> wrote:
> On 25 February 2013 02:08, Francois Berenger <berenger@riken.jp> wrote:
> > Is there a way to profile a program in order
> > to know which places in the source code
> > trigger a lot of garbage collection work?
>
> Well, as of last week, there is!
>
> I'm working on a compiler and runtime patch which allows the
> identification, without excessive overhead, of every location (source
> file name / line number) which causes a minor or major heap allocation
> together with the number of words allocated at that point.
>
> There should be something available within the next couple of weeks.
> It only works on native code compiled for x86-64 machines at present.
> Currently it has only been tested on Linux---although I expect it to
> work on other Unix-like platforms with little or no modification.
Meanwhile you can use poor man's allocation profiler :
- http://ygrek.org.ua/p/code/pmpa
- https://sympa-roc.inria.fr/wws/arc/caml-list/2011-08/msg00050.html
--
ygrek
http://ygrek.org.ua
next prev parent reply other threads:[~2013-02-25 10:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 2:08 Francois Berenger
2013-02-25 8:02 ` Mark Shinwell
2013-02-25 10:32 ` ygrek [this message]
2013-02-26 3:46 ` Francois Berenger
2013-02-26 4:29 ` ygrek
2013-02-25 13:31 ` AW: " Gerd Stolpmann
2013-02-25 15:45 ` Alain Frisch
2013-02-25 16:26 ` Gerd Stolpmann
2013-02-25 16:32 ` Gabriel Scherer
2013-02-25 16:52 ` [Caml-list] OCaml benchmarks Török Edwin
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=20130225183222.8f7eda023079e8ddf31e3f5f@gmail.com \
--to=ygrekheretix@gmail.com \
--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