From: Tom Hawkins <tom1@launchbird.com>
To: caml-list@inria.fr
Subject: [Caml-list] Memory Consumption and Profiling.
Date: Tue, 28 Jan 2003 10:01:13 -0600 [thread overview]
Message-ID: <200301281001.13888.tom1@launchbird.com> (raw)
Hi,
Can anyone offer tips for profiling a program for memory consumption?
One of my native compiled applications consumes a too much memory
and I'm having a hard time tracking down the source. I did time
profiling with gprof and here are the top four consumers:
Flat profile:
Each sample counts as 0.01 seconds.
% cumulative self self total
time seconds seconds calls s/call s/call name
21.66 2.38 2.38 1040 0.00 0.00 mark_slice
12.28 3.73 1.35 1035 0.00 0.00 sweep_slice
10.19 4.85 1.12 13611466 0.00 0.00 compare_val
4.73 5.37 0.52 1804453 0.00 0.00 Hashtbl__find_117
I'm assuming mark_slice and sweep_slice are part of the garbage collector.
The nature of the program does create a lot of small data structures with
short life span, and my hunch this is where the problem lies.
Any tips?
Thanks,
Tom
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
reply other threads:[~2003-01-28 15:55 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=200301281001.13888.tom1@launchbird.com \
--to=tom1@launchbird.com \
--cc=caml-list@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