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 D3102533A2 for ; Tue, 29 Mar 2005 15:53:02 +0100 (BST) 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 74922-04 for ; Tue, 29 Mar 2005 14:53:01 +0000 (GMT) Received: from jinx.internetstaff.com (unknown [63.214.174.241]) by svr1.postgresql.org (Postfix) with ESMTP id 5A06A52AA2 for ; Tue, 29 Mar 2005 15:53:00 +0100 (BST) Received: from localhost (localhost [127.0.0.1]) by jinx.internetstaff.com (Postfix) with ESMTP id BC8FF4BC2B3; Tue, 29 Mar 2005 07:53:04 -0700 (MST) Received: from jinx.internetstaff.com ([127.0.0.1]) by localhost (jinx [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 18457-05-68; Tue, 29 Mar 2005 07:52:59 -0700 (MST) Subject: Re: How to improve db performance with $7K? From: Cott Lang To: Steve Poe Cc: pgsql-performance@postgresql.org In-Reply-To: <424840AE.3050200@sfnet.cc> References: <42443863.4040302@sfnet.cc> <4244A90B.2030200@sfnet.cc> <42453273.2060509@turtle-entertainment.de> <200503261255.59007.josh@agliodbs.com> <42455DEC.2080301@sfnet.cc> <1112049794.23284.29.camel@localhost.localdomain> <424840AE.3050200@sfnet.cc> Content-Type: text/plain Date: Tue, 29 Mar 2005 07:52:54 -0700 Message-Id: <1112107974.7903.28.camel@sixtyfour.internetstaff.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-2) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at internetstaff.com X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200503/631 X-Sequence-Number: 11336 On Mon, 2005-03-28 at 17:36 +0000, Steve Poe wrote: > I agree with you. Unfortunately, I am not the developer of the > application. The vendor uses ProIV which connects via ODBC. The vendor > could certain do some tuning and create more indexes where applicable. I > am encouraging the vendor to take a more active role and we work > together on this. I've done a lot browsing through pg_stat_activity, looking for queries that either hang around for a while or show up very often, and using explain to find out if they can use some assistance. You may also find that a dump and restore with a reconfiguration to mirrored drives speeds you up a lot - just from the dump and restore. > With hardware tuning, I am sure we can do better than 35Mb per sec. Also > moving the top 3 or 5 tables and indexes to their own slice of a RAID10 > and moving pg_xlog to its own drive will help too. If your database activity involves a lot of random i/o, 35Mb per second wouldn't be too bad. While conventional wisdom is that pg_xlog on its own drives (I know you meant plural :) ) is a big boost, in my particular case I could never get a a measurable boost that way. Obviously, YMMV.