Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Kenneth Adam Miller <kennethadammiller@gmail.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Automated Instrumentation for Profiling
Date: Wed, 14 Oct 2015 04:25:24 -0400	[thread overview]
Message-ID: <CAK7rcp-m17Jm9YgCwXTh_25nF4cd9Qkj7v_foMf=PBHwRf=DKA@mail.gmail.com> (raw)
In-Reply-To: <CAPFanBFidU1POG=1-T-K13OwL5m8C+KWTtvk0Y-3vaWJ2VAtEg@mail.gmail.com>

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

That sounds like it would definitely be a good benefit to the community and
I'd be really happy to do it. I know that ppx is the successor to camlp4,
and I have a mind to teach myself the sort of magic where I can annotate a
type with some code generating function because I appreciate the power.

But right now, my extra curricular work is just ridiculously over loaded.
In my free time I'm teaching myself Coq, compiler construction with llvm,
taking a coursera course working on a shingled disassembler, working on an
ocamljava backend for ctypes and a ocaml link to CZMQ. I love what I do -
coding and learning all day long - but I have human limits, and I just
don't think I would be able to pick it up for probably 6-8 months. Possibly
something else will come along before then, whether that be even more
compelling challenges or that ocamlviz is seconded by something better.

So, I really honestly would, but I don't think I can. :(

On Wed, Oct 14, 2015 at 4:11 AM, Gabriel Scherer <gabriel.scherer@gmail.com>
wrote:

> 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.
>

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

  reply	other threads:[~2015-10-14  8:25 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
2015-10-14  8:25   ` Kenneth Adam Miller [this message]
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='CAK7rcp-m17Jm9YgCwXTh_25nF4cd9Qkj7v_foMf=PBHwRf=DKA@mail.gmail.com' \
    --to=kennethadammiller@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=gabriel.scherer@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