From: Jeff Davis <pgsql@j-davis.com>
To: Scott Carey <scott@richrelevance.com>
Cc: Michael March <mmarch@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Completely un-tuned Postgresql benchmark results: SSD vs desktop HDD
Date: Mon, 09 Aug 2010 15:41:59 -0700
Message-ID: <1281393719.3667.8.camel@jdavis-ux.asterdata.local> (raw)
In-Reply-To: <A1640F99-A7C5-4F04-9A25-782C46BE7DAB@richrelevance.com>
References: <AANLkTikXLYc32Jyr5Fb8VeVNt6R86mCcF+0CkTHALd8W@mail.gmail.com>
<BAE01AAD-6C69-48C7-BD2E-77E463D49903@richrelevance.com>
<AANLkTi=km+H+mZ=yyx0_HTFZ-yU2sh85D+p5cs+ZcUSF@mail.gmail.com>
<A1640F99-A7C5-4F04-9A25-782C46BE7DAB@richrelevance.com>
On Mon, 2010-08-09 at 09:49 -0700, Scott Carey wrote:
> Also, the amount of data at risk in a power loss varies between
> drives. For Intel's drives, its a small chunk of data ( < 256K). For
> some other drives, the cache can be over 30MB of outstanding writes.
> For some workloads this is acceptable -- not every application is
> doing financial transactions. Not every part of the system needs to
> be on an SSD either -- the WAL, and various table spaces can all have
> different data integrity and performance requirements.
I don't think it makes sense to speak about the data integrity of a
drive in terms of the amount of data at risk, especially with a DBMS.
Depending on which 256K you lose, you might as well lose your entire
database.
That may be an exaggeration, but the point is that it's not as simple as
"this drive is only risking 256K data loss per outage".
Regards,
Jeff Davis
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: pgsql@j-davis.com, scott@richrelevance.com, mmarch@gmail.com
Subject: Re: Completely un-tuned Postgresql benchmark results: SSD vs desktop HDD
In-Reply-To: <1281393719.3667.8.camel@jdavis-ux.asterdata.local>
* 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