On Thu, Nov 11, 2010 at 4:35 PM, Vick Khera <vivek@khera.org> wrote:
> On Thu, Nov 11, 2010 at 1:42 AM, Allan Kamau <kamauallan@gmail.com> wrote:
>> After googling I found little resent content (including survival
>> statistics) of using SSDs in a write intensive database environment.
>>
>
> We use the Texas Memory RAMSan-620 external disk units. It is
> designed specifically to survive high write loads, and uses internal
> monitoring and load leveling and spare parts with internal RAID
> configuration to keep from losing data in the eventual case when the
> SSD chips wear out. When that happens, you just swap out the failed
> piece and it keeps humming along.
>
> I wouldn't trust an SSD as a stand-alone drive for a DB. At minimum,
> I'd RAID1 them using the SATA controller... but be sure to get SATA3
> or even better SAS connected drives if you want to maximize the speed.
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From what I see from the responses it would be advisable to try ignore
the SSDs for now as there are other disk based alternatives such as
the VelociRaptor that seem in some cases to match half of the
performance of the SSDs not to mention that my application requires
expensive data writing.
Thank you all.
Allan
