转自: How to measure I/O Performance on Linux (文档 ID 1931009.1)
IOzone can be used to test any file-system type like: EXT3/4, LVM, XFS, BTRFS, NFS, SAMBA etc.
etc - so then we pick-up best one which will suit best app/db needs.
Also if more threads are being used with flag -l the more higher queue depth will become.
NOTE:
Please remember that -F can be used to specify different mount-points
so if we need to test for example two LVM mount-points in the same time
then simple please provide different paths for each test file like /u01/test1.tmp and /u02/test2.tmp.
The more files will be added for testing purpose the more load CPU will need to take, same also go for file-size.
If only one test is required for example write test use -u flag example: -u 0 will test only write/rewrite.
IOzone has many flags which can be used to test synchronous/asynchronous random/sequential I/O access, please use them to test variety of scenarios.
Always try to match sector size eg. -r flag with App/DB/LVM block size to achieve best performance results.
IOzone can be used to bypass system memory cache by using flag -I ( so it will use DirectI/O )
or don't use it to include Memory Cache mechanism
Please pay maximum attention while running IOzone tests as they can cause high CPU or I/O activity,
also keep in mind File-System space ( do not exceed file-system size with test files)