View source for Memory size, overcommit, limit

== Paging and the OOM-Killer  ==

Due to the nature of experiments our group runs, we often induce heavy paging and complete exhaustion of available memory on certain nodes. Linux has a pair of strategies to deal with heavy memory use. First, is overcommitting. This is where a process is allowed allocate or fork even when there is no more memory available. You can seem some interesting numbers here:[http://opsmonkey.blogspot.com/2007/01/linux-memory-overcommit.html]. The assumption is that processes may not use all memory that they allocate and failing on allocation is worse than failing at a later date when the memory use is actually required. More processes may be supported by allowing them to allocate memory (provided they do not use it all). The second part of the strategy is the Out-of-Memory killer (OOM Killer). When memory has been exhausted and a process tries to use some 'overcommitted' part of memory, the OOM killer is invoked. It's job is to rank all processes in terms of their memory use, priority, privilege and some other parameters, and then select a process to kill based on the ranks. 

The argument for using overcommital+OOM Killer is that rather than failing to allocate memory for some random unlucky process, which as a result would probably terminate, the kernel can instead allow the unlucky process to continue executing and then make a some-what-informed decision on which process to kill. Unfortunately, the behaviour of the OOM-killer sometimes causes problems which grind the machine to a complete halt, particularly when it decides to kill system processes. There is a good discussion on the OOM-killer here: [http://lwn.net/Articles/104179/] 

For this reason overcommit has been disabled on the HCL cluster. 

 cat /proc/sys/vm/overcommit_memory 
 2
 cat /proc/sys/vm/overcommit_ratio 
 100

To restore to default overcommit 

 # echo 0 &gt; /proc/sys/vm/overcommit_memory
 # echo 50 &gt; /proc/sys/vm/overcommit_ratio

<br> 

Run the following two programmes from here: [http://www.win.tue.nl/~aeb/linux/lk/lk-9.html www.win.tue.nl/~aeb/linux/lk/lk-9.html] to test results. 

Demo program 1: allocate memory without using it. 

<source lang="">#include <stdio.h>
#include <stdlib.h>

int main (void) {
        int n = 0;

        while (1) {
                if (malloc(1<<20) == NULL) {
                        printf("malloc failure after %d MiB\n", n);
                        return 0;
                }
                printf ("got %d MiB\n", ++n);
        }
}</source><br> 

Demo program 2: allocate memory and actually touch it all. 

<source lang="">#include <stdio.h>
#include <string.h>
#include <stdlib.h>

int main (void) {
        int n = 0;
        char *p;

        while (1) {
                if ((p = malloc(1<<20)) == NULL) {
                        printf("malloc failure after %d MiB\n", n);
                        return 0;
                }
                memset (p, 0, (1<<20));
                printf ("got %d MiB\n", ++n);
        }
}</source> 

== Manually Limit the Memory on the OS level  ==

as root edit /etc/default/grub 

 GRUB_CMDLINE_LINUX_DEFAULT="quiet mem=128M"

then run the command 

 update-grub
 reboot