From: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
To: pgsql-performance@postgresql.org
Subject: Re: FW: [ADMIN] Shared_buffers and kernel parameters, tuning
Date: Tue, 10 Jun 2003 10:45:25 +0530
Message-ID: <3EE5B6C5.31892.7FE833A@localhost> (raw)
In-Reply-To: <EFF9ABB64B24D511A75C0002A5512D5C01911DE4@LEWEXCH>
On 9 Jun 2003 at 11:18, Howard Oblowitz wrote:
> > in postgresql.conf:
> >
> > shared_buffers = 117248 (shmmax / 2 / 1024 / 8 ) This I got from this
> > forum.
> >
> >
> > Does this sound right or am I totally out of bounds here? I have, as said
> > before done this on our dev macine ( a lot smaller machine ), but it would
> > be nice with some feedback ..
With that kind of RAM and that kind of shared buffers setting, you must set
effective OS cache size so that postgresql can calculate when to flush buffers.
While tuning database, it always help to pin down the target first and then try
to reach it. If you could let us know what performance you are expecting out of
this machine and for what kind of load in terms of concurrent users, database
size and usage pattern etc., that would help.
HTH
Bye
Shridhar
--
QOTD: "I'm just a boy named 'su'..."
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: shridhar_daithankar@persistent.co.in
Subject: Re: FW: [ADMIN] Shared_buffers and kernel parameters, tuning
In-Reply-To: <3EE5B6C5.31892.7FE833A@localhost>
References: <EFF9ABB64B24D511A75C0002A5512D5C01911DE4@LEWEXCH> <3EE5B6C5.31892.7FE833A@localhost>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox