Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 7B111632FF7 for ; Tue, 2 Mar 2010 19:44:37 -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 70793-09 for ; Tue, 2 Mar 2010 23:44:26 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mail.postgresql.org (Postfix) with ESMTP id C86A4632D02 for ; Tue, 2 Mar 2010 19:44:26 -0400 (AST) Received: from [192.168.1.3] (pool-96-244-14-10.bltmmd.fios.verizon.net [96.244.14.10]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0LoKJV-1NFDws0HQ9-00g9MT; Wed, 03 Mar 2010 00:44:25 +0100 Message-ID: <4B8DA2D4.8000501@2ndquadrant.com> Date: Tue, 02 Mar 2010 18:44:20 -0500 From: Greg Smith User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Francisco Reyes CC: Yeb Havinga , Pgsql performance Subject: Re: 10K vs 15k rpm for analytics References: <4B8D7A6C.3010304@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+/04YMTVC3TkRBAq3AYRckp96jtcwUBcqVWds n7BqzZ+ii2BOSGhBmzGGcXXk7RkPKBkZtKO/bp6GjxPp0osLtW ILAEsDpUsEjLz8DQKkp2DdugIViBgz/ X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.185 tagged_above=-10 required=5 tests=BAYES_40=-0.185 X-Spam-Level: X-Archive-Number: 201003/42 X-Sequence-Number: 37867 Francisco Reyes wrote: > Going with a 3Ware SAS controller. > Already have simmilar machine in house. > With RAID 1+0 Bonne++ reports around 400MB/sec sequential read. Increase read-ahead and I'd bet you can add 50% to that easy--one area the 3Ware controllers need serious help, as they admit: http://www.3ware.com/kb/article.aspx?id=11050 Just make sure you ignore their dirty_ratio comments--those are completely the opposite of what you want on a database app. Still seems on the low side though. Short stroke and you could probably chop worst-case speeds in half too, on top of that. Note that 3Ware's controllers have seriously limited reporting on drive data when using SAS drives because they won't talk SMART to them: http://www.3ware.com/KB/Article.aspx?id=15383 I consider them still a useful vendor for SATA controllers, but would never buy a SAS solution from them again until this is resolved. -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us