From: Tom Lane <tgl@sss.pgh.pa.us>
To: andris@neti.ee
Cc: pgsql-performance@postgresql.org
Subject: Re: Serious issues with CPU usage
Date: Fri, 05 Sep 2003 20:05:00 -0400
Message-ID: <28675.1062806700@sss.pgh.pa.us> (raw)
In-Reply-To: <20030905215635.68C1173595@MX2.estpak.ee>
References: <20030905215635.68C1173595@MX2.estpak.ee>
<andris@neti.ee> writes:
> i'm having _serious_ issues of postgres hogging up the CPU over time. A graph
> showing this can be seen at http://andri.estpak.ee/cpu0.png .
You really haven't shown us anything that would explain that graph ...
repeated UPDATEs will slow down a little until you vacuum, but not
by the ratio you seem to be indicating. At least not if they're
indexscans. If you've also got sequential-scan queries, and you're
doing many zillion updates between vacuums, the answer is to vacuum
more often. A decent rule of thumb is to vacuum whenever you've updated
more than about 10% of the rows in a table since your last vacuum.
> A VACUUM FULL is a remedy to this problem, but a simple VACUUM isn't.
I find that odd; maybe there's something else going on here. But you've
not given enough details to speculate.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, andris@neti.ee
Subject: Re: Serious issues with CPU usage
In-Reply-To: <28675.1062806700@sss.pgh.pa.us>
References: <20030905215635.68C1173595@MX2.estpak.ee> <28675.1062806700@sss.pgh.pa.us>
* 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