From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Mark Shinwell <mark@three-tuns.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Allocation profiling for x86-64 native code
Date: Fri, 13 Sep 2013 18:52:10 +0200 [thread overview]
Message-ID: <1379091130.2471.12.camel@e130> (raw)
In-Reply-To: <20130913154834.GA6566@three-tuns.net>
[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]
Am Freitag, den 13.09.2013, 16:48 +0100 schrieb Mark Shinwell:
> Large OCaml programs can experience performance degradation due to high
> garbage collection loads (or possibly due to it being Friday 13th).
> Understanding the memory usage of such programs can also be difficult.
>
> To this end, I am pleased to release a version of OCaml 4.01 that
> contains functionality for the memory profiling of native code programs,
> for the x86-64 architecture. Currently it is only fully working on Linux
> platforms, but there should be a version for Mac OS X in the near future,
> and the BSDs.
> ...
> The runtime system for this compiler contains instrumentation that can
> produce a global analysis showing the total number of words allocated
> on the OCaml heaps by source location. This works not only for blocks
> allocated in OCaml code but also in C stubs. Further, values are
> instrumented---without space overhead---in order to be able to determine
> from a snapshot of the heap which value was allocated where; and also
> to provide a runtime API that can be queried from the instrumented
> program itself.
A dumb question: how do you do the value instrumentation? Without space
overhead? There is not much information in the value itself... do you
track value relocations?
Gerd
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
My OCaml site: http://www.camlcity.org
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
------------------------------------------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-09-13 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 15:48 Mark Shinwell
2013-09-13 16:52 ` Gerd Stolpmann [this message]
2013-09-16 8:00 ` Mark Shinwell
2013-09-14 22:10 ` Jacques-Henri Jourdan
2013-09-16 8:42 ` Mark Shinwell
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=1379091130.2471.12.camel@e130 \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=mark@three-tuns.net \
/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).