pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Yeb Havinga <yebhavinga@gmail.com>
To: Greg Smith <greg@2ndQuadrant.com>
Cc: Florian Weimer <fweimer@bfk.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: Contemplating SSD Hardware RAID
Date: Tue, 21 Jun 2011 22:25:47 +0200
Message-ID: <4E00FE4B.3030204@gmail.com> (raw)
In-Reply-To: <4E00FABB.6030302@gmail.com>
References: <4E0015F2.9060504@drivefaster.net>
	<4E003B44.9090005@2ndQuadrant.com>
	<4E004D96.7010308@gmail.com>
	<4E004E74.5020209@gmail.com>
	<82d3i777ow.fsf@mid.bfk.de>
	<4E00B4B9.50006@2ndQuadrant.com>
	<4E00FABB.6030302@gmail.com>

On 2011-06-21 22:10, Yeb Havinga wrote:
>
>
> There's some info burried in 
> http://archives.postgresql.org/pgsql-performance/2011-03/msg00350.php 
> where two Vertex 2 pro's are compared; the first has been really 
> hammered with pgbench, the second had a few months duty in a 
> workstation. The raw value of SSD Available Reserved Space seems to be 
> a good candidate to watch to go to 0, since the pgbenched-drive has 
> 16GB left and the workstation disk 17GB. Would be cool to graph with 
> e.g. symon (http://i.imgur.com/T4NAq.png)
>

I forgot to mention that both newest firmware of the drives as well as 
svn versions of smartmontools are advisable, before figuring out what 
all those strange values mean. It's too bad however that OCZ doesn't let 
the user choose which firmware to run (the tool always picks the 
newest), so after every upgrade it'll be a surprise what values are 
supported or if any of the values are reset or differently interpreted. 
Even when disks in production might not be upgraded eagerly, replacing a 
faulty drive means that one probably needs to be upgraded first and it 
would be nice to have a uniform smart value readout for the monitoring 
tools.

-- 
Yeb Havinga
http://www.mgrid.net/
Mastering Medical Data




view thread (13+ messages)  latest in thread

Message-ID: <4E00FE4B.3030204@gmail.com>
Permalink:  ../4E00FE4B.3030204@gmail.com/
Also on:    postgresql.org/message-id/4E00FE4B.3030204@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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: yebhavinga@gmail.com, greg@2ndQuadrant.com, fweimer@bfk.de
  Subject: Re: Contemplating SSD Hardware RAID
  In-Reply-To: <4E00FE4B.3030204@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