Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 85253B5DBD8 for ; Sun, 2 Oct 2011 21:44:32 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 79530-01 for ; Mon, 3 Oct 2011 00:44:26 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0-rc2 Received: from mail.nuevasync.com (server13-scl.nuevasync.com [64.13.157.153]) by mail.postgresql.org (Postfix) with ESMTP id 1D143B5DBD1 for ; Sun, 2 Oct 2011 21:44:25 -0300 (ADT) Received: from [69.145.82.243] (unknown [69.145.82.243]) by mail.nuevasync.com (Postfix) with ESMTP id 4403F2B195F for ; Sun, 2 Oct 2011 18:44:24 -0600 (MDT) Message-ID: <4E890565.3080400@boreham.org> Date: Sun, 02 Oct 2011 18:44:21 -0600 From: David Boreham User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2 MIME-Version: 1.0 To: "pgsql-performance@postgresql.org" Subject: Re: Suggestions for Intel 710 SSD test References: <4E87CEDF.3000504@boreham.org> <1317525762.87269.YahooMailNeo@web111315.mail.gq1.yahoo.com> <4E8821E9.9050002@tweakers.net> <4E88F4DB.4070306@boreham.org> <556E29CE-F51C-4A38-8362-3003A8D65593@mac.com> In-Reply-To: <556E29CE-F51C-4A38-8362-3003A8D65593@mac.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.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201110/10 X-Sequence-Number: 45232 On 10/2/2011 6:26 PM, Gregory Gerard wrote: > If I may ask what were your top three candidates before choosing the intel? All the other options considered viable were using traditional rotational disks. I personally don't have any confidence in the other SSD vendors today, except perhaps for FusionIO (where a couple of old friends work, and I can certainly vouch for their competence) but their products are too costly for our application at present. > > Also why not just plan a graceful switch to a replicated server? At some point you have to detect the drive is about to go (or it just goes without warning). Presumably that point will be in a while and be coordinated with an upgrade like 9.2 in a year. Sure, we have this capability but once you walk through what has to happen if you are burning through SSDs every few months, the 710 value proposition is more attractive for us. For example our data center is 1200 miles from our HQ and it takes a very long road trip or a plane flight to get hands-on with the boxes. We spent some considerable time planning for the 320 style deployment to be honest -- figuring out how to predict when the drive would wear out, building replication mechanisms that would cope gracefully and so on. But given the option of the 710 where wear out can essentially be crossed off the list of things to worry about, that's the way we decided to go. > > Finally why not the pci based cards? > Few reasons: 1) Today Intel doesn't make them (that will change soon), 2) a desire to maintain backwards compatibility at least for this generation, on a system architecture level with traditional disk drives, 3) concerns about mechanical integrity and system airflow issues with the PCI card and connector in 1U enclosures. The SSD fits into the same location as a traditional disk but can be velcro'ed down rather than bolted for easier field replacement.