X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 27E46D1E92A for ; Thu, 13 May 2004 10:02:37 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 90351-06 for ; Thu, 13 May 2004 10:02:19 -0300 (ADT) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by svr1.postgresql.org (Postfix) with ESMTP id 15644D1B231 for ; Thu, 13 May 2004 10:02:16 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 3D54D374D2; Thu, 13 May 2004 10:02:21 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 3A6A0374D0 for ; Thu, 13 May 2004 10:02:21 -0300 (ADT) X-Received: from localhost ([unix socket]) by ganymede.hub.org (Cyrus v2.2.3) with LMTP; Thu, 13 May 2004 03:45:26 -0300 X-Sieve: CMU Sieve 2.2 X-Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id DD95535690 for ; Thu, 13 May 2004 03:45:21 -0300 (ADT) X-Received: from mail.postgresql.org [200.46.204.71] by localhost with IMAP (fetchmail-6.2.5) for scrappy@localhost (single-drop); Thu, 13 May 2004 03:45:21 -0300 (ADT) X-Received: from svr1.postgresql.org ([unix socket]) by svr1.postgresql.org (Cyrus v2.2.3) with LMTP; Thu, 13 May 2004 03:44:35 -0300 X-Sieve: CMU Sieve 2.2 X-Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 4009CD1E632 for ; Thu, 13 May 2004 03:44:35 -0300 (ADT) X-Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 07155-06 for ; Thu, 13 May 2004 03:44:16 -0300 (ADT) X-Received: from bob.samurai.com (bob.samurai.com [205.207.28.75]) by svr1.postgresql.org (Postfix) with ESMTP id 53E94D1E6A5 for ; Thu, 13 May 2004 03:44:14 -0300 (ADT) X-Received: from localhost (localhost [127.0.0.1]) by bob.samurai.com (Postfix) with ESMTP id 4C5AC1FC5; Thu, 13 May 2004 02:44:14 -0400 (EDT) X-Received: from bob.samurai.com ([127.0.0.1]) by localhost (bob.samurai.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 49620-01-7; Thu, 13 May 2004 02:44:11 -0400 (EDT) X-Received: from [192.168.1.101] (d226-89-59.home.cgocable.net [24.226.89.59]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by bob.samurai.com (Postfix) with ESMTP id 707811FDE; Thu, 13 May 2004 02:44:09 -0400 (EDT) Subject: Re: Clarification on some settings From: Neil Conway To: Shridhar Daithankar Cc: Doug Y , psql-performance@postgresql.org In-Reply-To: <40A1E83E.2000402@frodo.hserus.net> References: <6.0.1.1.2.20040511163104.01e9cbb0@mail.traderonline.com> <40A1E83E.2000402@frodo.hserus.net> Content-Type: text/plain Message-Id: <1084430647.21452.40.camel@tokyo> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 13 May 2004 02:44:07 -0400 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mailbox.samurai.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-DCC: : X-Spam-Pyzor: ReSent-Date: Thu, 13 May 2004 10:02:14 -0300 (ADT) Resent-From: "Marc G. Fournier" Resent-To: pgsql-performance@postgresql.org ReSent-Subject: Re: [PERFORM] Clarification on some settings ReSent-Message-ID: <20040513100214.W58152@ganymede.hub.org> X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/119 X-Sequence-Number: 6950 On Wed, 2004-05-12 at 05:02, Shridhar Daithankar wrote: > I agree. For shared buffers start with 5000 and increase in batches on 1000. Or > set it to a high value and check with ipcs for maximum shared memory usage. If > share memory usage peaks at 100MB, you don't need more than say 120MB of buffers. If your DB touches more than 100MB worth of buffers over time, shared memory consumption won't peak at 100MB. PG shared buffers are only "recycled" when there are no unused buffers available, so this isn't a really valid way to determine the right shared_buffers setting. -Neil