From: "Mike Lin" <mikelin@mit.edu>
To: Caml <caml-list@yquem.inria.fr>
Subject: gprof timing
Date: Mon, 30 Jun 2008 19:01:33 -0400 [thread overview]
Message-ID: <2a1a1a0c0806301601q4d381588l8d1be1a2d7881838@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
I'm profiling an ocaml program with gprof on an AMD64 linux machine - does
anyone know what to do when the runtime it's reporting (i.e. bottom of the
"cumulative seconds" column) is much much less than the actual runtime
(10-20% of it)? Is this normal somehow?
I've compiled everything with the right flags as far as I can tell, the
program isn't I/O or swap bound and there is nothing else CPU-intensive
running on the machine. The runtime of the program is not much slower with
profiling on than otherwise -- certainly not by an order of magnitude. The
profile that comes out more or less makes sense (i.e. highly intensive
functions appear at the top of the flat profile) except all of the real
times reported seem to be scaled down.
-Mike
[-- Attachment #2: Type: text/html, Size: 781 bytes --]
reply other threads:[~2008-06-30 23:01 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=2a1a1a0c0806301601q4d381588l8d1be1a2d7881838@mail.gmail.com \
--to=mikelin@mit.edu \
--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).