From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Kenneth Adam Miller <kennethadammiller@gmail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Automated Instrumentation for Profiling
Date: Wed, 14 Oct 2015 10:11:57 +0200 [thread overview]
Message-ID: <CAPFanBFidU1POG=1-T-K13OwL5m8C+KWTtvk0Y-3vaWJ2VAtEg@mail.gmail.com> (raw)
In-Reply-To: <CAK7rcp8C_escNin+gC1ye18Yq39oNNiTrvF81RUQ3TjkOO93sA@mail.gmail.com>
Have you considered porting ocamlviz to ppx?
On Wed, Oct 14, 2015 at 9:44 AM, Kenneth Adam Miller
<kennethadammiller@gmail.com> wrote:
> 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.
next prev parent reply other threads:[~2015-10-14 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 7:44 Kenneth Adam Miller
2015-10-14 7:59 ` Kenneth Adam Miller
2015-10-14 8:04 ` Francois Berenger
2015-10-14 8:11 ` Gabriel Scherer [this message]
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='CAPFanBFidU1POG=1-T-K13OwL5m8C+KWTtvk0Y-3vaWJ2VAtEg@mail.gmail.com' \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=kennethadammiller@gmail.com \
/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