From: Erik de Castro Lopo <ocaml-erikd@mega-nerd.com>
To: caml-list@inria.fr
Subject: Determining memory usage?
Date: Sun, 13 Feb 2005 13:29:39 +1100 [thread overview]
Message-ID: <20050213132939.03ea86d1.ocaml-erikd@mega-nerd.com> (raw)
Hi all,
I was wondering if there was a way of finding the maximum memory
usage of a program compiled with ocamlopt. Preferably I'd like
to print that memory usage out at the end of a run of my program.
TIA,
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam@mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
The main confusion about C++ is that its practitioners think
it is simultaneously a high and low level language when in
reality it is good at neither.
next reply other threads:[~2005-02-13 2:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 2:29 Erik de Castro Lopo [this message]
2005-02-13 8:31 ` [Caml-list] " Remi Vanicat
2005-02-14 1:46 ` Erik de Castro Lopo
2005-02-14 2:05 ` William Lovas
2005-02-14 7:03 ` Erik de Castro Lopo
2005-02-16 15:06 ` Damien Doligez
2005-02-14 2:09 ` William D.Neumann
2005-02-14 2:20 ` Jon Harrop
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=20050213132939.03ea86d1.ocaml-erikd@mega-nerd.com \
--to=ocaml-erikd@mega-nerd.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;
as well as URLs for NNTP newsgroup(s).