
1.6.6.8 Summary of RAID Performance Characteristics
∙
∙
∙
Fastest
Allows seek and drive latency to be performed in parallel Significantly outperforms single large disk
∙
∙
∙
∙
Fast and reliable, but requires 100% disk space overhead Data copied to each set of drives
No performance degradation with a single disk failure
∙
∙
Very fast for sequential applications, such as graphics modelling Almost never used with
∙
∙
∙
∙
∙
Access to all drives to retrieve one record Best for large sequential reads
Very poor for random transactions Poor for any write operations
Faster than a single drive, but much slower than
∙
∙
∙
Best for large sequential I/O Very poor write performance
Faster than a single drive, but usually much slower than
∙
∙
∙
∙
∙
Best for random transactions
Poor for large sequential reads if request is larger than block size Better write performance than
Block size is key to performance, must be larger than typical request size Performance degrades in recovery mode (when a single drive has failed)
Table 7. Summary of RAID Performance Characteristics
RAID Level | Capacity | Large Transfers | High I/O Rate | Data Availability |
|
|
|
|
|
Single Disk | Fixed (100%) | Good | Good | 1 |
|
|
|
|
|
Excellent | Very Good | Very Good | Poor 2 | |
|
|
|
|
|
Moderate (50%) | Good | Good | Good | |
|
|
|
|
|
Very Good | Good | Poor | Good | |
|
|
|
|
|
Very Good | Very Good | Poor | Good | |
|
|
|
|
|
Very Good | Very Good | Poor | Good | |
|
|
|
|
|
Very Good | Very Good | Good | Good | |
|
|
|
|
|
Note:
1The MTBF (mean time before failure) for single disks can range from 10,000 to 1,000,000 hours. 2Availability = MTBF of one disk divided by the number of disks in the array.
30NetWare Integration Guide