Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 261E6B5DC1A for ; Wed, 14 Sep 2011 05:22:16 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 12093-08 for ; Wed, 14 Sep 2011 08:22:09 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0-rc2 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mail.postgresql.org (Postfix) with ESMTP id D239AB5DBC4 for ; Wed, 14 Sep 2011 05:22:08 -0300 (ADT) Received: from [75.207.132.212] (212.sub-75-207-132.myvzw.com [75.207.132.212]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0MWQME-1Qbd5h0kuo-00X1hp; Wed, 14 Sep 2011 10:22:07 +0200 Message-ID: <4E70561D.5090909@2ndQuadrant.com> Date: Wed, 14 Sep 2011 03:22:05 -0400 From: Greg Smith User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110818 Icedove/3.0.11 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: RAID Controller (HP P400) beat by SW-RAID? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:uIuyM44Oa09jRuWqdhuWFaEGAkpdYN0a+3mCLJLdpZT KLqNn5/MG9rYtF7npuoSivw4zPV/05fEKiM1qYlH8XAqtUKWpj Vtj0gyM1FearZR7qH2aQ1RCkdoDndMtlNA+KVT505C6rPYMkCt EVvSzU+ymXxVELOjWjsHGAnzLzJt47yYsEXT4XPQZ4iVfMcsxl l2rPcmvp8ko4VAD611c0Cya2a0iSyqPdGzl/kBH1EC6CcYeOFa smcw10cN1bBhEucyDHcEnXQhWmpg+hpJi386jxl+2bjFuQAcm6 Z0fU/Siq81HQfPhCmfCAYHm5PjW4Me5C7uRuz9GPQd2qF4qIlQ eD14Z8ohtX8burEHeJDekuafOcJ0OsBcgE9cmkkjC X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201109/206 X-Sequence-Number: 44982 On 09/11/2011 06:44 PM, Anthony Presley wrote: > We've currently got PG 8.4.4 running on a whitebox hardware set up, > with (2) 5410 Xeon's, and 16GB of RAM. It's also got (4) 7200RPM SATA > drives, using the onboard IDE controller and ext3. > > A few weeks back, we purchased two refurb'd HP DL360's G5's, and were > hoping to set them up with PG 9.0.2, running replicated. These > machines have (2) 5410 Xeon's, 36GB of RAM, (6) 10k SAS drives, and > are using the HP SA P400i with 512MB of BBWC. PG is running on an > ext4 (noatime) partition, and they drives configured as RAID 1+0 > (seems with this controller, I cannot do JBOD). . > To start with, I've set the "relevant" parameters in postgresql.conf > the same on the new config as the old: > > fsync = on > synchronous_commit = off The main thing that a hardware RAID controller improves on is being able to write synchronous commits much faster than you can do without one. If you've turned that off, you've essentially neutralized its primary value. In every other respect, software RAID is faster: the CPUs in your server are much faster than the IO processor on the card, and Linux has a lot more memory for caching than it does too. Turning off sync commit may be fine for loading, but you'll be facing data loss at every server interruption if you roll things out like that. It's not realistic production performance for most places running like that. A lot of your test results seem like they may be using different levels of write reliability, which makes things less fair than they should be too--in favor of the cheap IDE drives normally. Check out http://wiki.postgresql.org/wiki/Reliable_Writes for more information about that topic. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us