X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id B0DD2310BB7 for ; Tue, 10 Jun 2003 06:39:41 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 40759-07 for ; Tue, 10 Jun 2003 03:39:31 -0300 (ADT) Received: from www.pspl.co.in (www.pspl.co.in [202.54.11.65]) by svr1.postgresql.org (Postfix) with ESMTP id 33272313616 for ; Tue, 10 Jun 2003 02:16:22 -0300 (ADT) Received: (from root@localhost) by www.pspl.co.in (8.11.6/8.11.6) id h5A5GHI22531 for ; Tue, 10 Jun 2003 10:46:17 +0530 Received: from daithan (daithan.intranet.pspl.co.in [192.168.7.161]) by www.pspl.co.in (8.11.6/8.11.0) with ESMTP id h5A5GHQ22526 for ; Tue, 10 Jun 2003 10:46:17 +0530 From: "Shridhar Daithankar" To: pgsql-performance@postgresql.org Date: Tue, 10 Jun 2003 10:45:25 +0530 MIME-Version: 1.0 Subject: Re: FW: [ADMIN] Shared_buffers and kernel parameters, tuning Reply-To: shridhar_daithankar@persistent.co.in Message-ID: <3EE5B6C5.31892.7FE833A@localhost> In-reply-to: X-mailer: Pegasus Mail for Windows (v4.02) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Archive-Number: 200306/27 X-Sequence-Number: 2111 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'..."