From: Scott Carey <scott@richrelevance.com>
To: Jeff <threshar@torgo.978.org>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: Andy <angelflow@yahoo.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Cc: Greg Smith <greg@2ndquadrant.com>
Subject: Re: Intel SSDs that may not suck
Date: Wed, 6 Apr 2011 17:05:28 -0700
Message-ID: <C9C22157.2E93A%scott@richrelevance.com> (raw)
In-Reply-To: <8BE8F356-319F-4BE7-BE66-F45D50235985@torgo.978.org>
On 3/29/11 7:16 AM, "Jeff" <threshar@torgo.978.org> wrote:
>
>The write degradation could probably be monitored looking at svctime
>from sar. We may be implementing that in the near future to detect
>when this creeps up again.
For the X25-M's, overcommit. Do a secure erase, then only partition and
use 85% or so of the drive (~7% is already hidden). This helps a lot with
the write performance over time. The Intel rep claimed that the new G3's
are much better at limiting the occasional write latency, by splitting
longer delays into slightly more frequent smaller delays.
Some of the benchmark reviews have histograms that demonstrate this
(although the authors of the review only note average latency or
throughput, the deviations have clearly gone down in this generation).
I'll know more for sure after some benchmarking myself.
>
>
>--
>Jeff Trout <jeff@jefftrout.com>
>http://www.stuarthamm.net/
>http://www.dellsmartexitin.com/
>
>
>
>
>--
>Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-performance
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: scott@richrelevance.com, threshar@torgo.978.org, mmoncure@gmail.com, angelflow@yahoo.com, greg@2ndquadrant.com
Subject: Re: Intel SSDs that may not suck
In-Reply-To: <C9C22157.2E93A%scott@richrelevance.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