Performance Considerations; Configuring Software Raid - HP Z228 Maintenance And Service Manual

Table of Contents

of a failure). For all software RAID solutions on HP workstations, redundancy can be restored only after the

system is shut down so that the failed drive can be replaced. This replacement requires only a minimum

amount of work.

Performance considerations

Disk I/O bandwidth is typically limited by the system bus speeds, the disk controller, and the disks

themselves. The balance of these hardware limitations, as affected by the software configuration,

determines the location of the any bottleneck is in the system.

Several RAID levels offer improved performance relative to stand-alone disk performance. If disk throughput

is restricted because of a single disk controller, RAID can probably do little to improve performance until

another controller is added. Conversely, if raw disk performance is the bottleneck, a tuned software RAID

solution can dramatically improve the throughput. The slower disk performance is, relative to the rest of the

system, the better RAID performance will scale, because the slowest piece of the performance pipeline is

being directly addressed by moving to RAID.

See the following sites for additional information about configuring software RAID on Red Hat Enterprise

Linux (RHEL) or SUSE Linux Enterprise Desktop (SLED):

●

Red Hat Enterprise Linux 6—See the Storage Administration Guide at

US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/index.html

●

Red Hat Enterprise Linux 5—See the Deployment Guide at

Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/ch-raid.html.

●

SLED 11—See the Deployment Guide at

book_sle_deployment/?page=/documentation/sled11/book_sle_deployment/data/

book_sle_deployment.html.

Appendix B Configuring RAID devices

http://docs.redhat.com/docs/en-US/

http://www.suse.com/documentation/sled11/

http://docs.redhat.com/docs/en-

Table of Contents