From: Josh Berkus <josh@agliodbs.com>
To: Fabio Esposito <nfesposi@sourceweave.net>
To: pgsql-performance@postgresql.org
Subject: Re: postgres eating CPU on HP9000
Date: Fri, 26 Mar 2004 15:11:22 -0800
Message-ID: <200403261511.22493.josh@agliodbs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0403231318150.17978-100000@cr818510-a.basement>
References: <Pine.LNX.4.44.0403231318150.17978-100000@cr818510-a.basement>
Fabio,
> Postgres initially worked wonderfully, fast and solid. It
> preformed complex joins in 0.01secs, and was able to keep up with our
> message queue. It stayed this way for almost a year during our
> development.
>
> Recently it started eating up the cpu, and cannot keepup with the system
> like it used to. The interesting thing here is that it still runs great
> on an older system with less ram, one slower cpu, and an older disk.
This really points to a maintenance problem. How often do you run VACUUM
ANALYZE? You have a very high rate of data turnover, and should need to
VACUUM frequently.
Also, what's you max_fsm_pages setting.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, nfesposi@sourceweave.net
Subject: Re: postgres eating CPU on HP9000
In-Reply-To: <200403261511.22493.josh@agliodbs.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