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 DEB143A4AB8 for ; Fri, 26 Nov 2004 18:31:46 +0000 (GMT) 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 43559-09 for ; Fri, 26 Nov 2004 18:31:36 +0000 (GMT) Received: from server2.sitesell.com (server2.sitesell.com [216.95.221.3]) by svr1.postgresql.org (Postfix) with SMTP id 3566C3A4792 for ; Fri, 26 Nov 2004 18:31:35 +0000 (GMT) Received: (qmail 7637 invoked from network); 26 Nov 2004 18:31:31 -0000 Received: from dyn-70-236.tor.dsl.tht.net (134.22.70.236) by server2.sitesell.com with SMTP; 26 Nov 2004 18:31:31 -0000 Subject: Re: time to stop tuning? From: Rod Taylor To: David Parker Cc: Postgresql Performance In-Reply-To: <07FDEE0ED7455A48AC42AC2070EDFF7C26BDD2@corpsrv2.tazznetworks.com> References: <07FDEE0ED7455A48AC42AC2070EDFF7C26BDD2@corpsrv2.tazznetworks.com> Content-Type: text/plain Date: Fri, 26 Nov 2004 13:29:19 -0500 Message-Id: <1101493759.44437.302.camel@home> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/411 X-Sequence-Number: 9365 On Fri, 2004-11-26 at 12:13 -0500, David Parker wrote: > > I suspect the ultimate answer to our problem will be: > > 1) aggressive client-side caching > 2) SQL tuning > 3) more backend hardware #0 might actually be using connection pooling and using cached query plans (PREPARE), disabling the statistics daemon, etc. For the plans, send us EXPLAIN ANALYZE output for each of the common queries. If you can try it, I'd give a try at FreeBSD or a newer Linux on your system instead of Solaris. Older versions of Solaris had not received the same amount of attention for Intel hardware as the BSDs and Linux have and I would imagine (having not tested it recently) that this is still true for 32bit Intel. Another interesting test might be to limit the number of simultaneous connections to 8 instead of 30 (client side connection retry) after client side connection pooling via pgpool or similar has been installed. Please report back with your findings. -- Rod Taylor