pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marcus Andree S. Magalhaes <marcus.magalhaes@vlinfo.com.br>
To: scott.marlowe@ihs.com
Cc: nfesposi@sourceweave.net
Cc: pgsql-performance@postgresql.org
Subject: Re: postgres eating CPU on HP9000
Date: Sat, 27 Mar 2004 07:38:37 -0300 (BRT)
Message-ID: <62945.200.174.148.100.1080383917.squirrel@webmail.webnow.com.br> (raw)
In-Reply-To: <Pine.LNX.4.33.0403261516420.8192-100000@css120.ihs.com>
References: <Pine.LNX.4.44.0403231318150.17978-100000@cr818510-a.basement>
	<Pine.LNX.4.33.0403261516420.8192-100000@css120.ihs.com>

<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@postgresql.org)






view thread (18+ messages)  latest in thread

Message-ID: <62945.200.174.148.100.1080383917.squirrel@webmail.webnow.com.br>
Permalink:  ../62945.200.174.148.100.1080383917.squirrel@webmail.webnow.com.br/
Also on:    postgresql.org/message-id/62945.200.174.148.100.1080383917.squirrel@webmail.webnow.com.br

 · 

reply

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: marcus.magalhaes@vlinfo.com.br, scott.marlowe@ihs.com, nfesposi@sourceweave.net
  Subject: Re: postgres eating CPU on HP9000
  In-Reply-To: <62945.200.174.148.100.1080383917.squirrel@webmail.webnow.com.br>

* 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