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 8F569D1B194 for ; Thu, 13 May 2004 22:04:16 -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 66758-08 for ; Thu, 13 May 2004 22:03:58 -0300 (ADT) Received: from lamb.mcmillan.net.nz (leibniz.catalyst.net.nz [202.49.159.7]) by svr1.postgresql.org (Postfix) with ESMTP id C99FFD1B181 for ; Thu, 13 May 2004 22:03:53 -0300 (ADT) Received: from lamb.mcmillan.net.nz (lamb.mcmillan.net.nz [127.0.0.1]) by lamb.mcmillan.net.nz (Postfix) with ESMTP id 4B7DEAE178BF; Wed, 12 May 2004 20:58:13 +1200 (NZST) Subject: Re: Quad processor options From: Andrew McMillan To: Paul Tuckfield Cc: Bjoern Metzdorf , pgsql-performance@postgresql.org In-Reply-To: <089ED266-A39D-11D8-A34F-000393BD6C3E@tuckfield.com> References: <40A13A78.9000607@turtle-entertainment.de> <089ED266-A39D-11D8-A34F-000393BD6C3E@tuckfield.com> Content-Type: text/plain Message-Id: <1084352292.4785.37.camel@lamb.mcmillan.net.nz> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.5.7 Date: Wed, 12 May 2004 20:58:13 +1200 Content-Transfer-Encoding: 7bit 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/133 X-Sequence-Number: 6964 On Tue, 2004-05-11 at 15:46 -0700, Paul Tuckfield wrote: > - the "cache" column shows that linux is using 2.3G for cache. (way too > much) you generally want to give memory to postgres to keep it "close" to > the user, not leave it unused to be claimed by linux cache (need to leave > *some* for linux tho) > > My recommendations: > - I'll bet you have a low value for shared buffers, like 10000. On > your 3G system you should ramp up the value to at least 1G (125000 8k buffers) > unless something else runs on the system. It's best to not do things too > drastically, so if Im right and you sit at 10000 now, try going to > 30000 then 60000 then 125000 or above. Huh? Doesn't this run counter to almost every piece of PostgreSQL performance tuning advice given? I run my own boxes with buffers set to around 10000-20000 and an effective_cache_size = 375000 (8k pages - around 3G). That's working well with PostgreSQL 7.4.2 under Debian "woody" (using Oliver Elphick's backported packages from http://people.debian.org/~elphick/debian/). Regards, Andrew. ------------------------------------------------------------------------- Andrew @ Catalyst .Net .NZ Ltd, PO Box 11-053, Manners St, Wellington WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St DDI: +64(4)916-7201 MOB: +64(21)635-694 OFFICE: +64(4)499-2267 Q: How much does it cost to ride the Unibus? A: 2 bits. -------------------------------------------------------------------------