Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 0BC90B5DBE7 for ; Tue, 21 Jun 2011 04:52:19 -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 84934-01 for ; Tue, 21 Jun 2011 07:52:12 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f46.google.com (mail-ew0-f46.google.com [209.85.215.46]) by mail.postgresql.org (Postfix) with ESMTP id 35BF5B5DBE0 for ; Tue, 21 Jun 2011 04:52:12 -0300 (ADT) Received: by ewy4 with SMTP id 4so1457478ewy.19 for ; Tue, 21 Jun 2011 00:52:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DXhtlaRyjdRm3Wx9fuT5cBk/fPVD5IN2dczaOL+kiRY=; b=aIgT6Ve9x6rMt3GFruRA/gi0qpyp/mQr03Mz8TivBEeB0gHjVjva1ouyTBy71uugZx Kbg03ynCcCQxa+Wws2Ad2rLO95rKw954xz/5QE+M7xV6IEHPn01XfcDN5sgvJ4opt32M IL8t9Q2SCXp7bWWrPYlmti+dJJ+Fmbpgq+lEA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=V14cD5VBKSQIKRudhmyI/9dVwTr7risiK5GpORyMmIy2ZsDooLmUuVD4I5RnCSVG7p cm+9EGYU7HRBBOeLN5Kd19+oGAiyWvL8PGcWAJzNcc3n8KzeL+xbH+J+GoPjm2O5ngNQ 8Cc7xKVaplH7RGF1r/kB6hOEqUkCUHjdHbAYs= Received: by 10.14.50.196 with SMTP id z44mr2466765eeb.227.1308642729932; Tue, 21 Jun 2011 00:52:09 -0700 (PDT) Received: from [192.168.73.63] (5357DA75.cm-6-8d.dynamic.ziggo.nl [83.87.218.117]) by mx.google.com with ESMTPS id b19sm5201949eec.22.2011.06.21.00.52.08 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 21 Jun 2011 00:52:08 -0700 (PDT) Message-ID: <4E004D96.7010308@gmail.com> Date: Tue, 21 Jun 2011 09:51:50 +0200 From: Yeb Havinga User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Greg Smith CC: pgsql-performance@postgresql.org Subject: Re: Contemplating SSD Hardware RAID References: <4E0015F2.9060504@drivefaster.net> <4E003B44.9090005@2ndQuadrant.com> In-Reply-To: <4E003B44.9090005@2ndQuadrant.com> 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=-1.898 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RFC_ABUSE_POST=0.001 X-Spam-Level: X-Archive-Number: 201106/194 X-Sequence-Number: 44127 On 2011-06-21 08:33, Greg Smith wrote: > On 06/20/2011 11:54 PM, Dan Harris wrote: > >> I'm exploring the combination of an Areca 1880ix-12 controller with >> 6x OCZ Vertex 3 V3LT-25SAT3 2.5" 240GB SATA III drives in RAID-10. >> Has anyone tried this combination? What nasty surprise am I >> overlooking here? > > You can expect database corruption the first time something unexpected > interrupts the power to the server. That's nasty, but it's not > surprising--that's well documented as what happens when you run > PostreSQL on hardware with this feature set. You have to get a Vertex > 3 Pro to get one of the reliable 3rd gen designs from them with a > supercap. (I don't think those are even out yet though) We've had > reports here of the earlier Vertex 2 Pro being fully stress tested and > working out well. I wouldn't even bother with a regular Vertex 3, > because I don't see any reason to believe it could be reliable for > database use, just like the Vertex 2 failed to work in that role. > I've tested both the Vertex 2, Vertex 2 Pro and Vertex 3. The vertex 3 pro is not yet available. The vertex 3 I tested with pgbench didn't outperform the vertex 2 (yes, it was attached to a SATA III port). Also, the vertex 3 didn't work in my designated system until a firmware upgrade that came available ~2.5 months after I purchased it. The support call I had with OCZ failed to mention it, and by pure coincidende when I did some more testing at a later time, I ran the firmware upgrade tool (that kind of hides which firmwares are available, if any) and it did an update, after that it was compatible with the designated motherboard. Another disappointment was that after I had purchased the Vertex 3 drive, OCZ announced a max-iops vertex 3. Did that actually mean I bought an inferior version? Talking about a bad out-of-the-box experience. -1 ocz fan boy. When putting such a SSD up for database use I'd only consider a vertex 2 pro (for the supercap), paired with another SSD of a different brand with supercap (i.e. the recent intels). When this is done on a motherboard with > 1 sata controller, you'd have controller redundancy and can also survive single drive failures when a drive wears out. Having two different SSD versions decreases the chance of both wearing out the same time, and make you a bit more resilient against firmware bugs. It would be great if there was yet another supercapped SSD brand, with a modified md software raid that reads all three drives at once and compares results, instead of the occasional check. If at least two drives agree on the contents, return the data. -- Yeb Havinga http://www.mgrid.net/ Mastering Medical Data