Re: Where to start for performance problem?

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: MK Spam <mk_spam(at)comcast(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Where to start for performance problem?
Date: 2003-11-25 16:52:32
Message-ID: 20031125165232.GA25043@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Mon, Nov 24, 2003 at 16:03:17 -0600,
MK Spam <mk_spam(at)comcast(dot)net> wrote:
>
> The archives of this list provides many ideas for improving performance, but the problem we are having is gradually degrading performance ending in postgres shutting down. So it's not a matter of optimizing a complex query to take 5 seconds instead of 60 seconds. From what I can tell we are using the VACUUM command on a schedule but it doesn't seem to prevent the database from becoming "congested" as we refer to it. :] Anyway, the only way I know to "fix" the problem is to export (pg_dump) the db, drop the database, recreate the database and import the dump. This seems to return performance back to normal but obviously isn't a very good "solution". The slowdown and subsequent crash can take as little as 1 week for databases with a lot of data or go as long as a few weeks to a month for smaller data sets.

A couple of things you might look for are index bloat and having FSM set too
small for your plain vacuums. Upgrading to 7.4 may help with index bloat
if that is your problem.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2003-11-25 17:07:49 Re: Where to start for performance problem?
Previous Message Tom Lane 2003-11-25 15:47:37 Re: Maximum Possible Insert Performance?