Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UFyr7-0003U2-M2 for pgsql-performance@arkaria.postgresql.org; Thu, 14 Mar 2013 03:29:25 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UFyr6-00083F-Q1 for pgsql-performance@arkaria.postgresql.org; Thu, 14 Mar 2013 03:29:24 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UFyr5-00083A-V3 for pgsql-performance@postgresql.org; Thu, 14 Mar 2013 03:29:24 +0000 Received: from [2404:130:0:10::40:2] (helo=mail.catalyst.net.nz) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UFyr2-0005Mx-EY for pgsql-performance@postgresql.org; Thu, 14 Mar 2013 03:29:22 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.catalyst.net.nz (Postfix) with ESMTP id A63DB332F7 for ; Thu, 14 Mar 2013 16:29:15 +1300 (NZDT) X-Virus-Scanned: Debian amavisd-new at catalyst.net.nz Received: from mail.catalyst.net.nz ([127.0.0.1]) by localhost (bertrand.catalyst.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fw8oc9hIBhmS for ; Thu, 14 Mar 2013 16:29:14 +1300 (NZDT) Received: from [192.168.1.64] (122-60-64-230.jetstream.xtra.co.nz [122.60.64.230]) (Authenticated sender: mark.kirkwood) by mail.catalyst.net.nz (Postfix) with ESMTPSA id E3DB532D31 for ; Thu, 14 Mar 2013 16:29:13 +1300 (NZDT) Message-ID: <51414409.6090505@catalyst.net.nz> Date: Thu, 14 Mar 2013 16:29:13 +1300 From: Mark Kirkwood User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: New server setup References: <4D6D1410-2208-4DAA-BD64-69BE1FD94E55@autouncle.com> <513CADB7.4030803@2ndQuadrant.com> <51409C51.1070601@kickstone.com> <38D48FB0-92A8-433B-8D34-4C63738B45BA@gmail.com> <5140A623.20005@kickstone.com> <5140D226.4060609@pinpointresearch.com> <5140DE90.5010009@boreham.org> In-Reply-To: <5140DE90.5010009@boreham.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2404:130:0:10::40:2 (failed) X-Pg-Spam-Score: -1.1 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On 14/03/13 09:16, David Boreham wrote: > On 3/13/2013 1:23 PM, Steve Crawford wrote: >> >> What concerns me more than wear is this: >> >> InfoWorld Article: >> http://www.infoworld.com/t/solid-state-drives/test-your-ssds-or-risk-massive-data-loss-researchers-warn-213715 >> >> >> Referenced research paper: >> https://www.usenix.org/conference/fast13/understanding-robustness-ssds-under-power-fault >> >> >> Kind of messes with the "D" in ACID. > > It is somewhat surprising to discover that many SSD products are not > durable under sudden power loss (what where they thinking!?, and ...why > doesn't anyone care??). > > However, there is a set of SSD types known to be designed to address > power loss events that have been tested by contributors to this list. > Use only those devices and you won't see this problem. SSDs do have a > wear-out mechanism but wear can be monitored and devices replaced in > advance of failure. In practice longevity is such that most machines > will be in the dumpster long before the SSD wears out. We've had > machines running with several hundred wps constantly for 18 months using > Intel 710 drives and the wear level SMART value is still zero. > > In addition, like any electronics module (CPU, memory, NIC), an SSD can > fail so you do need to arrange for valuable data to be replicated. > As with old school disk drives, firmware bugs are a concern so you might > want to consider what would happen if all the drives of a particular > type all decided to quit working at the same second in time (I've only > seen this happen myself with magnetic drives, but in theory it could > happen with SSD). > > Just going through this now with a vendor. They initially assured us that the drives had "end to end protection" so we did not need to worry. I had to post stripdown pictures from Intel's s3700, showing obvious capacitors attached to the board before I was taken seriously and actually meaningful specifications were revealed. So now I'm demanding to know: - chipset (and version) - original manufacturer (for re-badged ones) - power off protection *explicitly* mentioned - show me the circuit board (and where are the capacitors) Seems like you gotta push 'em! Cheers Mark -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance