Skip site navigation (1) Skip section navigation (2)

Re: postgres eating CPU on HP9000

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Fabio Esposito <nfesposi(at)sourceweave(dot)net>,pgsql-performance(at)postgresql(dot)org
Subject: Re: postgres eating CPU on HP9000
Date: 2004-03-26 23:11:22
Message-ID: 200403261511.22493.josh@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-performance
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


In response to

Responses

pgsql-performance by date

Next:From: Steve AtkinsDate: 2004-03-26 23:14:59
Subject: Re: [HACKERS] fsync method checking
Previous:From: Tom LaneDate: 2004-03-26 23:08:54
Subject: Re: odd planner choice

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group