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 9ACF5D1B893 for ; Mon, 29 Mar 2004 19:15:21 +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 38835-02 for ; Mon, 29 Mar 2004 15:15:20 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id B9074D1EA84 for ; Mon, 29 Mar 2004 15:15:18 -0400 (AST) Received: from [63.195.55.98] (HELO 192.168.1.29) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 4726805; Mon, 29 Mar 2004 11:16:37 -0800 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Fabio Esposito Subject: Re: postgres eating CPU on HP9000 Date: Mon, 29 Mar 2004 11:14:47 -0800 User-Agent: KMail/1.5.4 Cc: pgsql-performance@postgresql.org References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403291114.47932.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/414 X-Sequence-Number: 6270 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