Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Kenneth Adam Miller <kennethadammiller@gmail.com>
To: caml users <caml-list@inria.fr>
Subject: [Caml-list] Automated Instrumentation for Profiling
Date: Wed, 14 Oct 2015 03:44:11 -0400	[thread overview]
Message-ID: <CAK7rcp8C_escNin+gC1ye18Yq39oNNiTrvF81RUQ3TjkOO93sA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]

So, I'm looking to do some performance profiling of some libraries and
tools. I would like some tools that are more language facilitated than an
alternative of using something like oprofile because while oprofile is
good, you can only guess at what is consuming the most time in your actual
ocaml source because all the function names have been lost by that time.

I found ocamlviz, and that seems pretty good, but I'm looking for something
else because we plan to move away from using camlp4 toward ppx. Introducing
this will mean an additional hurdle to overcome once the transition is
complete in terms of customizing the build chain twice.

In any case, I guess what I'd really like to know is:

1) How good are the ocamlcp and ocamloptp tools and how would you get a
vanilla oasis/ocamlbuild combo to easily start using them instead?

2) Are there any ppx based profiling tools out there? I need both memory
and time profiling to be done. OCamlviz was great because it had a graph-I
don't necessarily need a dedicated gui, but some way to visualize the data
would be very helpful.

[-- Attachment #2: Type: text/html, Size: 1220 bytes --]

             reply	other threads:[~2015-10-14  7:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14  7:44 Kenneth Adam Miller [this message]
2015-10-14  7:59 ` Kenneth Adam Miller
2015-10-14  8:04   ` Francois Berenger
2015-10-14  8:11 ` Gabriel Scherer
2015-10-14  8:25   ` Kenneth Adam Miller
2015-10-14  8:33     ` Kenneth Adam Miller

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=CAK7rcp8C_escNin+gC1ye18Yq39oNNiTrvF81RUQ3TjkOO93sA@mail.gmail.com \
    --to=kennethadammiller@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