public inbox for [email protected]  

help / color / mirror / Atom feed

From: Toru SHIMOGAKI <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: doc patch for Linux memory overcommit
Date: Tue, 06 Mar 2007 17:28:20 +0900
Message-ID: <[email protected]> (raw)


The attached is a doc patch for Linux memory overcommit and an additional way of
avoiding a problem that postmaster is suddenly killed by OOM-Killer.

http://archives.postgresql.org/pgsql-docs/2007-03/msg00000.php

Best regards,

-- 
Toru SHIMOGAKI<[email protected]>

*** runtime.sgml.orig	2007-03-06 16:23:10.000000000 +0900
--- runtime.sgml	2007-03-06 17:14:38.000000000 +0900
***************
*** 1207,1215 ****
     </para>
  
     <para>
!     On Linux 2.6 and later, a better solution is to modify the kernel's
!     behavior so that it will not <quote>overcommit</> memory.  This is
!     done by selecting strict overcommit mode via <command>sysctl</command>:
  <programlisting>
  sysctl -w vm.overcommit_memory=2
  </programlisting>
--- 1207,1224 ----
     </para>
  
     <para>
!     In addition, increasing swap area on OS can avoid the problem too.
!     Out-of-Memory-Killer(OOM-Killer) is invoked whenever physical memory and 
!     swap area are exhausted. Increasing swap area is easy to set and it 
!     doesn't have harmful influence.
!    </para>
! 
!    <para>
!     On Linux 2.6 and later, a better solution is to modify the kernel's 
!     behavior so that it will not <quote>overcommit</> memory.  Though this 
!     setting can't prevent OOM-Killer from invoking directly, we can expect 
!     healty memory allocation. This is done by selecting strict overcommit 
!     mode via <command>sysctl</command>:
  <programlisting>
  sysctl -w vm.overcommit_memory=2
  </programlisting>


Attachments:

  [text/plain] overcommit_doc.patch (1.2K, 2-overcommit_doc.patch)
  download | inline diff:
*** runtime.sgml.orig	2007-03-06 16:23:10.000000000 +0900
--- runtime.sgml	2007-03-06 17:14:38.000000000 +0900
***************
*** 1207,1215 ****
     </para>
  
     <para>
!     On Linux 2.6 and later, a better solution is to modify the kernel's
!     behavior so that it will not <quote>overcommit</> memory.  This is
!     done by selecting strict overcommit mode via <command>sysctl</command>:
  <programlisting>
  sysctl -w vm.overcommit_memory=2
  </programlisting>
--- 1207,1224 ----
     </para>
  
     <para>
!     In addition, increasing swap area on OS can avoid the problem too.
!     Out-of-Memory-Killer(OOM-Killer) is invoked whenever physical memory and 
!     swap area are exhausted. Increasing swap area is easy to set and it 
!     doesn't have harmful influence.
!    </para>
! 
!    <para>
!     On Linux 2.6 and later, a better solution is to modify the kernel's 
!     behavior so that it will not <quote>overcommit</> memory.  Though this 
!     setting can't prevent OOM-Killer from invoking directly, we can expect 
!     healty memory allocation. This is done by selecting strict overcommit 
!     mode via <command>sysctl</command>:
  <programlisting>
  sysctl -w vm.overcommit_memory=2
  </programlisting>

view thread (3+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: doc patch for Linux memory overcommit
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox