From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Performance-question
Date: Thu, 7 Feb 2008 16:23:54 +0000 [thread overview]
Message-ID: <200802071623.54116.jon@ffconsultancy.com> (raw)
In-Reply-To: <CE49CA70-EEE5-4B54-9595-FB41B69E8BFF@inria.fr>
On Thursday 07 February 2008 16:13:25 Damien Doligez wrote:
> More generally, I'm looking for (small) programs that exhibit this
> kind of behaviour: they call the compactor frequently and their memory
> usage grows without bound when the compactor is disabled.
The "n"th-nearest neighbor example from OCaml for Scientists is certainly very
allocation intensive because it makes extensive use of the Set module:
http://www.ffconsultancy.com/products/ocaml_for_scientists/complete/
but I'm not sure that its memory use will grow unbounded if compaction is
disabled though.
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?e
prev parent reply other threads:[~2008-02-07 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 13:33 Performance-question Oliver Bandel
2008-02-05 13:51 ` [Caml-list] Performance-question Jon Harrop
2008-02-05 16:18 ` Oliver Bandel
2008-02-07 16:13 ` Damien Doligez
2008-02-07 16:23 ` Jon Harrop [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=200802071623.54116.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--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).