caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Kasper Janssens <Kasper.Janssens@hgst.com>
To: Malcolm Matalka <mmatalka@gmail.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Profiling ocaml with lwt
Date: Wed, 9 Mar 2016 09:57:37 +0000	[thread overview]
Message-ID: <A8D4A12D-D366-4391-B2A8-B9CEBE8D350D@HGST.com> (raw)
In-Reply-To: <CAKziXDXhpg5ftsGXe5gg1xfHXRrr6cMdkWLDjy9sFqNYJ6BNZA@mail.gmail.com>

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

Yes, considered that, but the thing is, there are quite q few functions that would need to be wrapped, on two slightly different code bases. It doesn’t seem very feasible but it might be what I’ll have to resort to.
Other than that, isn’t that an error prone approach when lwt swaps to another thread in the mean time? Don’t you run the risk of timing not just your call but also everything that is done in between (e.g. Having lwt swapping in another thread in the mean time, won’t that show in the timing as well?)?

Kasper

From: Malcolm Matalka <mmatalka@gmail.com<mailto:mmatalka@gmail.com>>
Date: Wednesday 9 March 2016 at 10:49
To: Kasper <Kasper.Janssens@hgst.com<mailto:Kasper.Janssens@hgst.com>>
Cc: caml-list <caml-list@inria.fr<mailto:caml-list@inria.fr>>
Subject: Re: [Caml-list] Profiling ocaml with lwt


Generally I wrap external calls in something that gets that gets the wall time of an external service call and logs it somewhere.

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. The communication to those servers is done asynchronously, through lwt (epoll). I suspect that is the reason why delays in that communication don’t show up in the gprof result, but I’m not really sure.


Does anybody know of a way to profile lwt applications in a way that these kinds of delays might show up so I know which backend system I have to focus on?


Kasper

Western Digital Corporation (and its subsidiaries) E-mail Confidentiality Notice & Disclaimer:

This e-mail and any files transmitted with it may contain confidential or legally privileged information of WDC and/or its affiliates, and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. If you have received this e-mail in error, please notify the sender immediately and delete the e-mail in its entirety from your system.
Western Digital Corporation (and its subsidiaries) E-mail Confidentiality Notice & Disclaimer:

This e-mail and any files transmitted with it may contain confidential or legally privileged information of WDC and/or its affiliates, and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. If you have received this e-mail in error, please notify the sender immediately and delete the e-mail in its entirety from your system.

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

  reply	other threads:[~2016-03-09  9:58 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 [this message]
2016-03-10  7:41     ` Török Edwin
2016-03-10  7:55       ` Malcolm Matalka
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=A8D4A12D-D366-4391-B2A8-B9CEBE8D350D@HGST.com \
    --to=kasper.janssens@hgst.com \
    --cc=caml-list@inria.fr \
    --cc=mmatalka@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).