The following commands are examples to run sequential and random IOzone tests, the results of which are recorded in performance evaluation.
For sequential writes:
iozone -i 0 -c -e -w -r 16M -s $Size -t $Thread -+n -+m /path/to/threadlist
For sequential reads:
iozone -i 1 -c -e -w -r 16M -s $Size -t $Thread -+n -+m /path/to/threadlist
For IOPS random reads/writes:
iozone -i 2 -w -O -I -r 4K -s $Size -t $Thread -+n -+m /path/to/threadlist
The following table describes the IOzone command-line options. The O_Direct command-line option, -I, enables us to bypass the cache on the compute nodes where the IOzone threads are running:
Table 13. IOzone command-line options
-i 0 | Write test |
-I 1 | Read test |
-I 2 | Random IOPS test |
-+n | No retest |
-c | Includes close in the timing calculations |
-e | Includes flush in the timing calculations |
-r | Records size |
-s | File size |
-+m | Location of clients to run IOzone on when in clustered mode |
-I | Use O_Direct |
-w | Does not unlink (delete) temporary file |
-O | Return results in OPS |
