From: Yeb Havinga <yebhavinga@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Testing Sandforce SSD
Date: Sat, 24 Jul 2010 09:20:50 +0200
Message-ID: <4C4A9452.9070100@gmail.com> (raw)
Hello list,
Probably like many other's I've wondered why no SSD manufacturer puts a
small BBU on a SSD drive. Triggered by Greg Smith's mail
http://archives.postgresql.org/pgsql-performance/2010-02/msg00291.php
here, and also anandtech's review at
http://www.anandtech.com/show/2899/1 (see page 6 for pictures of the
capacitor) I ordered a SandForce drive and this week it finally arrived.
And now I have to test it and was wondering about some things like
* How to test for power failure? I thought by running on the same
machine a parallel pgbench setup on two clusters where one runs with
data and wal on a rotating disk, the other on the SSD, both without BBU
controller. Then turn off power. Do that a few times. The problem in
this scenario is that even when the SSD would show not data loss and the
rotating disk would for a few times, a dozen tests without failure isn't
actually proof that the drive can write it's complete buffer to disk
after power failure.
* How long should the power be turned off? A minute? 15 minutes?
* What filesystem to use on the SSD? To minimize writes and maximize
chance for seeing errors I'd choose ext2 here. For the sake of not
comparing apples with pears I'd have to go with ext2 on the rotating
data disk as well.
Do you guys have any more ideas to properly 'feel this disk at its teeth' ?
regards,
Yeb Havinga
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
Subject: Re: Testing Sandforce SSD
In-Reply-To: <4C4A9452.9070100@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