From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Adam Chlipala <achlipala@janestcapital.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml runtime using too much memory in 64-bit Linux
Date: Wed, 07 Nov 2007 19:20:21 +0100 [thread overview]
Message-ID: <1194459622.15728.94.camel@localhost.localdomain> (raw)
In-Reply-To: <4731F5D1.2070405@janestcapital.com>
Am Mittwoch, den 07.11.2007, 12:28 -0500 schrieb Adam Chlipala:
> I've encountered a problem where certain OCaml programs use orders of
> magnitude more RAM when compiled/run in 64-bit Linux instead of 32-bit
> Linux. Some investigation led to the conclusion that the difference has
> to do with the size of OCaml page tables. (Here I mean the page tables
> maintained by the OCaml runtime system, not any OS stuff.)
>
> A program that should be using just a few megabytes of RAM ends up using
> 200+ MB to store a page table. It seems that a C macro is defined by
> default on 64-bit Linux to use mmap() instead of malloc(). Ironically,
> a comment says that this was done to avoid being given blocks of memory
> that are very far apart from each other, forcing the creation of overly
> large page tables. It's ironic because that is exactly the problem that
> is showing up now with mmap(). It ends up called twice for the program
> I'm looking at, and the two addresses it returns are far enough apart to
> lead to creation of a 200 MB page table.
>
> Has anyone else experienced this problem? Would the runtime system need
> to be changed to avoid it?
We are using O'Caml on 64 bit Linux, and aren't aware of such problems.
Did you observe a debug GC message that proves it? 200 MB means that an
address space of 200M * 4K = 8E is covered.
Also think of Linux modifications that do address randomization, i.e.
prevent that contiguous addresses are allocated.
Gerd
--
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany
gerd@gerd-stolpmann.de http://www.gerd-stolpmann.de
Phone: +49-6151-153855 Fax: +49-6151-997714
------------------------------------------------------------
next prev parent reply other threads:[~2007-11-07 18:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 17:28 Adam Chlipala
2007-11-07 18:20 ` Gerd Stolpmann [this message]
2007-11-07 19:12 ` [Caml-list] " Adam Chlipala
2007-11-08 12:56 ` Samuel Mimram
2007-11-14 4:20 ` Romain Beauxis
2007-11-14 12:03 ` Vladimir Shabanov
2007-11-14 12:55 ` Xavier Leroy
2007-11-14 13:45 ` Brian Hurt
2007-11-14 14:16 ` Romain Beauxis
2007-11-14 15:56 ` Markus Mottl
2007-11-14 16:22 ` Stefan Monnier
2007-11-14 16:36 ` [Caml-list] " Brian Hurt
2007-11-14 17:08 ` Lionel Elie Mamane
2007-11-14 17:26 ` Stefan Monnier
2007-11-14 16:45 ` Lionel Elie Mamane
2007-11-14 17:08 ` Lionel Elie Mamane
2007-11-08 20:51 ` [Caml-list] " Romain Beauxis
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=1194459622.15728.94.camel@localhost.localdomain \
--to=info@gerd-stolpmann.de \
--cc=achlipala@janestcapital.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