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 1DE0952814 for ; Tue, 14 Jun 2005 21:00:23 -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 17467-07 for ; Wed, 15 Jun 2005 00:00:16 +0000 (GMT) Received: from tektite.k12usa.com (tektite.k12hq.com [12.160.186.24]) by svr1.postgresql.org (Postfix) with SMTP id EC2DF52915 for ; Tue, 14 Jun 2005 21:00:14 -0300 (ADT) Received: (qmail 15398 invoked by uid 1001); 14 Jun 2005 23:59:37 -0000 Date: Tue, 14 Jun 2005 19:59:37 -0400 From: Christopher Weimann To: Mark Stosberg Cc: pgsql-performance@postgresql.org Subject: Re: Most effective tuning choices for busy website? Message-ID: <20050614235937.GA97567@tektite.k12usa.internal> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200506/361 X-Sequence-Number: 12998 On 06/01/2005-07:19PM, Mark Stosberg wrote: > > - I saw the hardware tip to "Separate the Transaction Log from the > Database". We have about 60% SELECT statements and 14% UPDATE > statements. Focusing more on SELECT performance seems more important > for us. > I would think that would help SELECT If the spindle isn't busy writing Transaction log it can be reading for your SELECTs. You did say you were CPU bound though. -- ------------------------------------------------------------ Christopher Weimann http://www.k12usa.com K12USA.com Cool Tools for Schools! ------------------------------------------------------------