Re: Reports from SSD purgatory - Mailing list pgsql-performance

From Tomas Vondra
Subject Re: Reports from SSD purgatory
Date
Msg-id d32d411b09d8e7c614772de567a94229.squirrel@sq.gransy.com
Whole thread Raw
In response to Re: Reports from SSD purgatory  (<gnuoytr@rcn.com>)
Responses Re: Reports from SSD purgatory  (Merlin Moncure <mmoncure@gmail.com>)
Re: Reports from SSD purgatory  (<gnuoytr@rcn.com>)
Re: Reports from SSD purgatory  (David Boreham <david_list@boreham.org>)
List pgsql-performance
On 24 Srpen 2011, 20:48, gnuoytr@rcn.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).

Tomas


pgsql-performance by date:

Previous
From: david@lang.hm
Date:
Subject: Re: Reports from SSD purgatory
Next
From: Merlin Moncure
Date:
Subject: Re: Reports from SSD purgatory