From: Rik van Riel <riel@redhat.com>
To: Marco Nietz <m.nietz-mm@iplabs.de>
Cc: Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: oom-killer why ?
Date: Sat, 30 Aug 2008 14:19:08 -0400 [thread overview]
Message-ID: <20080830141908.2fdf788b@bree.surriel.com> (raw)
In-Reply-To: <48B4F268.20901@iplabs.de>
On Wed, 27 Aug 2008 08:21:28 +0200
Marco Nietz <m.nietz-mm@iplabs.de> wrote:
> My first guess that the oom where caused by running out of Lowmem was
> confirmed and the Solution is to upgrade the Server to a 64bit OS.
Indeed.
> All right to that point, but why this was affected by the raised up
> Sharded Buffers from postgres ? Is shared buffer preferred to be in lowmem ?
>
> With the smaller Buffersize (256mb) we haven't had any Problems with
> that Machine.
No, but the page tables used to map the shared buffer are in lowmem.
Page tables take up 0.5% of the data size, per process.
This means that if you have 200 processes mapping 1GB of data, you
would need 1GB of page tables. You do not have that much lowmem :)
--
All rights reversed.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2008-08-30 18:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 11:25 Marco Nietz
2008-08-25 15:56 ` Christoph Lameter
2008-08-25 16:18 ` Marco Nietz
2008-08-25 16:29 ` Christoph Lameter
2008-08-25 17:26 ` Marco Nietz
2008-08-25 18:55 ` Christoph Lameter
2008-08-26 6:44 ` Marco Nietz
2008-08-26 13:23 ` Christoph Lameter
2008-08-26 10:45 ` Larry Woodman
2008-08-25 17:36 ` Larry Woodman
2008-08-26 11:11 ` Balbir Singh
2008-08-26 12:00 ` Marco Nietz
2008-08-26 13:15 ` Balbir Singh
2008-08-26 13:18 ` Balbir Singh
2008-08-26 19:09 ` Larry Woodman
2008-08-27 2:32 ` Balbir Singh
2008-08-27 6:21 ` Marco Nietz
2008-08-30 18:19 ` Rik van Riel [this message]
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=20080830141908.2fdf788b@bree.surriel.com \
--to=riel@redhat.com \
--cc=linux-mm@kvack.org \
--cc=m.nietz-mm@iplabs.de \
/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