caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: oliver <oliver@first.in-berlin.de>
Cc: Anil Madhavapeddy <anil@recoil.org>,
	William Le Ferrand <William.Le-Ferrand@polytechnique.edu>,
	Stephane Glondu <steph@glondu.net>,
	caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Storing ocaml values outside ocaml's heap
Date: Thu, 08 Dec 2011 18:02:40 +0100	[thread overview]
Message-ID: <87d3bzdmj3.fsf@frosties.localnet> (raw)
In-Reply-To: <20111208110343.GC2042@siouxsie> (oliver@first.in-berlin.de's message of "Thu, 8 Dec 2011 12:03:43 +0100")

oliver <oliver@first.in-berlin.de> writes:

> On Thu, Dec 08, 2011 at 09:04:50AM +0000, Anil Madhavapeddy wrote:
>> I think Ancient is exactly what you're looking for.
>> 
>> Just disable swap (which you should do anyway on a big modern server), and it
>> will let you keep in-memory, out-of-heap OCaml values that don't get scanned by
>> the GC.
> [...]
>
>
> Completely disabling swap can crash the system.

No it can't. Or at least that would be a serious bug.

With or without swap if you run out of memory the OOM killer activates
and your system goes down the drain. But it should never crash. Swap
just delays the inevitable.

> Better just fine tune it, so that it uses swapping less often.
>
> => on Linux swappiness can be set via /proc:   /proc/sys/vm/swappiness

What I saw is that often on a 16GB node people would start programs that
use up 15.99GB. As in try to maximize the memory they use. Now when some
other things run like a cron job the system would reach an OOM
situation. And that is where a little swap comes in handly.

So give the system 1GB swap so it can swap out enough of a 16GB batch
job to run cron and friends when they occasionally wake up. But nowhere
the amount the ancient swap = 2x ram rule would dictate.

MfG
        Goswin


  reply	other threads:[~2011-12-08 17:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08  4:35 William Le Ferrand
2011-12-08  6:04 ` Stéphane Glondu
2011-12-08  8:19   ` William Le Ferrand
2011-12-08  9:04     ` Anil Madhavapeddy
2011-12-08  9:07       ` William Le Ferrand
2011-12-08 11:03       ` oliver
2011-12-08 17:02         ` Goswin von Brederlow [this message]
2011-12-08  9:40   ` Gaius Hammond
2011-12-08  8:49 ` Anders Fugmann
2011-12-08  8:56   ` William Le Ferrand
2011-12-08  9:29     ` Anders Fugmann
2011-12-08  9:12 ` Gerd Stolpmann
2011-12-08 10:33 ` Goswin von Brederlow

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=87d3bzdmj3.fsf@frosties.localnet \
    --to=goswin-v-b@web.de \
    --cc=William.Le-Ferrand@polytechnique.edu \
    --cc=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=oliver@first.in-berlin.de \
    --cc=steph@glondu.net \
    /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).