meaning kilo, mega, and giga. So if you want to specify 4096,
you could either write out '4096' or just give 4k. The postfixes
signify base 2 values, so 1024 is 1k and 1024k is 1m and so on.
+ If the option accepts an upper and lower range, use a colon ':'
+ or minus '-' to seperate such values. See irange.
bool Boolean. Usually parsed as an integer, however only defined for
true and false (1 and 0).
irange Integer range with postfix. Allows value range to be given, such
files between threads in a job or several jobs, specify
a filename for each of them to override the default. If
the ioengine used is 'net', the filename is the host and
- port to connect to in the format of =host:port.
+ port to connect to in the format of =host/port. If the
+ ioengine is file based, you can specify a number of files
+ by seperating the names with a ':' colon. So if you wanted
+ a job to open /dev/sda and /dev/sdb as the two working files,
+ you would use filename=/dev/sda:/dev/sdb
+opendir=str Tell fio to recursively add any file it can find in this
+ directory and down the file system tree.
+
+readwrite=str
rw=str Type of io pattern. Accepted values are:
read Sequential reads
For the mixed io types, the default is to split them 50/50.
For certain types of io the result may still be skewed a bit,
- since the speed may be different.
+ since the speed may be different. It is possible to specify
+ a number of IO's to do before getting a new offset - this
+ is only useful for random IO, where fio would normally
+ generate a new random offset for every IO. If you append
+ eg 8 to randread, you would get a new random offset for
+ every 8 IO's. The result would be a seek for only every 8
+ IO's, instead of for every IO. Use rw=randread:8 to specify
+ that.
randrepeat=bool For random IO workloads, seed the generator in a predictable
way so that results are repeatable across repetitions.
+fadvise_hint=bool By default, fio will use fadvise() to advise the kernel
+ on what IO patterns it is likely to issue. Sometimes you
+ want to test specific IO patterns without telling the
+ kernel about it, in which case you can disable this option.
+ If set, fio will use POSIX_FADV_SEQUENTIAL for sequential
+ IO and POSIX_FADV_RANDOM for random IO.
+
size=siint The total size of file io for this job. This may describe
the size of the single file the job uses, or it may be
divided between the number of files in the job. If the
size if larger than the current file size. If this parameter
is not given and the file exists, the file size will be used.
+filesize=siint Individual file sizes. May be a range, in which case fio
+ will select sizes for files at random within the given range
+ and limited to 'size' in total (if that is given). If not
+ given, each created file is the same size.
+
+blocksize=siint
bs=siint The block size used for the io units. Defaults to 4k. Values
can be given for both read and writes. If a single siint is
given, it will apply to both. If a second siint is specified
can do so by passing an empty read size - bs=,8k will set
8k for writes and leave the read default value.
+blocksize_range=irange
bsrange=irange Instead of giving a single block size, specify a range
and fio will mix the issued io block sizes. The issued
io unit will always be a multiple of the minimum value
writes, however a second range can be given after a comma.
See bs=.
+blocksize_unaligned
bs_unaligned If this option is given, any byte size value within bsrange
may be used as a block range. This typically wont work with
direct IO, as that normally requires sector alignment.
nrfiles=int Number of files to use for this job. Defaults to 1.
+openfiles=int Number of files to keep open at the same time. Defaults to
+ the same as nrfiles, can be set smaller to limit the number
+ simultaneous opens.
+
+file_service_type=str Defines how fio decides which file from a job to
+ service next. The following types are defined:
+
+ random Just choose a file at random.
+
+ roundrobin Round robin over open files. This
+ is the default.
+
+ The string can have a number appended, indicating how
+ often to switch to a new file. So if option random:4 is
+ given, fio will switch to a new random file after 4 ios
+ have been issued.
+
ioengine=str Defines how the job issues io to the file. The following
types are defined:
net Transfer over the network to given host:port.
'filename' must be set appropriately to
- filename=host:port regardless of send
+ filename=host/port regardless of send
or receive, if the latter only the port
argument is used.
+ cpu Doesn't transfer any data, but burns CPU
+ cycles according to the cpuload= and
+ cpucycle= options. Setting cpuload=85
+ will cause that job to do nothing but burn
+ 85% of the CPU.
+
+ guasi The GUASI IO engine is the Generic Userspace
+ Asyncronous Syscall Interface approach
+ to async IO. See
+
+ http://www.xmailserver.org/guasi-lib.html
+
+ for more info on GUASI.
+
+ external Prefix to specify loading an external
+ IO engine object file. Append the engine
+ filename, eg ioengine=external:/tmp/foo.o
+ to load ioengine foo.o in /tmp.
+
iodepth=int This defines how many io units to keep in flight against
the file. The default is 1 for each file defined in this
job, can be overridden with a larger value for higher
end_fsync=bool If true, fsync file contents when the job exits.
+fsync_on_close=bool If true, fio will fsync() a dirty file on close.
+ This differs from end_fsync in that it will happen on every
+ file close, not just at the end of the job.
+
rwmixcycle=int Value in milliseconds describing how often to switch between
reads and writes for a mixed workload. The default is
500 msecs.
rate=int Cap the bandwidth used by this job to this number of KiB/sec.
ratemin=int Tell fio to do whatever it can to maintain at least this
- bandwidth.
+ bandwidth. Failing to meet this requirement, will cause
+ the job to exit.
+
+rate_iops=int Cap the bandwidth to this number of IOPS. Basically the same
+ as rate, just specified independently of bandwidth. If the
+ job is given a block size range instead of a fixed value,
+ the smallest block size is used as the metric.
+
+rate_iops_min=int If fio doesn't meet this rate of IO, it will cause
+ the job to exit.
ratecycle=int Average bandwidth for 'rate' and 'ratemin' over this number
of milliseconds.
sync=bool Use sync io for buffered writes. For the majority of the
io engines, this means using O_SYNC.
+iomem=str
mem=str Fio can use various types of memory as the io unit buffer.
The allowed values are:
crc32 Use a crc32 sum of the data area and store
it in the header of each block.
+ null Only pretend to verify. Useful for testing
+ internals with ioengine=null, not for much
+ else.
+
This option can be used for repeated burn-in tests of a
system to make sure that the written data is also
correctly read back.
+verifysort=bool If set, fio will sort written verify blocks when it deems
+ it faster to read them back in a sorted manner. This is
+ often the case when overwriting an existing file, since
+ the blocks are already laid out in the file system. You
+ can ignore this option unless doing huge amounts of really
+ fast IO where the red-black tree sorting CPU time becomes
+ significant.
+
stonewall Wait for preceeding jobs in the job file to exit, before
starting this one. Can be used to insert serialization
- points in the job file.
+ points in the job file. A stone wall also implies starting
+ a new reporting group.
+
+new_group Start a new reporting group. If this option isn't given,
+ jobs in a file will be part of the same reporting group
+ unless seperated by a stone wall (or if it's a group
+ by itself, with the numjobs option).
numjobs=int Create the specified number of clones of this job. May be
used to setup a larger number of threads/processes doing
- the same thing.
+ the same thing. We regard that grouping of jobs as a
+ specific group.
+
+group_reporting If 'numjobs' is set, it may be interesting to display
+ statistics for the group as a whole instead of for each
+ individual job. This is especially true of 'numjobs' is
+ large, looking at individual thread/process output quickly
+ becomes unwieldy. If 'group_reporting' is specified, fio
+ will show the final report per-group instead of per-job.
thread fio defaults to forking jobs, however if this option is
given, fio will use pthread_create(3) to create threads
io= Number of megabytes io performed
bw= Average bandwidth rate
runt= The runtime of that thread
- slat= Submission latency (avg being the average, dev being the
+ slat= Submission latency (avg being the average, stdev being the
standard deviation). This is the time it took to submit
the io. For sync io, the slat is really the completion
latency, since queue/complete is one operation there.
----------------
For scripted usage where you typically want to generate tables or graphs
-of the results, fio can output the results in a comma separated format.
+of the results, fio can output the results in a semicolon separated format.
The format is one long line of values, such as:
-client1,0,0,936,331,2894,0,0,0.000000,0.000000,1,170,22.115385,34.290410,16,714,84.252874%,366.500000,566.417819,3496,1237,2894,0,0,0.000000,0.000000,0,246,6.671625,21.436952,0,2534,55.465300%,1406.600000,2008.044216,0.000000%,0.431928%,1109
+client1;0;0;1906777;1090804;1790;0;0;0.000000;0.000000;0;0;0.000000;0.000000;929380;1152890;25.510151%;1078276.333333;128948.113404;0;0;0;0;0;0.000000;0.000000;0;0;0.000000;0.000000;0;0;0.000000%;0.000000;0.000000;100.000000%;0.000000%;324;100.0%;0.0%;0.0%;0.0%;0.0%;0.0%;0.0%;100.0%;0.0%;0.0%;0.0%;0.0%;0.0%
+;0.0%;0.0%;0.0%;0.0%;0.0%
Split up, the format is as follows:
Completion latency: min, max, mean, deviation
Bw: min, max, aggregate percentage of total, mean, deviation
CPU usage: user, system, context switches
+ IO depths: <=1, 2, 4, 8, 16, 32, >=64
+ IO latencies: <=2, 4, 10, 20, 50, 100, 250, 500, 750, 1000, >=2000
+ Text description
projects / fio.git / blobdiff