From: Greg Smith <greg@2ndquadrant.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Testing Sandforce SSD
Date: Mon, 02 Aug 2010 20:07:43 -0400
Message-ID: <4C575DCF.3050700@2ndquadrant.com> (raw)
In-Reply-To: <4C5744F5.3020805@agliodbs.com>
References: <4C4A9452.9070100@gmail.com>
<4C4B1F84.5030306@2ndquadrant.com>
<4C4B4B41.7000800@2ndquadrant.com>
<4C52E957.8020304@gmail.com>
<AANLkTinNX63EsRtNjtKeeygymWjH8VA3EWwxBzXGCy0=@mail.gmail.com>
<4C56DD8B.6050303@gmail.com>
<4C5744F5.3020805@agliodbs.com>
Josh Berkus wrote:
> That doesn't make much sense unless there's some special advantage to a
> 4K blocksize with the hardware itself.
Given that pgbench is always doing tiny updates to blocks, I wouldn't be
surprised if switching to smaller blocks helps it in a lot of situations
if one went looking for them. Also, as you point out, pgbench runtime
varies around wildly enough that 10% would need more investigation to
really prove that means something. But I think Yeb has done plenty of
investigation into the most interesting part here, the durability claims.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com www.2ndQuadrant.us
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: greg@2ndquadrant.com, josh@agliodbs.com
Subject: Re: Testing Sandforce SSD
In-Reply-To: <4C575DCF.3050700@2ndquadrant.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