pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: gnuoytr@rcn.com
To: pgsql-performance@postgresql.org
Subject: Re: Reports from SSD purgatory
Date: Wed, 24 Aug 2011 14:48:09 -0400 (EDT)
Message-ID: <201108241848.061232@ms14.lnh.mail.rcn.net> (raw)
In-Reply-To: <4E49B0A0.2060705@2ndQuadrant.com>
References: <4E49B0A0.2060705@2ndQuadrant.com>



---- Original message ----
>Date: Mon, 15 Aug 2011 19:49:52 -0400
>From: pgsql-performance-owner@postgresql.org (on behalf of Greg Smith <greg@2ndQuadrant.com>)
>Subject: [PERFORM] Reports from SSD purgatory  
>To: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
>
>News update for anyone else who's trapped like me, waiting for a fix to 
>the Intel 320 SSD bug where they can truncate themselves to 8MB.  Over 
>the weekend Intel has announced a firmware fix for the problem is done, 
>and is due to ship "within the next two weeks":  
>http://communities.intel.com/thread/24121
>
>On the larger SSD reliability front, Tom's Hardware surveyed heavy SSD 
>users they're friendly with who use Intel drives.  The most interesting 
>data came from Softlayer:  
>http://www.tomshardware.com/reviews/ssd-reliability-failure-rate,2923-6.html
>
>This supports two claims I made before based on my private data that 
>were controversial:
>
>-Annualized SSD failure rates are not significantly lower than 
>traditional drives in the first couple of years.  Jury is still out on 
>whether they will spike upwards starting at 3 years as mechanical ones do.
>
>-The most common source of dead drives is sudden, catastrophic 
>electronics failure.  These are not predicted by SMART, and have nothing 
>to do with hitting the drive's wear limits.

It's worth knowing exactly what that means.  Turns out that NAND quality is price specific.  There's gooduns and baduns.  Is this a failure in the controller(s) or the NAND?

Also, given that PG is *nix centric and support for TRIM is win centric, having that makes a big difference in performance.  


>
>-- 
>Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
>PostgreSQL Training, Services, and 24x7 Support  www.2ndQuadrant.us
>
>
>-- 
>Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-performance



view thread (13+ messages)  latest in thread

Message-ID: <201108241848.061232@ms14.lnh.mail.rcn.net>
Permalink:  ../201108241848.061232@ms14.lnh.mail.rcn.net/
Also on:    postgresql.org/message-id/201108241848.061232@ms14.lnh.mail.rcn.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: gnuoytr@rcn.com
  Subject: Re: Reports from SSD purgatory
  In-Reply-To: <201108241848.061232@ms14.lnh.mail.rcn.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox