X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id DC0E1D1ED87 for ; Sat, 27 Mar 2004 10:38:39 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 33294-01 for ; Sat, 27 Mar 2004 06:38:40 -0400 (AST) Received: from ideafix.webnow.com.br (unknown [200.155.0.57]) by svr1.postgresql.org (Postfix) with ESMTP id 52E98D1ED73 for ; Sat, 27 Mar 2004 06:38:37 -0400 (AST) Received: by ideafix.webnow.com.br (Postfix, from userid 48) id 4BBFE197636; Sat, 27 Mar 2004 07:38:37 -0300 (BRT) Received: from 148100.cps.virtua.com.br ([200.174.148.100]) (SquirrelMail authenticated user marcus.magalhaes@vlinfo.com.br) by webmail.webnow.com.br with HTTP; Sat, 27 Mar 2004 07:38:37 -0300 (BRT) Message-ID: <62945.200.174.148.100.1080383917.squirrel@webmail.webnow.com.br> Date: Sat, 27 Mar 2004 07:38:37 -0300 (BRT) Subject: Re: postgres eating CPU on HP9000 From: "Marcus Andree S. Magalhaes" To: In-Reply-To: References: X-Priority: 3 Importance: Normal Cc: , X-Mailer: SquirrelMail (version 1.2.11) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/399 X-Sequence-Number: 6255 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)