str String. This is a sequence of alpha characters.
int Integer. A whole number value, can be negative. If prefixed with
- 0x, the integer is assumed to be of base 16 (hexidecimal).
+ 0x, the integer is assumed to be of base 16 (hexadecimal).
siint SI integer. A whole number value, which may contain a postfix
describing the base of the number. Accepted postfixes are k/m/g,
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.
+ or minus '-' to separate 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
- as 1024-4096. A colon may also be used as the seperator, eg
+ as 1024-4096. A colon may also be used as the separator, eg
1k:4k. If the option allows two sets of ranges, they can be
specified with a ',' or '/' delimiter: 1k-4k/8k-32k. Also see
siint.
the ioengine used is 'net', the filename is the host and
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
+ by separating 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. '-' is a reserved
name, meaning stdin or stdout. Which of the two depends
The option may be post-fixed with a lock batch number. If
set, then each thread/process may do that amount of IOs to
- the file before giving up the lock. Since lock acqusition is
+ the file before giving up the lock. Since lock acquisition is
expensive, batching the lock/unlocks will speed up IO.
readwrite=str
job, can be overridden with a larger value for higher
concurrency.
+iodepth_batch_submit=int
iodepth_batch=int This defines how many pieces of IO to submit at once.
It defaults to 1 which means that we submit each IO
as soon as it is available, but can be raised to submit
bigger batches of IO at the time.
+iodepth_batch_complete=int This defines how many pieces of IO to retrieve
+ at once. It defaults to 1 which means that we'll ask
+ for a minimum of 1 IO in the retrieval process from
+ the kernel. The IO retrieval will go on until we
+ hit the limit set by iodepth_low. If this variable is
+ set to 0, then fio will always check for completed
+ events before queuing more IO. This helps reduce
+ IO latency, at the cost of more retrieval system calls.
+
iodepth_low=int The low water mark indicating when to start filling
the queue again. Defaults to the same as iodepth, meaning
that fio will attempt to keep the queue full at all times.
cap the total runtime to a given time.
time_based If set, fio will run for the duration of the runtime
- specified even if the file(s) are completey read or
+ specified even if the file(s) are completely read or
written. It will simply loop over the same workload
as many times as the runtime allows.
default.
unlink=bool Unlink the job files when done. Not the default, as repeated
- runs of that job would then waste time recreating the fileset
- again and again.
+ runs of that job would then waste time recreating the file
+ set again and again.
loops=int Run the specified number of iterations of this job. Used
to repeat the same workload a given number of times. Defaults
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
+ unless separated 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
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. This
- value can be in miliseconds or microseconds, fio will choose
+ value can be in milliseconds or microseconds, fio will choose
the most appropriate base and print that. In the example
- above, miliseconds is the best scale.
+ above, milliseconds is the best scale.
clat= Completion latency. Same names as slat, this denotes the
time from submission to completion of the io pieces. For
sync io, clat will usually be equal (or very close) to 0,
projects / fio.git / blobdiff