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

Re: postgres eating CPU on HP9000

From: "Marcus Andree S(dot) Magalhaes" <marcus(dot)magalhaes(at)vlinfo(dot)com(dot)br>
To: <scott(dot)marlowe(at)ihs(dot)com>
Cc: <nfesposi(at)sourceweave(dot)net>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: postgres eating CPU on HP9000
Date: 2004-03-27 10:38:37
Message-ID: 62945.200.174.148.100.1080383917.squirrel@webmail.webnow.com.br (view raw or flat)
Thread:
Lists: pgsql-performance
<snip>

We are experiencing exactly the same problem here, and we use 7.4 on
Linux/i386 SMP (2 processors). Our databases does even more access:
about 30k selects per hour, 10k updates and inserts per hour

Vacuum analyze is done daily.

We migrated our database to a new server. Initially, everything was fine,
and pretty fast. In a week or so, Vacuum performance is pretty slow. What
was done in 15 minutes now takes 2 hours. Postgres is consuming a lot of
CPU power and, when the system is in peak period, it's even worse.

Sure, we have a large database. 3 tables have more than 10M records, but
more or less suddenly, we're having a heavy performance prejudice.

>
> This almost sounds like a problem (fixed in 7.4 I believe) where some
> system catalog indexes would get huge over time, and couldn't be
> vacuumed  or reindexed while the database was up in multi-user mode.
>
> I'll defer to Tom or Bruce or somebody to say if my guess is even
> close...
>
>
> ---------------------------(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: Tom LaneDate: 2004-03-28 17:16:18
Subject: Re: severe performance issue with planner
Previous:From: Tom LaneDate: 2004-03-27 00:36:29
Subject: Re: postgres eating CPU on HP9000

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