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

intensive workloads result in roughly double the CPU overhead (for example, from 15% to 30%). For most
applications, this overhead is easily handled by excess headroom in the processors. But for some applications
where disk and CPU performance are very well balanced and already near bottleneck levels, this additional
CPU overhead can become troublesome.
Hardware RAID offers advantages because of its large hardware cache and the capability for better
scheduling of operations in parallel. However, software RAID offers more flexibility for disk and disk controller
setup. Additionally, hardware RAID requires that a failed RAID controller must be replaced with an identical
model to avoid data loss, whereas software RAID imposes no such requirements.
Some software RAID schemes offer data protection through mirroring (copying the data to multiple disks in
case one disk fails) or parity data (checksums that allow error detection and limited rebuilding of data in case
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.

Configuring software RAID

See the following sites for additional information about configuring software RAID:
● Red Hat Enterprise Linux 7—See the Storage Administration Guide at
documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Storage_Administration_Guide/index.html
Red Hat Enterprise Linux 6—See the Storage Administration Guide at
●
US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/index.html
SLED 12—See the Deployment Guide at
●
book_sle_deployment/data/sec_yast2_system_raid.html.
SLED 11—See the Deployment Guide at
●
book_sle_deployment/?page=/documentation/sled11/book_sle_deployment/data/
book_sle_deployment.html.
● Ubuntu 14.04 LTS—See the Server Guide at
installation.html
SoftwareRAID.
For more information about Open Source and Linux at HP, go to
linux/index.html.
80 Appendix B Configuring RAID devices
https://www.suse.com/documentation/sled-12/
http://www.suse.com/documentation/sled11/
or the Community Wiki at
https://help.ubuntu.com/lts/serverguide/advanced-
https://help.ubuntu.com/community/Installation/
http://h10018.www1.hp.com/wwsolutions/
https://access.redhat.com/
http://docs.redhat.com/docs/en-