Content-Type: text/plain;
  charset="iso-8859-1"
From: snpe <snpe@snpe.co.yu>
To: pgsql-general@postgresql.org
Subject: Re: Performance tuning for linux, 1GB RAM, dual CPU?
Date: Thu, 12 Jul 2001 19:18:23 +0200
References: <5146853DD571D411AC54000102070D611C7F10@MINGBGNTS02>
	<20010712134958W.t-ishii@sra.co.jp> <16987.994947657@sss.pgh.pa.us>
In-Reply-To: <16987.994947657@sss.pgh.pa.us>
MIME-Version: 1.0
Message-Id: <01071219182300.01463@spnew>
Content-Transfer-Encoding: 8bit


> Another factor, not under our control, is that if the shared memory
> region gets too large the kernel may decide to swap out portions of
> it that haven't been touched lately.  This of course is completely
> counterproductive, especially if what gets swapped is a dirty buffer,
> which'll eventually have to be read back in and then written to where
> it should have gone.  This is the main factor behind my thought that you
> don't want to skimp on kernel disk buffer space --- any memory pressure
> in the system should be resolvable by dropping kernel disk buffers, not
> by starting to swap shmem or user processes.
>

You can lock shared memory for this problem ?


regards
haris peco