X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 15CC1D1B241 for ; Tue, 29 Jun 2004 13:22:56 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 69323-05 for ; Tue, 29 Jun 2004 16:22:48 +0000 (GMT) Received: from snowwhite.lulu.com (stymie.lulu.com [66.193.5.50]) by svr1.postgresql.org (Postfix) with ESMTP id F41DED1B196 for ; Tue, 29 Jun 2004 13:22:45 -0300 (ADT) Received: from [10.0.0.32] (meatwad.rdu.lulu.com [10.0.0.32]) (authenticated) by snowwhite.lulu.com (8.11.6/8.11.6) with ESMTP id i5TGNB715143; Tue, 29 Jun 2004 12:23:11 -0400 Message-ID: <40E19752.7040509@lulu.com> Date: Tue, 29 Jun 2004 12:22:42 -0400 From: Bill Montgomery User-Agent: Mozilla Thunderbird 0.7 (X11/20040615) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-performance@postgresql.org Cc: eleven@ludojad.itpp.pl Subject: Re: High load average with PostgreSQL 7.4.2 on debian/ibm References: <20040629155537.GA5465@ludojad.itpp.pl> In-Reply-To: <20040629155537.GA5465@ludojad.itpp.pl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/305 X-Sequence-Number: 7363 eleven@ludojad.itpp.pl wrote: > <>I'm using PostgreSQL 7.4.2 (package from backports.org) > on a Debian (woody) box. The machine is IBM eServer 345 > with two 2.8 Xeon CPUs, it has 1024MB of RAM and > two 15k RPM SCSI disks running in hardware RAID1, which > is provided by the onboard LSI Logic controller (LSI53C1030). > <>With kernel 2.6.x which I was using earlier, > top showed very high "wa" values (which indicate I/O waiting, AFAIK) It sounds like you are very much bound by disk I/O. Your iostat output indicates a good amount of I/O going on--I bet an iostat -x /dev/sdX would show very high await times (time in ms before an IO request to the device is serviced). If your RAID controller has a battery-backed cache, check that you have write-back (as opposed to write-through) enabled. This will cause the controller to report data written only to RAID cache and not yet flushed to disk as sync'd. You can experience large gains in write performance this way. If write-back is already enabled, or enabling it does not give a large enough performance boost, you may need to buy more disks. In general, if you have the budget for lots of disks, RAID 10 is the best you can do performance-wise; if your budget for disks is limited, RAID 5 is the next best thing. Also, you will get more bang for your buck with a larger number of 10k disks than a smaller number of 15k disks. Good luck, Bill Montgomery