From: Martin DeMello <martindemello@gmail.com>
To: OCaml List <caml-list@yquem.inria.fr>
Subject: [Caml-list] profiling question about caml_apply2
Date: Mon, 28 Jul 2014 02:38:21 -0700 [thread overview]
Message-ID: <CAFrFfuFbtvSm46gx=hSJdLmjC5bhxRh8SNSysShrO_iXcaJy3w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
I'm profiling some code where it seems that caml_apply2 is right near the
top of the gprof list
% cumulative self
time seconds seconds calls name
15.95 0.52 0.52 92467664 camlMutable_rack__has_letter_1031
12.27 0.92 0.40 109589844 caml_apply2
10.74 1.27 0.35 92467664 camlMutable_rack__remove_1035
8.28 1.54 0.27 2478379 camlArray__iteri_1064
7.82 1.80 0.26 32188972 camlMutable_rack__play_1040
3.99 1.93 0.13 64437854 camlTrie__fun_76276
and seems (from the call graphs later down) to be contributing towards the
time taken by camlArray_iteri as well, unless I've misunderstood that bit.
Is this an actual problem, or just a sign that I've optimised all the
obvious bottlenecks already?
martin
[-- Attachment #2: Type: text/html, Size: 1421 bytes --]
reply other threads:[~2014-07-28 9:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAFrFfuFbtvSm46gx=hSJdLmjC5bhxRh8SNSysShrO_iXcaJy3w@mail.gmail.com' \
--to=martindemello@gmail.com \
--cc=caml-list@yquem.inria.fr \
/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).