Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id CEDA06326B4 for ; Sat, 24 Jul 2010 04:19:33 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 15207-01 for ; Sat, 24 Jul 2010 07:19:25 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f46.google.com (mail-ew0-f46.google.com [209.85.215.46]) by mail.postgresql.org (Postfix) with ESMTP id D21B463250C for ; Sat, 24 Jul 2010 04:19:25 -0300 (ADT) Received: by ewy23 with SMTP id 23so356661ewy.19 for ; Sat, 24 Jul 2010 00:19:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=5NQ3SV10Bq9sDyJwlEuBVpJS5lbNEd/dxfE4amQmT5c=; b=A726NCfeGrF8JfLjpJrhjALWMwX7I9Qg0e95w3md29UGTDDvhB6LsFRvBYibXlQg6f E7ywcTtfZlvNR5rhnxYmmAQys30dcBQaONiahyc/+SsYful57zcIKI70fjdmxpFIqq0z ef13ujALhsY+5POXPgc7kzy5GlunmwmEe9Ymw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=QoppN8laYqDkOJ3bXIejxfq0ohTymoa+z8GYaBagwh8hphewXKBiHbP/S/pP3RF/06 Ma61SlDebc73oGo9uwhWi2T+m9pNPq92IzH8Rf4s/WeWB4NRzNuxJH7JyQVGw0Y5OXx7 iWEcEyJzXE7j+NLePmubIYxIBmS/u8Z59lsDM= Received: by 10.213.26.70 with SMTP id d6mr4072855ebc.41.1279955964050; Sat, 24 Jul 2010 00:19:24 -0700 (PDT) Received: from [0.0.0.0] (5357DA75.cable.casema.nl [83.87.218.117]) by mx.google.com with ESMTPS id v59sm1686285eeh.16.2010.07.24.00.19.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 24 Jul 2010 00:19:23 -0700 (PDT) Message-ID: <4C4A9452.9070100@gmail.com> Date: Sat, 24 Jul 2010 09:20:50 +0200 From: Yeb Havinga User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Testing Sandforce SSD Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201007/350 X-Sequence-Number: 39739 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