From: Anthony Tavener <anthony.tavener@gmail.com>
To: oliver <oliver@first.in-berlin.de>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Early GC'ing
Date: Mon, 19 Aug 2013 00:43:56 -0600 [thread overview]
Message-ID: <CAN=ouMSFSEmrnbdkfEefa0faKKoTJQqTNdgzT+5tnLADDMaU3A@mail.gmail.com> (raw)
In-Reply-To: <20130819002023.GA11063@siouxsie>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
What I was hinting at with Gc.full_major (), is that if you still had a
large amount of memory allocated after calling that, I think that means
your program is still holding on to the values somewhere.
In your loop, when you read in the data each time, is there any way
something might leak? A hashtable holding reference to buffers? Or files
left open?
I tried searching for tools which might help with memory leaks or
profiling, and got a recent presentation I hadn't seen:
http://oud.ocaml.org/2012/slides/oud2012-paper13-slides.pdf
Not that that is much help for you right now...!
And I found these tips on GC params:
http://elehack.net/writings/programming/ocaml-memory-tuning
But it doesn't seem like it's a tuning problem, if the memory is still
"live", especially after a full_major collection.
Sorry I don't have much more help on this!
On Sun, Aug 18, 2013 at 6:20 PM, oliver <oliver@first.in-berlin.de> wrote:
> ...strangely the resulting data is different for each run...
>
>
> ...strange.
>
>
>
[-- Attachment #2: Type: text/html, Size: 1713 bytes --]
next prev parent reply other threads:[~2013-08-19 6:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 20:42 oliver
2013-08-18 20:53 ` oliver
2013-08-18 21:14 ` Anthony Tavener
2013-08-18 22:40 ` oliver
2013-08-19 0:20 ` oliver
2013-08-19 6:43 ` Anthony Tavener [this message]
2013-08-19 10:34 ` oliver
2013-08-19 11:39 ` Mark Shinwell
2013-08-19 11:51 ` Adrien Nader
2013-08-19 12:36 ` oliver
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='CAN=ouMSFSEmrnbdkfEefa0faKKoTJQqTNdgzT+5tnLADDMaU3A@mail.gmail.com' \
--to=anthony.tavener@gmail.com \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.de \
/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).