From: John Lister <john.lister@kickstone.com>
To: Greg Jaskiewicz <gryzman@gmail.com>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: New server setup
Date: Wed, 13 Mar 2013 16:15:31 +0000
Message-ID: <5140A623.20005@kickstone.com> (raw)
In-Reply-To: <38D48FB0-92A8-433B-8D34-4C63738B45BA@gmail.com>
References: <4D6D1410-2208-4DAA-BD64-69BE1FD94E55@autouncle.com>
<513CADB7.4030803@2ndQuadrant.com>
<CAJY59_jNGwrPceXg8k04=1VWTTZTFTPTh+jGHopx92c+17Cj1w@mail.gmail.com>
<51409C51.1070601@kickstone.com>
<38D48FB0-92A8-433B-8D34-4C63738B45BA@gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 13/03/2013 15:50, Greg Jaskiewicz wrote:
> SSDs have much shorter life then spinning drives, so what do you do when one inevitably fails in your system ?
Define much shorter? I accept they have a limited no of writes, but that
depends on load. You can actively monitor the drives "health" level in
terms of wear using smart and it is relatively straightforward to
calculate an estimate of life based on average use and for me that works
out at about in excess of 5 years. Experience tells me that spinning
drives have a habit of failing in that time frame as well :( and in 5
years I'll be replacing the server probably.
I also overprovisioned the drives by about an extra 13% giving me 20%
spare capacity when adding in the 7% manufacturer spare space - given
this currently my drives have written about 4TB of data each and show 0%
wear, this is for 160GB drives. I actively monitor the wear level and
plan to replace the drives when they get low. For a comparison of write
levels see
http://www.xtremesystems.org/forums/showthread.php?271063-SSD-Write-Endurance-25nm-Vs-34nm,
it shows for the 320series that it reported to have hit the wear limit
at 190TB (for a drive 1/4 the size of mine) but actually managed nearer
700TB before the drive failed.
I've mixed 2 different manufacturers in my raid 10 pairs to mitigate
against both pairs failing at the same time either due to a firmware bug
or being full In addition when I was setting the box up I did some
performance testing against the drives but with using different
combinations for each test - the aim here is to pre-load each drive
differently to prevent them failing when full simultaneously.
If you do go for raid 10 make sure to have a power fail endurance, ie
capacitor or battery on the drive.
John
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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: john.lister@kickstone.com, gryzman@gmail.com
Subject: Re: New server setup
In-Reply-To: <5140A623.20005@kickstone.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