In a RAID 5 array...

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

imported_Tick

Diamond Member
Feb 17, 2005
4,682
1
0
Originally posted by: TGS
Actually the XOR processor does most of the work in a hardware setup. The cache just helps you from becoming I/O limited in large bursts. Both of which are a product of a high I/O environment. Which the OP is not going to be.

edit:

i have hardware raid 5 u320 scsi.. its not over the top if you have over 1tb of data.. if i had less, i'd prob use raid 1 software

It really shouldn't matter how large the array is, except for parity purposes on very large arrays(IE numbers of drives, opposed to amount of data). The basis for hardware vs software is you will choke the processor with XOR parity calculations in a high I/O scenario. Where as with hardware the controllers onboard XOR processor handles all those transactions without having to take CPU time away from more critical OS functions. The purpose of the cache is to minimize the parity write penalty. The cache provides the buffer for data to be held while the parity calculations are going off in the background. Typically smaller controllers can be set to writeback immediately or stage the data off when the cache is reaching a certain point.

K. Informative.
 

Fullmetal Chocobo

Moderator<br>Distributed Computing
Moderator
May 13, 2003
13,704
7
81
Good thread while it lasted, but let it die if it needs to. Unless you have another question, or need some more help with something... But if you have to bump three times in a row, it's a sign. Especially in an hours time.
Tas.