From: Malcolm Matalka <mmatalka@gmail.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: caml users <caml-list@inria.fr>,
Damien Doligez <damien.doligez@inria.fr>
Subject: Re: [Caml-list] Measuring GC latencies for OCaml program
Date: Tue, 31 May 2016 05:39:15 +0000 [thread overview]
Message-ID: <86a8j6rdks.fsf@gmail.com> (raw)
In-Reply-To: <CAPFanBGLcibjYFLYqvzdFjM31ZVL43msYougACCT6WxGJxxU9A@mail.gmail.com> (Gabriel Scherer's message of "Mon, 30 May 2016 15:48:29 -0400")
This post was a great read! I can say, at least, that I am looking
forward to this instrumentation being easier to use in the future. I'm
planning on writing some low-latency programs in Ocaml and being able to
measure these things would be great.
next prev parent reply other threads:[~2016-05-31 5:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 19:48 Gabriel Scherer
2016-05-31 1:13 ` Yaron Minsky
2016-05-31 5:39 ` Malcolm Matalka [this message]
2016-06-10 20:35 ` Jon Harrop
2016-06-10 21:34 ` Stanislav Artemkin
2016-06-10 23:14 ` Yaron Minsky
2016-06-11 8:53 ` Jon Harrop
2016-09-14 2:51 ` pratikfegade
2016-09-14 8:38 ` Gabriel Scherer
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=86a8j6rdks.fsf@gmail.com \
--to=mmatalka@gmail.com \
--cc=caml-list@inria.fr \
--cc=damien.doligez@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;
as well as URLs for NNTP newsgroup(s).