From: | Ron <rjpeace(at)earthlink(dot)net> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: What's the best hardver for PostgreSQL 8.1? |
Date: | 2005-12-24 22:24:58 |
Message-ID: | 6.2.5.6.0.20051224171301.01dd4e00@earthlink.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
At 04:42 PM 12/24/2005, Joshua D. Drake wrote:
>>If you've got the budget or are dealing with small enough physical
>>storage needs, by all means use RAID 10. OTOH, if you are dealing
>>with large enterprise class apps like Sarbanes Oxley compliance,
>>medical and/or insurance, etc, etc, the storage needs can get so
>>large that RAID 10 for everything or even most things is not
>>possible. Even if economically feasible.
>>
>>RAID levels are like any other tool. Each is useful in the proper
>>circumstances.
>There is also RAID 50 which is quite nice.
The "quite nice" part that Joshua is referring to is that RAID 50
gets most of the write performance of RAID 10 w/o using nearly as
many HD's as RAID 10. OTOH, there still is a significant increase in
the number of HD's used, and that means MBTF's become more frequent
but you are not getting protection levels you would with RAID 10.
IME RAID 50 gets mixed reviews. My two biggest issues are
a= Admin of RAID 50 is more complex than the other commonly used
versions (1, 10, 5, and 6)
b= Once a HD failure takes place, you suffer a _permenent_
performance drop, even after the automatic volume rebuild, until you
take the entire RAID 50 array off line, reinitialize it, and rebuild
it from scratch.
IME "a" and "b" make RAID 50 inappropriate for any but the biggest
and most dedicated of DB admin groups.
YMMV,
Ron
From | Date | Subject | |
---|---|---|---|
Next Message | William Yu | 2005-12-24 22:36:57 | Re: What's the best hardver for PostgreSQL 8.1? |
Previous Message | David Lang | 2005-12-24 21:54:21 | Re: What's the best hardver for PostgreSQL 8.1? |