caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Malcolm Matalka <mmatalka@gmail.com>
To: "Török Edwin" <edwin+ml-ocaml@etorok.net>
Cc: Kasper Janssens <Kasper.Janssens@hgst.com>,  caml-list@inria.fr
Subject: Re: [Caml-list] Profiling ocaml with lwt
Date: Thu, 10 Mar 2016 07:55:56 +0000	[thread overview]
Message-ID: <86pov2n4vn.fsf@gmail.com> (raw)
In-Reply-To: <56E12538.6040003@etorok.net> (=?utf-8?B?IlTDtnLDtms=?= Edwin"'s message of "Thu, 10 Mar 2016 09:41:44 +0200")

Török Edwin <edwin+ml-ocaml@etorok.net> writes:

> On 03/09/2016 11:57, Kasper Janssens wrote:
>> Den 9 mar 2016 9:54 fm skrev "Kasper Janssens" <Kasper.Janssens@hgst.com <mailto:Kasper.Janssens@hgst.com>>:
>> 
>>     Hello,
>> 
>> 
>>     I’m trying to profile an ocaml application that has a performance degradation of about 20 %, with quite some code changes between both
>> versions. I tried attaching perf and gprof to it, but to no real avail. Sure, there are slight differences in the running time of
>> functions in the gprof result, but nothing whatsoever that seems to explain that kind of delay. Perf doesn’t seem to indicate a problem
>> neither.
>> 
>> 
>>     The thing is, I think it’s a delay in one of the servers that the application communicates with.
>
> Is that communication done over a TCP/UDP socket?
> You could use wireshark and see if you spot anything (e.g. too many SSL handshakes -> application would benefit from persistent connections, etc.)
>
> Depending on the complexity of your application you may try to use a branch of Lwt that reports more tracing information,
> although this would likely require manual annotations to produce useful output:
> http://roscidus.com/blog/blog/2014/10/27/visualising-an-asynchronous-monad/
>
> I usually just wrap+log calls and use strace though, as already
> mentioned in this thread.

And if you're on FreeBSD or OS X or Solaris you can use dtrace.

>
> Best regards,
> -- 
> Edwin Török | Co-founder and Lead Developer
>
> Skylable open-source object storage: reliable, fast, secure
> http://www.skylable.com

  reply	other threads:[~2016-03-10  7:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09  8:54 Kasper Janssens
2016-03-09  9:49 ` Malcolm Matalka
2016-03-09  9:57   ` Kasper Janssens
2016-03-10  7:41     ` Török Edwin
2016-03-10  7:55       ` Malcolm Matalka [this message]
2016-03-09 18:13 ` Adrien Nader
     [not found] <1911376179.6660816.1457526862329.JavaMail.yahoo.ref@mail.yahoo.com>
2016-03-09 12:34 ` tools

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=86pov2n4vn.fsf@gmail.com \
    --to=mmatalka@gmail.com \
    --cc=Kasper.Janssens@hgst.com \
    --cc=caml-list@inria.fr \
    --cc=edwin+ml-ocaml@etorok.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).