23.07.2014 Views

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

10.2 Insights into Disk Performance<br />

Measurement<br />

Several tips and insights for disk performance measurement are provided below.<br />

Some of this information is specific to RAID arrays and/or the Linux RAID<br />

implementation.<br />

■ Performance is limited by the slowest disk.<br />

Benchmark all disks individually. We have frequently encountered situations<br />

where drive performance was not consistent for all devices in the array.<br />

Note – On a Thumper system with the out-of-tree Marvell driver, disk ordering is<br />

not preserved between boots (but controller ordering is). Perform a sgp_dd survey<br />

and create arrays without rebooting in-between.<br />

■<br />

■<br />

■<br />

Disks and arrays are very sensitive to request size.<br />

To identify the optimal request size for a given disk, benchmark the disk with<br />

different record sizes ranging from 4 KB to 1 to 2 MB.<br />

By default, the maximum size of a request is quite small.<br />

To properly handle I/O request sizes greater than 256 KB, the current Linux<br />

kernel needs either a driver patch or several changes in the block layer defaults,<br />

namely MAX_SECTORS, MAX_PHYS_SEGMENTS and MAX_HW_SEGMENTS.<br />

Select the best I/O scheduler for your setup.<br />

Try different I/O schedulers (kernel parameter elevator= on old kernels or echo<br />

>/sys/block//queue/scheduler), because they behave<br />

differently depending on storage and load. Benchmark all I/O schedulers and<br />

select the best one for your setup. For further information on I/O schedulers,<br />

refer to:<br />

http://www.linuxjournal.com/article/6931<br />

http://www.redhat.com/magazine/008jun05/features/schedulers/<br />

Chapter 10 RAID 10-5

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!