X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 6F1F09FB345 for ; Mon, 7 Aug 2006 19:26:39 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 55608-09 for ; Mon, 7 Aug 2006 22:26:29 +0000 (UTC) X-Greylist: delayed 00:19:57.422222 by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 3EE749FB35B for ; Mon, 7 Aug 2006 19:26:29 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from pelego.atua.com.br (unknown [200.248.138.61]) by svr4.postgresql.org (Postfix) with ESMTP id C86BE5AF042 for ; Mon, 7 Aug 2006 22:06:28 +0000 (GMT) Received: from [10.0.0.171] (bagual.atua.com.br [200.248.138.60]) by pelego.atua.com.br (Postfix) with ESMTP id 5D29513F660 for ; Mon, 7 Aug 2006 19:06:13 -0300 (BRT) Message-ID: <44D7B958.6030004@atua.com.br> Date: Mon, 07 Aug 2006 19:06:16 -0300 From: Alvaro Nunes Melo User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060725) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Hardware upgraded but performance still ain't good enough Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200608/86 X-Sequence-Number: 20271 Hi, First of all I must tell that my reality in a southern brazilian city is way different than what we read in the list. I was lookig for ways to find the HW bottleneck and saw a configuration like: "we recently upgraded our dual Xeon Dell to a brand new Sun v40z with 4 opterons, 16GB of memory and MegaRAID with enough disks. OS is Debian Sarge amd64, PostgreSQL is 8.0.3." on (http://archives.postgresql.org/pgsql-performance/2005-07/msg00431.php) Our old server was a very modest Dell Xeon 2.8 (512 Kb Cache), with 1 GB RAM and one SCSI disc. This server runs PostgreSQL (8.1.4), Apache (PHP) and other minor services. We managed to get a test machine, a HP Xeon 3.2 (2 MB cache), also with 1 GB RAM but 4 SCSI discs (in one sigle array controller). They're organized in the following way: disk 0: Linux Root disk 1: Database Cluster disk 2: pg_xlog disk 3: a dir the suffers constant read/write operations The database size stands around 10 GB. The new server has a better performance than the old one, but sometimes it still stucks. We tried to use a HP proprietary tool to monitor the server, and find out what is the bottleneck, but it's been difficult to install it on Debian. The tool is only certified for SuSe and RedHat. So we tried to use some Linux tools to see what's going on, like vmstat and iostat. Are this tools (vm and iostat) enough? Should we use something else? Is there any specifical material about finding bottlenecks in Linux/PostgreSQL machines? Is our disks design proper? I really apologize for my lack of knowledge in this area, and for the excessive number of questions in a single e-mail. Best regards, Alvaro