From srinathsmn at gmail.com  Wed Jul 16 18:18:05 2014
From: srinathsmn at gmail.com (Varadharajan Mukundan)
Date: Wed, 16 Jul 2014 21:48:05 +0530
Subject: [Rd] Reducing RAM usage using UKSM
In-Reply-To: <722C34AE-0634-4D41-AFD4-4E7BD332D222@warnes.net>
References: <CACKkDGGf0XXsrqYXmKW3Lnp4dw3zzJ0SG=2_pmWo1HpD=HPY2A@mail.gmail.com>
	<CACKkDGHrW5e1RF3YPJ2NSwgD=GCK6PWJwgQbyFRen_zuTREExw@mail.gmail.com>
	<722C34AE-0634-4D41-AFD4-4E7BD332D222@warnes.net>
Message-ID: <CACKkDGEd1Vw3Z0ZAC_SJGPxKvnYQzW91jeEfZ1b7Rg+p2RuFdg@mail.gmail.com>

Hi Gregory,

> Linux uses a copy-on-write for the memory image of forked processes.  Thus, you may also get significant memory savings by launching a single R process, loading your large data object, and then using fork::fork() to split off the other worker process.

True. The problem is each and every instance has its own dataset (but
they are only similar). For example, QA environment might have about
90% of the rows similar to Showcase environment. Hence we need to have
multiple instances instantiated with its own nearly similar dataset.
This in turn makes it necessary to have some kind of de-duplication
running on the entire memory image.

- Varadharajan



[Rd] Reducing RAM usage using UKSM
Varadharajan Mukundan