From: Gabriel Kerneis <gabriel@kerneis.info>
To: Yoann Padioleau <pad@fb.com>
Cc: Caml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] strategies to deal with huge in-memory "object" graphs?
Date: Sat, 09 Aug 2014 21:57:53 +0200 [thread overview]
Message-ID: <8e82de9a0b57f16739bc1cec3a075ff5@kerneis.info> (raw)
In-Reply-To: <7F92DE4E-875E-4020-AF4F-5BC19080225A@fb.com>
Le 2014-08-09 00:20, Yoann Padioleau a écrit :
> Is there a way to partition the heap so that for instance in my case
> all the graph related things are put in a different area that the Gc
> does not have
> to explore each time.
Isn't it what Ancient is (was) for? Designed in times where the keyword
was swap rather than inconceivably large amount of RAM, but the same
idea should work for both situations I guess.
http://caml.inria.fr/cgi-bin/hump.en.cgi?contrib=538
Best,
--
Gabriel
next prev parent reply other threads:[~2014-08-09 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 22:20 Yoann Padioleau
2014-08-09 19:57 ` Gabriel Kerneis [this message]
2014-08-10 6:51 ` Gerd Stolpmann
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=8e82de9a0b57f16739bc1cec3a075ff5@kerneis.info \
--to=gabriel@kerneis.info \
--cc=caml-list@yquem.inria.fr \
--cc=pad@fb.com \
/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).