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 8336FD1D8A5 for ; Fri, 26 Mar 2004 23:11:53 +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 18896-04 for ; Fri, 26 Mar 2004 19:11:58 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 39423D1D84E for ; Fri, 26 Mar 2004 19:11:50 -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 4704133; Fri, 26 Mar 2004 15:13:16 -0800 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Fabio Esposito , pgsql-performance@postgresql.org Subject: Re: postgres eating CPU on HP9000 Date: Fri, 26 Mar 2004 15:11:22 -0800 User-Agent: KMail/1.5.4 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: <200403261511.22493.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/390 X-Sequence-Number: 6246 Fabio, > Postgres initially worked wonderfully, fast and solid. It > preformed complex joins in 0.01secs, and was able to keep up with our > message queue. It stayed this way for almost a year during our > development. > > Recently it started eating up the cpu, and cannot keepup with the system > like it used to. The interesting thing here is that it still runs great > on an older system with less ram, one slower cpu, and an older disk. This really points to a maintenance problem. How often do you run VACUUM ANALYZE? You have a very high rate of data turnover, and should need to VACUUM frequently. Also, what's you max_fsm_pages setting. -- -Josh Berkus Aglio Database Solutions San Francisco