I/O engine ioengine=str
Defines how the job issues I/O to the file. The following types are defined:
("libaio/sg/net/netsplice/rdma/rados/rbd/gfapi/gfapi_async" defines engine specific options)
null
Doesn't transfer any data, just pretends to. This is mainly used to
exercise …
Environment variables
Fio also supports environment variable expansion in job files. Any sub-string of the form ${VARNAME} as part of an option value (in other words, on the right
of the '='), will be expanded to the value of the environment variable called VARNAME. If no such environment variable …
more ...
fio accepts one or more job files describing what it is supposed to do.
The job file format is the classic ini file, where the names
enclosed in [] brackets define the job name. You are free to use any ASCII name you want, except global which has special …
more ...
How fio works
The first step in getting fio to simulate a desired I/O workload, is writing a job file describing that specific setup.
A job file may contain any number of threads and/or files -- the typical contents of the job file is a global section …
more ...