pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Merlin Moncure <mmoncure@gmail.com>
To: Matthew Wakeling <matthew@flymine.org>
Cc: Vivek Khera <vivek@khera.org>
Cc: Pgsql performance <pgsql-performance@postgresql.org>
Subject: Re: Hardware vs Software RAID
Date: Thu, 26 Jun 2008 13:35:09 -0400
Message-ID: <b42b73150806261035y34802356hfaf9f9a366a00c8a@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806261705280.4085@aragorn.flymine.org>
References: <200806251311.m5PDBNv23559@inv.it.uc3m.es>
	<Pine.GSO.4.64.0806251051060.29204@westnet.com>
	<Pine.LNX.4.64.0806251631520.4085@aragorn.flymine.org>
	<97454AF8-315A-4B3D-8F95-D96B190C6909@khera.org>
	<Pine.LNX.4.64.0806261705280.4085@aragorn.flymine.org>

On Thu, Jun 26, 2008 at 12:14 PM, Matthew Wakeling <matthew@flymine.org> wrote:
>> None of these manufacturers rates these drives for massive amounts of
>> writes. They're sold as suitable for laptop/desktop use, which normally is
>> not a heavy wear and tear operation like a DB.  Once they claim suitability
>> for this purpose, be sure that I and a lot of others will dive into it to
>> see how well it really works.  Until then, it will just be an expensive
>> brick-making experiment, I'm sure.
>
> It claims a MTBF of 2,000,000 hours, but no further reliability information
> seems forthcoming. I thought the idea that flash couldn't cope with many
> writes was no longer true these days?

Flash and disks have completely different failure modes, and you can't
do apples to apples MTBF comparisons.  In addition there are many
different types of flash (MLC/SLC) and the flash cells themselves can
be organized in particular ways involving various trade-offs.

The best flash drives combined with smart wear leveling are
anecdotally believed to provide lifetimes that are good enough to
warrant use in high duty server environments.  The main issue is lousy
random write performance that basically makes them useless for any
kind of OLTP operation.  There are a couple of software (hacks?) out
there which may address this problem if the technology doesn't get
there first.

If the random write problem were solved, a single ssd would provide
the equivalent of a stack of 15k disks in a raid 10.

see:
http://www.bigdbahead.com/?p=44
http://feedblog.org/2008/01/30/24-hours-with-an-ssd-and-mysql/

merlin



view thread (32+ messages)  latest in thread

Message-ID: <b42b73150806261035y34802356hfaf9f9a366a00c8a@mail.gmail.com>
Permalink:  ../b42b73150806261035y34802356hfaf9f9a366a00c8a@mail.gmail.com/
Also on:    postgresql.org/message-id/b42b73150806261035y34802356hfaf9f9a366a00c8a@mail.gmail.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: mmoncure@gmail.com, matthew@flymine.org, vivek@khera.org
  Subject: Re: Hardware vs Software RAID
  In-Reply-To: <b42b73150806261035y34802356hfaf9f9a366a00c8a@mail.gmail.com>
  References: <200806251311.m5PDBNv23559@inv.it.uc3m.es> <Pine.GSO.4.64.0806251051060.29204@westnet.com> <Pine.LNX.4.64.0806251631520.4085@aragorn.flymine.org> <97454AF8-315A-4B3D-8F95-D96B190C6909@khera.org> <Pine.LNX.4.64.0806261705280.4085@aragorn.flymine.org> <b42b73150806261035y34802356hfaf9f9a366a00c8a@mail.gmail.com>

* 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