From: Scott Carey <scott@richrelevance.com>
To: gnuoytr@rcn.com <gnuoytr@rcn.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Intel SSDs that may not suck
Date: Wed, 6 Apr 2011 17:22:01 -0700
Message-ID: <C9C25160.2EB61%scott@richrelevance.com> (raw)
In-Reply-To: <201104062303.060548@ms14.lnh.mail.rcn.net>
On 4/6/11 4:03 PM, "gnuoytr@rcn.com" <gnuoytr@rcn.com> wrote:
>Not for user data, only controller data.
>
False. I used to think so, but there is volatile write cache for user
data -- its on the 256K chip SRAM not the DRAM though.
Simple power failure tests demonstrate that you lose data with these
drives unless you disable the cache. Disabling the cache roughly drops
write performance by a factor of 3 to 4 on G1 drives and significantly
hurts wear-leveling and longevity (I haven't tried G2's).
>
>
>---- Original message ----
>>Date: Wed, 6 Apr 2011 14:11:10 -0700 (PDT)
>>From: pgsql-performance-owner@postgresql.org (on behalf of Andy
>><angelflow@yahoo.com>)
>>Subject: Re: [PERFORM] Intel SSDs that may not suck
>>To: Merlin Moncure <mmoncure@gmail.com>,Scott Carey
>><scott@richrelevance.com>
>>Cc: "pgsql-performance@postgresql.org"
>><pgsql-performance@postgresql.org>,Greg Smith <greg@2ndquadrant.com>
>>
>>
>>--- On Wed, 4/6/11, Scott Carey <scott@richrelevance.com> wrote:
>>
>>
>>> I could care less about the 'fast' sandforce drives.
>>> They fail at a high
>>> rate and the performance improvement is BECAUSE they are
>>> using a large,
>>> volatile write cache.
>>
>>The G1 and G2 Intel MLC also use volatile write cache, just like most
>>SandForce drives do.
>>
>>--
>>Sent via pgsql-performance mailing list
>>(pgsql-performance@postgresql.org)
>>To make changes to your subscription:
>>http://www.postgresql.org/mailpref/pgsql-performance
>
>--
>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, gnuoytr@rcn.com
Subject: Re: Intel SSDs that may not suck
In-Reply-To: <C9C25160.2EB61%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