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

Re: postgres eating CPU on HP9000

From: Fabio Esposito <nfesposi(at)sourceweave(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: postgres eating CPU on HP9000
Date: 2004-03-29 19:36:24
Message-ID: Pine.LNX.4.44.0403291434220.25470-100000@cr818510-a.basement (view raw or flat)
Thread:
Lists: pgsql-performance

The Vacuum's don't take too long, 10 minutes at most.  I can tell from ps
-ef | grep and top that its the selects/inserts/updates from the postgres
related to our app that take all that time up.  If we rerun initdb and
reload the data, it works great for about two days, then goes bad again.

We are in the process of trying out 7.4.2 right now, just waiting on the
reload of pg_dump.

Fabio

> Fabio,
>
> > We run VACUUM ANALYZE after we remove about 1000 rows every hour on the
> > halh hour.  Our max_fsm_pages is set to 10000
>
> Have you checked how long these vacuums take?   If they are starting to
> overlap, that would explain your high CPU usage and poor performance.    You
> might want to consider raising FSM_pages and vacuuming less frequently.
>
> --
> -Josh Berkus
>  Aglio Database Solutions
>  San Francisco
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>


In response to

Responses

pgsql-performance by date

Next:From: Josh BerkusDate: 2004-03-29 20:23:27
Subject: Re: postgres eating CPU on HP9000
Previous:From: Josh BerkusDate: 2004-03-29 19:14:47
Subject: Re: postgres eating CPU on HP9000

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