Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 6893B632A6A for ; Wed, 3 Mar 2010 09:52:03 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 21765-08 for ; Wed, 3 Mar 2010 13:51:52 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from madmax.bizintegrators.com (madmax.bizintegrators.com [64.94.184.54]) by mail.postgresql.org (Postfix) with ESMTP id F16786325E1 for ; Wed, 3 Mar 2010 09:51:52 -0400 (AST) Received: from shelca (p65-147.acedsl.com [66.114.65.147]) (authenticated bits=0) by madmax.bizintegrators.com (8.13.4/8.13.4) with ESMTP id o23Dpmkd030798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Mar 2010 08:51:49 -0500 (EST) References: <4B8D7A6C.3010304@gmail.com> <4B8E2FA9.4010109@gmail.com> Message-ID: X-Mailer: http://www.courier-mta.org/cone/ From: Francisco Reyes To: Yeb Havinga Cc: Pgsql performance Subject: Re: 10K vs 15k rpm for analytics Date: Wed, 03 Mar 2010 08:51:56 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Loftmail-Check: No X-Scanned-By: MIMEDefang 2.57 on 64.94.184.88 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=-10 required=5 tests=BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 201003/57 X-Sequence-Number: 37882 Yeb Havinga writes: > controllers. Also, I am not sure if it is wise to put the WAL on the > same logical disk as the indexes, If I only have two controllers would it then be better to put WAL on the first along with all the data and the indexes on the external? Specially since the external enclosure will have 15K rpm vs 10K rpm in the internal. > thread (unwise to mix random and sequential io and also the wal has > demands when it comes to write cache). Thanks for pointing that out. With any luck I will actually be able to do some tests for the new hardware. The curernt one I literaly did a few hours stress test and had to put in production right away.