caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Francois Berenger <berenger@riken.jp>
To: caml-list@inria.fr
Subject: [Caml-list] What is triggering a lot of GC work?
Date: Mon, 25 Feb 2013 11:08:14 +0900	[thread overview]
Message-ID: <512AC78E.7070908@riken.jp> (raw)

Hello,

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?

I've seen some profiling traces of OCaml programs
of mine, sometimes the trace is very flat,
and the obvious things are only GC-related.

I think it may mean some performance-critical part
is written in a functional style and may benefit
from some more imperative style.

Regards,
F.

             reply	other threads:[~2013-02-25  2:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25  2:08 Francois Berenger [this message]
2013-02-25  8:02 ` Mark Shinwell
2013-02-25 10:32   ` ygrek
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=512AC78E.7070908@riken.jp \
    --to=berenger@riken.jp \
    --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).