From: Greg Smith <gsmith@gregsmith.com>
To: Guy Rouillier <guyr-ml1@burntmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Making the most of memory?
Date: Wed, 23 Jan 2008 19:54:24 -0500 (EST)
Message-ID: <Pine.GSO.4.64.0801231937090.12679@westnet.com> (raw)
In-Reply-To: <47979C15.3040406@burntmail.com>
References: <4796BE84.9030803@centriccrm.com>
<dcc563d10801222120q78e390dbj2b884eca729c2975@mail.gmail.com>
<B30794E6-CD2A-43C1-B431-E24B56FBFB1D@concursive.com>
<dcc563d10801231044p1dba892r9b8bf1269395f068@mail.gmail.com>
<47979C15.3040406@burntmail.com>
On Wed, 23 Jan 2008, Guy Rouillier wrote:
> Flash has a limited number of writes before it becomes unreliable. On
> good quality consumer grade, that's about 300,000 writes, while on
> industrial grade it's about 10 times that.
The main advance that's made SSD practical given the write cycle
limitation is increasing sophisticated wear leveling:
http://en.wikipedia.org/wiki/Wear_levelling
The best devices now use static wear levelling; overviews at
http://en.wikipedia.org/wiki/Static_Wear_Leveling and
http://www.storagesearch.com/siliconsys-art1.html
The basic idea is that the number of writes to each block is tracked, and
as it approaches the limit that block gets swapped with one that has been
more read-only. So essentially the number of writes before failure
approaches something closer to 1M x number of blocks. This means that as
the size of the device goes up, so does its longevity. If you believe the
hype, the combination in the increase in size of designs with these more
sophisticated wear-levelling approaches has now crossed the line where
it's more likely a standard moving-parts hard drive will fail first if you
compare it to a similarly sized SDD doing the same job (a standard
mechanical drive under heavy write load also wears out faster than one
doing less work).
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
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: gsmith@gregsmith.com, guyr-ml1@burntmail.com
Subject: Re: Making the most of memory?
In-Reply-To: <Pine.GSO.4.64.0801231937090.12679@westnet.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