From: "David Baelde" <david.baelde@gmail.com>
To: "Hendrik Tews" <H.Tews@cs.ru.nl>
Cc: Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Memory cost of a compaction
Date: Mon, 4 Dec 2006 10:22:47 +0100 [thread overview]
Message-ID: <53c655920612040122tbabcc27mb89fac3bee50475c@mail.gmail.com> (raw)
In-Reply-To: <wwuejrgf2r2.fsf@tandem.cs.ru.nl>
Hi,
I actually started logging Gc compactions and a few other messages
after that mail. It showed me that many compactions happened before 10
hours of run, without any noticeable cost in memory consumption.
Besides, the OCaml heap is really small compared to the C heap.
Using mtrace() I actually found out that my bug is related to vorbis
(probably used in a wrong way in ocaml-vorbis in case of downsampling)
which after ten hours requires two 50MB PCM buffers...
Anyway, after a little thinking it seems to me that not much extra
memory is needed by compactions, you can just move things inside down
the heap without extra room, right?
David
prev parent reply other threads:[~2006-12-04 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 15:34 David Baelde
2006-12-04 9:07 ` [Caml-list] " Hendrik Tews
2006-12-04 9:22 ` David Baelde [this message]
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=53c655920612040122tbabcc27mb89fac3bee50475c@mail.gmail.com \
--to=david.baelde@gmail.com \
--cc=H.Tews@cs.ru.nl \
--cc=caml-list@inria.fr \
--cc=david.baelde@ens-lyon.org \
/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).