From: David Boreham <david_list@boreham.org>
To: pgsql-performance@postgresql.org
Subject: Re: Choosing between Intel 320, Intel 510 or OCZ Vertex 3 SSD for db server
Date: Mon, 24 Oct 2011 20:37:05 -0600
Message-ID: <4EA620D1.5090008@boreham.org> (raw)
In-Reply-To: <CAGTBQpYLLDC=fiE=sWhZk7wTdxsmKBaFV4+voMD_RnpokvY8PQ@mail.gmail.com>
References: <CAPTAQB+VTVuk_fuDh2JLa9oDqwRONEMNfj1jBJiLw9rpmkAO2A@mail.gmail.com>
<4EA5980E.9050903@boreham.org>
<CAHyXU0zZxnznLuP+fytLHT6Wu257w7ysAyuALR0BVZ4JxYWROg@mail.gmail.com>
<CAGTBQpYLLDC=fiE=sWhZk7wTdxsmKBaFV4+voMD_RnpokvY8PQ@mail.gmail.com>
On 10/24/2011 4:47 PM, Claudio Freire wrote:
> What about redundancy?
>
> How do you swap an about-to-die SSD?
>
> Software RAID-1?
The approach we take is that we use 710 series devices which have
predicted reliability similar to all the other components in the
machine, therefore the unit of replacement is the entire machine. We
don't use trays for example (which saves quite a bit on data center
space). If I were running short endurance devices such as 320 series I
would be interested in replacing the drives before the machine itself is
likely to fail, but I'd do so by migrating the data and load to another
machine for the replacement to be done offline. Note that there are
other operations procedures that need to be done and can not be done
without downtime (e.g. OS upgrade), so some kind of plan to deliver
service while a single machine is down for a while will be needed
regardless of the storage device situation.
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: david_list@boreham.org
Subject: Re: Choosing between Intel 320, Intel 510 or OCZ Vertex 3 SSD for db server
In-Reply-To: <4EA620D1.5090008@boreham.org>
* 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