pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: david@lang.hm
To: David Boreham <david_list@boreham.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Testing Sandforce SSD
Date: Sat, 24 Jul 2010 01:25:38 -0700 (PDT)
Message-ID: <alpine.DEB.2.00.1007240123370.25170@asgard.lang.hm> (raw)
In-Reply-To: <4C4A981D.2000605@boreham.org>
References: <4C4A9452.9070100@gmail.com>
	<4C4A981D.2000605@boreham.org>

On Sat, 24 Jul 2010, David Boreham wrote:

>> Do you guys have any more ideas to properly 'feel this disk at its teeth' ?
>
> While an 'end-to-end' test using PG is fine, I think it would be easier to 
> determine if the drive is behaving correctly by using a simple test program 
> that emulates the storage semantics the WAL expects. Have it write a constant 
> stream of records, fsync'ing after each write. Record the highest record 
> number flushed so far in some place that won't be lost with the drive under 
> test (e.g. send it over the network to another machine).
>
> Kill the power, bring the system back up again and examine what's at the tail 
> end of that file. I think this will give you the worst case test with the 
> easiest result discrimination.
>
> If you want to you could add concurrent random writes to another file for 
> extra realism.
>
> Someone here may already have a suitable test program. I know I've written 
> several over the years in order to test I/O performance, prove the existence 
> of kernel bugs, and so on.
>
> I doubt it matters much how long the power is turned of. A second should be 
> plenty time to flush pending writes if the drive is going to do so.

remember that SATA is designed to be hot-plugged, so you don't have to 
kill the entire system to kill power to the drive.

this is a little more ubrupt than the system loosing power, but in terms 
of loosing data this is about the worst case (while at the same time, it 
eliminates the possibility that the OS continues to perform writes to the 
drive as power dies, which is a completely different class of problems, 
independant of the drive type)

David Lang



view thread (60+ messages)  latest in thread

Message-ID: <alpine.DEB.2.00.1007240123370.25170@asgard.lang.hm>
Permalink:  ../alpine.DEB.2.00.1007240123370.25170@asgard.lang.hm/
Also on:    postgresql.org/message-id/alpine.DEB.2.00.1007240123370.25170@asgard.lang.hm

 · 

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: david@lang.hm, david_list@boreham.org
  Subject: Re: Testing Sandforce SSD
  In-Reply-To: <alpine.DEB.2.00.1007240123370.25170@asgard.lang.hm>
  References: <4C4A9452.9070100@gmail.com> <4C4A981D.2000605@boreham.org> <alpine.DEB.2.00.1007240123370.25170@asgard.lang.hm>

* 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