| 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 |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-03-28 17:16:18 | Re: severe performance issue with planner |
| Previous Message | Tom Lane | 2004-03-27 00:36:29 | Re: postgres eating CPU on HP9000 |