From: Cott Lang <cott@internetstaff.com>
To: Steve Poe <spoe@sfnet.cc>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to improve db performance with $7K?
Date: Tue, 29 Mar 2005 07:52:54 -0700
Message-ID: <1112107974.7903.28.camel@sixtyfour.internetstaff.com> (raw)
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>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: cott@internetstaff.com, spoe@sfnet.cc
Subject: Re: How to improve db performance with $7K?
In-Reply-To: <1112107974.7903.28.camel@sixtyfour.internetstaff.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox