Re: Reports from SSD purgatory

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Tomas Vondra <tv(at)fuzzy(dot)cz>
Cc: gnuoytr(at)rcn(dot)com, pgsql-performance(at)postgresql(dot)org
Subject: Re: Reports from SSD purgatory
Date: 2011-08-24 19:41:47
Message-ID: CAHyXU0zDA+3naKPdVf5h9=gOSWPwPa2fUc+Psbwna5SgUU3TAw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wed, Aug 24, 2011 at 2:32 PM, Tomas Vondra <tv(at)fuzzy(dot)cz> wrote:
> On 24 Srpen 2011, 20:48, gnuoytr(at)rcn(dot)com wrote:
>
>> It's worth knowing exactly what that means.  Turns out that NAND quality
>> is price specific.  There's gooduns and baduns.  Is this a failure in the
>> controller(s) or the NAND?
>
> Why is that important? It's simply a failure of electronics and it has
> nothing to do with the wear limits. It simply fails without prior warning
> from the SMART.
>
>> Also, given that PG is *nix centric and support for TRIM is win centric,
>> having that makes a big difference in performance.
>
> Windows specific? What do you mean? TRIM is a low-level way to tell the
> drive 'this block is empty and may be used for something else' - it's just
> another command sent to the drive. It has to be supported by the
> filesystem, though (e.g. ext4/btrfs support it).

Well, it's a fair point that TRIM support is probably more widespread
on windows.

merlin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message gnuoytr 2011-08-24 19:42:05 Re: Reports from SSD purgatory
Previous Message Tomas Vondra 2011-08-24 19:32:16 Re: Reports from SSD purgatory