RAID 5 setups allow for getting the most storage out of an array of disks without loosing parity, or redundancy. For example.
Raid 5 array with four disks will have the capacity of three of those disks using the forth's pool of storage (over all the disks) as a parity bit so if one of the disks were to fail you would simply swap out the defective disk and the array will rebuild itself in an ideal world.
Because of this write speeds on RAID 5 arrays tend to be a bit slower then other arrays because it's spreading out it's data on however many disks you have any it's writing parity bits at the same time. Read speeds tend to be quick on RAID 5 making it ideal for archival use or data that must be read a lot but not edited much or changed. Think of a server dishing up programs to users or storing their finished work files.
Hope that helps!
raid 5
RAID 5
Raid 5
RAID 1, RAID 1 + 0, and RAID 5, 6.
Essentially that just means understanding what raid one and raid 5 are. Raid one stores the data on 2 hard disks, raid 5 stores the data on 3 to 5 disks. In either of these circumstances all the hard disks must be completely identical right down to brand cache, size etc.
For Raid 5 all the hard drives have to be of the same speed.
RAID controllers have a wide variety of benefits which apply to the cloud computing community. RAID essentially improves performance for programmers that need to compute various codes.
I did...
Every RAID level stripes data across multiple drives, which improves performance compared to using a single disk. RAID 0, RAID 1, RAID 1+0, RAID 5, RAID 6, etc. all have better performance than a single disk. Other than RAID 0, all other RAID levels provide fault tolerance. RAID 1, RAID 1+0, RAID 5, RAID 6, etc. all have fault tolerance.
RAID 1, RAID 0+1, RAID 5 and 6.
RAID 1 OR RAID 5 provide added performance as well as fault tolerance --- GAURAV TOMAR
steal