From: | Scott Carey <scott(at)richrelevance(dot)com> |
---|---|
To: | Andy <angelflow(at)yahoo(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, Greg Smith <greg(at)2ndquadrant(dot)com> |
Subject: | Re: Intel SSDs that may not suck |
Date: | 2011-04-07 00:20:21 |
Message-ID: | C9C25083.2EB4E%scott@richrelevance.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 4/6/11 2:11 PM, "Andy" <angelflow(at)yahoo(dot)com> wrote:
>
>--- On Wed, 4/6/11, Scott Carey <scott(at)richrelevance(dot)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.
1. People are complaining that the Intel G3's aren't as fast as the
SandForce drives (they are faster than the 1st gen SandForce, but not the
yet-to-be-released ones like Vertex 3). From a database perspective, this
is complete BS.
2. 256K versus 64MB write cache. Power + time to flush a cache matters.
3. None of the performance benchmarks of drives are comparing the
performance with the cache _disabled_ which is required when not power
safe. If the SandForce drives are still that much faster with it
disabled, I'd be shocked. Disabling a 256K write cache will affect
performance less than disabling a 64MB one.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Carey | 2011-04-07 00:22:01 | Re: Intel SSDs that may not suck |
Previous Message | Scott Carey | 2011-04-07 00:10:31 | Re: Intel SSDs that may not suck |