IOzone: Difference between revisions
From Leo's Notes
This page was last edited on 30 December 2021, at 01:17.
m →Usage |
m Added categories and navbox |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
IOzone is a filesystem benchmark that can test read and write performance. It supports both sequential and random IO. | IOzone is a filesystem benchmark that can test read and write performance. It supports both sequential and random IO. | ||
* Project Website: http://iozone.org/ | *Project Website: http://iozone.org/ | ||
* Download: http://www.iozone.org/src/current/iozone3_491.tgz | *Download: http://www.iozone.org/src/current/iozone3_491.tgz | ||
== Usage == | ==Usage== | ||
Refer to these commonly used options or skip to the examples below. | |||
{| class="wikitable" | {| class="wikitable" | ||
|+All size values can be given with units k, m, or g, etc. Eg. 128k, 512m | |+All size values can be given with units k, m, or g, etc. Eg. 128k, 512m | ||
| Line 40: | Line 40: | ||
{{columns-list|colwidth=15em| | {{columns-list|colwidth=15em| | ||
<!-- start at 0 --> | <!-- start at 0 --> | ||
: 0. write/rewrite | : 0. write/rewrite (sequential) | ||
# read/reread | # read/reread (sequential) | ||
# random-read/write | # random-read/write (random I/O) | ||
# read-backwards | # read-backwards (sequential) | ||
# rewrite record | # rewrite record | ||
# stride read | # stride read | ||
| Line 63: | Line 63: | ||
|} | |} | ||
=== Examples === | ===Examples=== | ||
{{Highlight | {{Highlight | ||
| code = ## Testing read/write on a 1GB file with 32 threads. Use 16K record sizes | | code = ## Testing read/write on a 1GB file with 32 threads. Use 16K record sizes | ||
$ iozone -i 0 -i 1 -s 1g -r 16k -t 32 | $ iozone -i 0 -i 1 -s 1g -r 16k -t 32 | ||
## Write test. 256K cache with 64K record size. Write a 128MB file, which we do not delete | |||
$ iozone -i 0 -S 256k -r 64k -s 128m -w -e | |||
## Random read/write tests | |||
$ iozone -i 2 -S 256k -r 64k -s 128m -w -e | |||
| lang = terminal | | lang = terminal | ||
}} | }} | ||
{{Navbox Linux}} | |||
[[Category:Linux]] | |||
[[Category:LinuxUtilities]] | |||
Latest revision as of 01:17, 30 December 2021
IOzone is a filesystem benchmark that can test read and write performance. It supports both sequential and random IO.
- Project Website: http://iozone.org/
- Download: http://www.iozone.org/src/current/iozone3_491.tgz
Usage
Refer to these commonly used options or skip to the examples below.
| Option | Description |
|---|---|
-a
|
automatic mode. Tests in record sizes 4K to 16M and file sizes 64K to 512M |
-g size
|
maximum file size. Useful to test IO without memory caching interfering. |
-n size
|
minimum file size (64K default) |
-s size
|
specific size (overrides -g and -n)
|
-S size
|
specify cache size |
-r size
|
record size |
-w
|
do not delete temporary files, useful for read tests |
-e
|
ensure flush time is included in calculations |
-i
|
Specifies the test to run. Most commonly used tests are 0 (write), 1 (read), 2 (random).
You can specify more than one test to run by calling with multiple
|
-R
|
exports a report in csv format |
-t
|
Number of threads to run; to test throughput. |
Examples
## Testing read/write on a 1GB file with 32 threads. Use 16K record sizes
$ iozone -i 0 -i 1 -s 1g -r 16k -t 32
## Write test. 256K cache with 64K record size. Write a 128MB file, which we do not delete
$ iozone -i 0 -S 256k -r 64k -s 128m -w -e
## Random read/write tests
$ iozone -i 2 -S 256k -r 64k -s 128m -w -e