X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 06345D1B1A9 for ; Mon, 28 Jun 2004 16:40:11 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 76636-05 for ; Mon, 28 Jun 2004 19:40:12 +0000 (GMT) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 66F9BD1B1D2 for ; Mon, 28 Jun 2004 16:40:09 -0300 (ADT) Received: from [64.81.245.111] (HELO 192.168.1.102) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 5533388; Mon, 28 Jun 2004 12:41:49 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Frank Knobbe Subject: Re: postgres 7.4 at 100% Date: Mon, 28 Jun 2004 12:40:02 -0700 User-Agent: KMail/1.5.4 Cc: pgsql-performance@postgresql.org References: <40DE5C25.6070805@familyhealth.com.au> <1088397641.1105.10.camel@localhost> In-Reply-To: <1088397641.1105.10.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200406281240.02954.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.3 tagged_above=0.0 required=5.0 tests=RCVD_NUMERIC_HELO X-Spam-Level: X-Archive-Number: 200406/278 X-Sequence-Number: 7336 Frank, > Doug said the same, yet the PG Tuning article recommends not make this > too large as it is just temporary used by the query queue or so. (I > guess the system would benefit using more memory for file system cache) As one of the writers of that article, let me point out: " -- Medium size data set and 256-512MB available RAM: 16-32MB (2048-4096) -- Large dataset and lots of available RAM (1-4GB): 64-256MB (8192-32768) " While this is probably a little conservative, it's still way bigger than 40. I would disagree with the folks who suggest 32,000 as a setting for you. On Linux, that's a bit too large; I've never seen performance improvements with shared_buffers greater than 18% of *available* RAM. -- -Josh Berkus Aglio Database Solutions San Francisco