.TH fio 1 "September 2007" "User Manual"
fio \- flexible I/O tester
is a tool that will spawn a number of threads or processes doing a
particular type of I/O action as specified by the user.
The typical use of fio is to write a job file matching the I/O load
one wants to simulate.
.BI \-\-output \fR=\fPfilename
Write output to \fIfilename\fR.
.BI \-\-timeout \fR=\fPtimeout
Limit run time to \fItimeout\fR seconds.
Generate per-job latency logs.
Generate per-job bandwidth logs.
Print statistics in a terse, semicolon-delimited format.
.BI \-\-showcmd \fR=\fPjobfile
Convert \fIjobfile\fR to a set of command-line options.
Enable read-only safety checks.
.BI \-\-eta \fR=\fPwhen
Specifies when real-time ETA estimate should be printed. \fIwhen\fR may
be one of `always', `never' or `auto'.
.BI \-\-section \fR=\fPsec
Only run section \fIsec\fR from job file.
.BI \-\-cmdhelp \fR=\fPcommand
Print help information for \fIcommand\fR. May be `all' for all commands.
.BI \-\-debug \fR=\fPtype
Enable verbose tracing of various fio actions. May be `all' for all types
or individual types seperated by a comma (eg \-\-debug=io,file). `help' will
list all available tracing options.
Display usage information and exit.
Display version information and exit.
.SH "JOB FILE FORMAT"
Job files are in `ini' format. They consist of one or more
job definitions, which begin with a job name in square brackets and
extend to the next job name. The job name can be any ASCII string
except `global', which has a special meaning. Following the job name is
a sequence of zero or more parameters, one per line, that define the
behavior of the job. Any line starting with a `;' or `#' character is
considered a comment and ignored.
If \fIjobfile\fR is specified as `-', the job file will be read from
.SS "Global Section"
The global section contains default parameters for jobs specified in the
job file. A job is only affected by global sections residing above it,
and there may be any number of global sections. Specific job definitions
may override any parameter set in global sections.
.SH "JOB PARAMETERS"
Some parameters may take arguments of a specific type. The types used are:
String: a sequence of alphanumeric characters.
SI integer: a whole number, possibly containing a suffix denoting the base unit
of the value. Accepted suffixes are `k', 'M', 'G', 'T', and 'P', denoting
kilo (1024), mega (1024^2), giga (1024^3), tera (1024^4), and peta (1024^5)
respectively. The suffix is not case sensitive. If prefixed with '0x', the
value is assumed to be base 16 (hexadecimal).
Boolean: a true or false value. `0' denotes false, `1' denotes true.
Integer range: a range of integers specified in the format
\fIlower\fR:\fIupper\fR or \fIlower\fR\-\fIupper\fR. \fIlower\fR and
\fIupper\fR may contain a suffix as described above. If an option allows two
sets of ranges, they are separated with a `,' or `/' character. For example:
.SS "Parameter List"
.BI name \fR=\fPstr
May be used to override the job name. On the command line, this parameter
has the special purpose of signalling the start of a new job.
.BI description \fR=\fPstr
Human-readable description of the job. It is printed when the job is run, but
otherwise has no special purpose.
.BI directory \fR=\fPstr
Prefix filenames with this directory. Used to place files in a location other
.BI filename \fR=\fPstr
normally makes up a file name based on the job name, thread number, and file
number. If you want to share files between threads in a job or several jobs,
specify a \fIfilename\fR for each of them to override the default. If the I/O
engine used is `net', \fIfilename\fR is the host and port to connect to in the
format \fIhost\fR/\fIport\fR. If the I/O engine is file-based, you can specify
a number of files by separating the names with a `:' character. `\-' is a
reserved name, meaning stdin or stdout, depending on the read/write direction
.BI lockfile \fR=\fPstr
Fio defaults to not locking any files before it does IO to them. If a file or
file descriptor is shared, fio can serialize IO to that file to make the end
result consistent. This is usual for emulating real workloads that share files.
The lock modes are:
No locking. This is the default.
Only one thread or process may do IO at the time, excluding all others.
Read-write locking on the file. Many readers may access the file at the same
time, but writes get exclusive access.
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 acquisition is expensive, batching the lock/unlocks will speed up IO.
.BI opendir \fR=\fPstr
Recursively open any files below directory \fIstr\fR.
.BI readwrite \fR=\fPstr "\fR,\fP rw" \fR=\fPstr
Type of I/O pattern. Accepted values are:
Mixed sequential reads and writes.
Mixed random reads and writes.
For mixed I/O, the default split is 50/50. For random I/O, the number of I/Os
to perform before getting a new offset can be specified by appending
`:\fIint\fR' to the pattern type. The default is 1.
.BI kb_base \fR=\fPint
The base unit for a kilobyte. The defacto base is 2^10, 1024. Storage
manufacturers like to use 10^3 or 1000 as a base ten unit instead, for obvious
reasons. Allow values are 1024 or 1000, with 1024 being the default.
.BI randrepeat \fR=\fPbool
Seed the random number generator in a predictable way so results are repeatable
across runs. Default: true.
.BI fallocate \fR=\fPbool
By default, fio will use fallocate() to advise the system of the size of the
file we are going to write. This can be turned off with fallocate=0. May not
be available on all supported platforms.
.BI fadvise_hint \fR=\fPbool
Disable use of \fIposix_fadvise\fR\|(2) to advise the kernel what I/O patterns
are likely to be issued. Default: true.
.BI size \fR=\fPint
Total size of I/O for this job. \fBfio\fR will run until this many bytes have
been transfered, unless limited by other options (\fBruntime\fR, for instance).
Unless \fBnr_files\fR and \fBfilesize\fR options are given, this amount will be
divided between the available files for the job.
.BI fill_device \fR=\fPbool
Sets size to something really large and waits for ENOSPC (no space left on
device) as the terminating condition. Only makes sense with sequential write.
For a read workload, the mount point will be filled first then IO started on
.BI filesize \fR=\fPirange
Individual file sizes. May be a range, in which case \fBfio\fR will select sizes
for files at random within the given range, limited to \fBsize\fR in total (if
that is given). If \fBfilesize\fR is not specified, each created file is the
.BI blocksize \fR=\fPint[,int] "\fR,\fB bs" \fR=\fPint[,int]
Block size for I/O units. Default: 4k. Values for reads and writes can be
specified seperately in the format \fIread\fR,\fIwrite\fR, either of
which may be empty to leave that value at its default.
.BI blocksize_range \fR=\fPirange[,irange] "\fR,\fB bsrange" \fR=\fPirange[,irange]
Specify a range of I/O block sizes. The issued I/O unit will always be a
multiple of the minimum size, unless \fBblocksize_unaligned\fR is set. Applies
to both reads and writes if only one range is given, but can be specified
seperately with a comma seperating the values. Example: bsrange=1k-4k,2k-8k.
Also (see \fBblocksize\fR).
.BI bssplit \fR=\fPstr
This option allows even finer grained control of the block sizes issued,
not just even splits between them. With this option, you can weight various
block sizes for exact control of the issued IO for a job that has mixed
block sizes. The format of the option is bssplit=blocksize/percentage,
optionally adding as many definitions as needed seperated by a colon.
Example: bssplit=4k/10:64k/50:32k/40 would issue 50% 64k blocks, 10% 4k
blocks and 40% 32k blocks. \fBbssplit\fR also supports giving separate
splits to reads and writes. The format is identical to what the
\fBbs\fR option accepts, the read and write parts are separated with a
.B blocksize_unaligned\fR,\fP bs_unaligned
If set, any size in \fBblocksize_range\fR may be used. This typically won't
work with direct I/O, as that normally requires sector alignment.
.BI blockalign \fR=\fPint[,int] "\fR,\fB ba" \fR=\fPint[,int]
At what boundary to align random IO offsets. Defaults to the same as 'blocksize'
the minimum blocksize given. Minimum alignment is typically 512b
for using direct IO, though it usually depends on the hardware block size.
This option is mutually exclusive with using a random map for files, so it
will turn off that option.
Initialise buffers with all zeros. Default: fill buffers with random data.
If this option is given, fio will refill the IO buffers on every submit. The
default is to only fill it at init time and reuse that data. Only makes sense
if zero_buffers isn't specified, naturally. If data verification is enabled,
refill_buffers is also automatically enabled.
.BI nrfiles \fR=\fPint
Number of files to use for this job. Default: 1.
.BI openfiles \fR=\fPint
Number of files to keep open at the same time. Default: \fBnrfiles\fR.
.BI file_service_type \fR=\fPstr
Defines how files to service are selected. The following types are defined:
Choose a file at random
Round robin over open files (default).
Do each file in the set sequentially.
The number of I/Os to issue before switching a new file can be specified by
appending `:\fIint\fR' to the service type.
.BI ioengine \fR=\fPstr
Defines how the job issues I/O. The following types are defined:
Basic \fIread\fR\|(2) or \fIwrite\fR\|(2) I/O. \fIfseek\fR\|(2) is used to
position the I/O location.
Basic \fIpread\fR\|(2) or \fIpwrite\fR\|(2) I/O.
Basic \fIreadv\fR\|(2) or \fIwritev\fR\|(2) I/O. Will emulate queuing by
coalescing adjacents IOs into a single submission.
Linux native asynchronous I/O.
glibc POSIX asynchronous I/O using \fIaio_read\fR\|(3) and \fIaio_write\fR\|(3).
File is memory mapped with \fImmap\fR\|(2) and data copied using
\fIsplice\fR\|(2) is used to transfer the data and \fIvmsplice\fR\|(2) to
transfer data from user-space to the kernel.
Use the syslet system calls to make regular read/write asynchronous.
SCSI generic sg v3 I/O. May be either synchronous using the SG_IO ioctl, or if
the target is an sg character device, we use \fIread\fR\|(2) and
\fIwrite\fR\|(2) for asynchronous I/O.
Doesn't transfer any data, just pretends to. Mainly used to exercise \fBfio\fR
itself and for debugging and testing purposes.
Transfer over the network. \fBfilename\fR must be set appropriately to
`\fIhost\fR/\fIport\fR' regardless of data direction. If receiving, only the
\fIport\fR argument is used.
Like \fBnet\fR, but uses \fIsplice\fR\|(2) and \fIvmsplice\fR\|(2) to map data
Doesn't transfer any data, but burns CPU cycles according to \fBcpuload\fR and
The GUASI I/O engine is the Generic Userspace Asynchronous Syscall Interface
approach to asycnronous I/O.
Loads an external I/O engine object file. Append the engine filename as
.BI iodepth \fR=\fPint
Number of I/O units to keep in flight against the file. Default: 1.
.BI iodepth_batch \fR=\fPint
Number of I/Os to submit at once. Default: \fBiodepth\fR.
.BI iodepth_batch_complete \fR=\fPint
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
\fBiodepth_low\fR. 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.
.BI iodepth_low \fR=\fPint
Low watermark indicating when to start filling the queue again. Default:
.BI direct \fR=\fPbool
If true, use non-buffered I/O (usually O_DIRECT). Default: false.
.BI buffered \fR=\fPbool
If true, use buffered I/O. This is the opposite of the \fBdirect\fR parameter.
.BI offset \fR=\fPint
Offset in the file to start I/O. Data before the offset will not be touched.
.BI fsync \fR=\fPint
How many I/Os to perform before issuing an \fBfsync\fR\|(2) of dirty data. If
0, don't sync. Default: 0.
.BI fdatasync \fR=\fPint
Like \fBfsync\fR, but uses \fBfdatasync\fR\|(2) instead to only sync the
data parts of the file. Default: 0.
.BI sync_file_range \fR=\fPstr:int
Use sync_file_range() for every \fRval\fP number of write operations. Fio will
track range of writes that have happened since the last sync_file_range() call.
\fRstr\fP can currently be one or more of:
So if you do sync_file_range=wait_before,write:8, fio would use
\fBSYNC_FILE_RANGE_WAIT_BEFORE | SYNC_FILE_RANGE_WRITE\fP for every 8 writes.
Also see the sync_file_range(2) man page. This option is Linux specific.
.BI overwrite \fR=\fPbool
If writing, setup the file first and do overwrites. Default: false.
.BI end_fsync \fR=\fPbool
Sync file contents when job exits. Default: false.
.BI fsync_on_close \fR=\fPbool
If true, sync file contents on close. This differs from \fBend_fsync\fR in that
it will happen on every close, not just at the end of the job. Default: false.
.BI rwmixcycle \fR=\fPint
How many milliseconds before switching between reads and writes for a mixed
workload. Default: 500ms.
.BI rwmixread \fR=\fPint
Percentage of a mixed workload that should be reads. Default: 50.
.BI rwmixwrite \fR=\fPint
Percentage of a mixed workload that should be writes. If \fBrwmixread\fR and
\fBrwmixwrite\fR are given and do not sum to 100%, the latter of the two
overrides the first. This may interfere with a given rate setting, if fio is
asked to limit reads or writes to a certain rate. If that is the case, then
the distribution may be skewed. Default: 50.
Normally \fBfio\fR will cover every block of the file when doing random I/O. If
this parameter is given, a new offset will be chosen without looking at past
I/O history. This parameter is mutually exclusive with \fBverify\fR.
See \fBnorandommap\fR. If fio runs with the random block map enabled and it
fails to allocate the map, if this option is set it will continue without a
random block map. As coverage will not be as complete as with random maps, this
option is disabled by default.
.BI nice \fR=\fPint
Run job with given nice value. See \fInice\fR\|(2).
.BI prio \fR=\fPint
Set I/O priority value of this job between 0 (highest) and 7 (lowest). See
.BI prioclass \fR=\fPint
Set I/O priority class. See \fIionice\fR\|(1).
.BI thinktime \fR=\fPint
Stall job for given number of microseconds between issuing I/Os.
.BI thinktime_spin \fR=\fPint
Pretend to spend CPU time for given number of microseconds, sleeping the rest
of the time specified by \fBthinktime\fR. Only valid if \fBthinktime\fR is set.
.BI thinktime_blocks \fR=\fPint
Number of blocks to issue before waiting \fBthinktime\fR microseconds.
.BI rate \fR=\fPint
Cap bandwidth used by this job. The number is in bytes/sec, the normal postfix
rules apply. You can use \fBrate\fR=500k to limit reads and writes to 500k each,
or you can specify read and writes separately. Using \fBrate\fR=1m,500k would
limit reads to 1MB/sec and writes to 500KB/sec. Capping only reads or writes
can be done with \fBrate\fR=,500k or \fBrate\fR=500k,. The former will only
limit writes (to 500KB/sec), the latter will only limit reads.
.BI ratemin \fR=\fPint
Tell \fBfio\fR to do whatever it can to maintain at least the given bandwidth.
Failing to meet this requirement will cause the job to exit. The same format
as \fBrate\fR is used for read vs write separation.
.BI rate_iops \fR=\fPint
Cap the bandwidth to this number of IOPS. Basically the same as rate, just
specified independently of bandwidth. The same format as \fBrate\fR is used for
read vs write seperation. If \fBblocksize\fR is a range, the smallest block
size is used as the metric.
.BI rate_iops_min \fR=\fPint
If this rate of I/O is not met, the job will exit. The same format as \fBrate\fR
is used for read vs write seperation.
.BI ratecycle \fR=\fPint
Average bandwidth for \fBrate\fR and \fBratemin\fR over this number of
milliseconds. Default: 1000ms.
.BI cpumask \fR=\fPint
Set CPU affinity for this job. \fIint\fR is a bitmask of allowed CPUs the job
may run on. See \fBsched_setaffinity\fR\|(2).
.BI cpus_allowed \fR=\fPstr
Same as \fBcpumask\fR, but allows a comma-delimited list of CPU numbers.
.BI startdelay \fR=\fPint
Delay start of job for the specified number of seconds.
.BI runtime \fR=\fPint
Terminate processing after the specified number of seconds.
If given, run for the specified \fBruntime\fR duration even if the files are
completely read or written. The same workload will be repeated as many times
as \fBruntime\fR allows.
.BI ramp_time \fR=\fPint
If set, fio will run the specified workload for this amount of time before
logging any performance numbers. Useful for letting performance settle before
logging results, thus minimizing the runtime required for stable results. Note
that the \fBramp_time\fR is considered lead in time for a job, thus it will
increase the total runtime if a special timeout or runtime is specified.
.BI invalidate \fR=\fPbool
Invalidate buffer-cache for the file prior to starting I/O. Default: true.
.BI sync \fR=\fPbool
Use synchronous I/O for buffered writes. For the majority of I/O engines,
this means using O_SYNC. Default: false.
.BI iomem \fR=\fPstr "\fR,\fP mem" \fR=\fPstr
Allocation method for I/O unit buffer. Allowed values are:
Allocate memory with \fImalloc\fR\|(3).
Use shared memory buffers allocated through \fIshmget\fR\|(2).
Same as \fBshm\fR, but use huge pages as backing.
Use \fImmap\fR\|(2) for allocation. Uses anonymous memory unless a filename
is given after the option in the format `:\fIfile\fR'.
Same as \fBmmap\fR, but use huge files as backing.
The amount of memory allocated is the maximum allowed \fBblocksize\fR for the
job multiplied by \fBiodepth\fR. For \fBshmhuge\fR or \fBmmaphuge\fR to work,
the system must have free huge pages allocated. \fBmmaphuge\fR also needs to
have hugetlbfs mounted, and \fIfile\fR must point there. At least on Linux,
huge pages must be manually allocated. See \fB/proc/sys/vm/nr_hugehages\fR
and the documentation for that. Normally you just need to echo an appropriate
number, eg echoing 8 will ensure that the OS has 8 huge pages ready for
.BI iomem_align \fR=\fPint
This indiciates the memory alignment of the IO memory buffers. Note that the
given alignment is applied to the first IO unit buffer, if using \fBiodepth\fR
the alignment of the following buffers are given by the \fBbs\fR used. In
other words, if using a \fBbs\fR that is a multiple of the page sized in the
system, all buffers will be aligned to this value. If using a \fBbs\fR that
is not page aligned, the alignment of subsequent IO memory buffers is the
sum of the \fBiomem_align\fR and \fBbs\fR used.
.BI hugepage\-size \fR=\fPint
Defines the size of a huge page. Must be at least equal to the system setting.
Should be a multiple of 1MB. Default: 4MB.
Terminate all jobs when one finishes. Default: wait for each job to finish.
.BI bwavgtime \fR=\fPint
Average bandwidth calculations over the given time in milliseconds. Default:
.BI create_serialize \fR=\fPbool
If true, serialize file creation for the jobs. Default: true.
.BI create_fsync \fR=\fPbool
\fIfsync\fR\|(2) data file after creation. Default: true.
.BI create_on_open \fR=\fPbool
If true, the files are not created until they are opened for IO by the job.
.BI pre_read \fR=\fPbool
If this is given, files will be pre-read into memory before starting the given
IO operation. This will also clear the \fR \fBinvalidate\fR flag, since it is
pointless to pre-read and then drop the cache. This will only work for IO
engines that are seekable, since they allow you to read the same data
multiple times. Thus it will not work on eg network or splice IO.
.BI unlink \fR=\fPbool
Unlink job files when done. Default: false.
.BI loops \fR=\fPint
Specifies the number of iterations (runs of the same workload) of this job.
.BI do_verify \fR=\fPbool
Run the verify phase after a write phase. Only valid if \fBverify\fR is set.
.BI verify \fR=\fPstr
Method of verifying file contents after each iteration of the job. Allowed
.B md5 crc16 crc32 crc32c crc32c-intel crc64 crc7 sha256 sha512 sha1
Store appropriate checksum in the header of each block.
Write extra information about each I/O (timestamp, block number, etc.). The
block number is verified.
Fill I/O buffers with a specific pattern that is used to verify. If the pattern
is < 4bytes, it can either be a decimal or a hexadecimal number. If the pattern
is > 4bytes, currently, it can only be a hexadecimal pattern starting with
either "0x" or "0X".
Pretend to verify. Used for testing internals.
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. If the data direction given
is a read or random read, fio will assume that it should verify a previously
written file. If the data direction includes any form of write, the verify will
be of the newly written data.
.BI verify_sort \fR=\fPbool
If true, written verify blocks are sorted if \fBfio\fR deems it to be faster to
read them back in a sorted manner. Default: true.
.BI verify_offset \fR=\fPint
Swap the verification header with data somewhere else in the block before
writing. It is swapped back before verifying.
.BI verify_interval \fR=\fPint
Write the verification header for this number of bytes, which should divide
\fBblocksize\fR. Default: \fBblocksize\fR.
.BI verify_fatal \fR=\fPbool
If true, exit the job on the first observed verification failure. Default:
.BI verify_async \fR=\fPint
Fio will normally verify IO inline from the submitting thread. This option
takes an integer describing how many async offload threads to create for IO
verification instead, causing fio to offload the duty of verifying IO contents
to one or more separate threads. If using this offload option, even sync IO
engines can benefit from using an \fBiodepth\fR setting higher than 1, as it
allows them to have IO in flight while verifies are running.
.BI verify_async_cpus \fR=\fPstr
Tell fio to set the given CPU affinity on the async IO verification threads.
See \fBcpus_allowed\fP for the format used.
Wait for preceeding jobs in the job file to exit before starting this one.
\fBstonewall\fR implies \fBnew_group\fR.
Start a new reporting group. If not given, all jobs in a file will be part
of the same reporting group, unless separated by a stonewall.
.BI numjobs \fR=\fPint
Number of clones (processes/threads performing the same workload) of this job.
If set, display per-group reports instead of per-job when \fBnumjobs\fR is
Use threads created with \fBpthread_create\fR\|(3) instead of processes created
.BI zonesize \fR=\fPint
Divide file into zones of the specified size in bytes. See \fBzoneskip\fR.
.BI zoneskip \fR=\fPint
Skip the specified number of bytes when \fBzonesize\fR bytes of data have been
.BI write_iolog \fR=\fPstr
Write the issued I/O patterns to the specified file.
.BI read_iolog \fR=\fPstr
Replay the I/O patterns contained in the specified file generated by
\fBwrite_iolog\fR, or may be a \fBblktrace\fR binary file.
.B write_bw_log \fR=\fPstr
If given, write a bandwidth log of the jobs in this job file. Can be used to
store data of the bandwidth of the jobs in their lifetime. The included
fio_generate_plots script uses gnuplot to turn these text files into nice
graphs. See \fBwrite_log_log\fR for behaviour of given filename. For this
option, the postfix is _bw.log.
Same as \fBwrite_bw_log\fR, but writes I/O completion latencies. If no
filename is given with this option, the default filename of "jobname_type.log"
is used. Even if the filename is given, fio will still append the type of log.
.B disable_clat \fR=\fPbool
Disable measurements of completion latency numbers. Useful only for cutting
back the number of calls to gettimeofday, as that does impact performance at
really high IOPS rates. Note that to really get rid of a large amount of these
calls, this option must be used with disable_slat and disable_bw as well.
.B disable_slat \fR=\fPbool
Disable measurements of submission latency numbers. See \fBdisable_clat\fR.
.B disable_bw_measurement \fR=\fPbool
Disable measurements of throughput/bandwidth numbers. See \fBdisable_clat\fR.
.BI lockmem \fR=\fPint
Pin the specified amount of memory with \fBmlock\fR\|(2). Can be used to
simulate a smaller amount of memory.
.BI exec_prerun \fR=\fPstr
Before running the job, execute the specified command with \fBsystem\fR\|(3).
.BI exec_postrun \fR=\fPstr
Same as \fBexec_prerun\fR, but the command is executed after the job completes.
.BI ioscheduler \fR=\fPstr
Attempt to switch the device hosting the file to the specified I/O scheduler.
.BI cpuload \fR=\fPint
If the job is a CPU cycle-eater, attempt to use the specified percentage of
.BI cpuchunks \fR=\fPint
If the job is a CPU cycle-eater, split the load into cycles of the
given time in milliseconds.
.BI disk_util \fR=\fPbool
Generate disk utilization statistics if the platform supports it. Default: true.
.BI gtod_reduce \fR=\fPbool
Enable all of the gettimeofday() reducing options (disable_clat, disable_slat,
disable_bw) plus reduce precision of the timeout somewhat to really shrink the
gettimeofday() call count. With this option enabled, we only do about 0.4% of
the gtod() calls we would have done if all time keeping was enabled.
.BI gtod_cpu \fR=\fPint
Sometimes it's cheaper to dedicate a single thread of execution to just getting
the current time. Fio (and databases, for instance) are very intensive on
gettimeofday() calls. With this option, you can set one CPU aside for doing
nothing but logging current time to a shared memory location. Then the other
threads/processes that run IO workloads need only copy that segment, instead of
entering the kernel with a gettimeofday() call. The CPU set aside for doing
these time calls will be excluded from other uses. Fio will manually clear it
from the CPU mask of other jobs.
.BI cgroup \fR=\fPstr
Add job to this control group. If it doesn't exist, it will be created.
The system must have a mounted cgroup blkio mount point for this to work. If
your system doesn't have it mounted, you can do so with:
# mount -t cgroup -o blkio none /cgroup
.BI cgroup_weight \fR=\fPint
Set the weight of the cgroup to this value. See the documentation that comes
with the kernel, allowed values are in the range of 100..1000.
.BI uid \fR=\fPint
Instead of running as the invoking user, set the user ID to this value before
the thread/process does any work.
.BI gid \fR=\fPint
Set group ID, see \fBuid\fR.
While running, \fBfio\fR will display the status of the created jobs. For
Threads: 1: [_r] [24.8% done] [ 13509/ 8334 kb/s] [eta 00h:01m:31s]
The characters in the first set of brackets denote the current status of each
threads. The possible values are:
Setup but not started.
Running, doing sequential reads.
Running, doing random reads.
Running, doing sequential writes.
Running, doing random writes.
Running, doing mixed sequential reads/writes.
Running, doing mixed random reads/writes.
Running, currently waiting for \fBfsync\fR\|(2).
Running, verifying written data.
Exited, not reaped by main thread.
Exited, thread reaped.
The second set of brackets shows the estimated completion percentage of
the current group. The third set shows the read and write I/O rate,
respectively. Finally, the estimated run time of the job is displayed.
When \fBfio\fR completes (or is interrupted by Ctrl-C), it will show data
for each thread, each group of threads, and each disk, in that order.
Per-thread statistics first show the threads client number, group-id, and
error code. The remaining figures are as follows:
Number of megabytes of I/O performed.
Average data rate (bandwidth).
Threads run time.
Submission latency minimum, maximum, average and standard deviation. This is
the time it took to submit the I/O.
Completion latency minimum, maximum, average and standard deviation. This
is the time between submission and completion.
Bandwidth minimum, maximum, percentage of aggregate bandwidth received, average
and standard deviation.
CPU usage statistics. Includes user and system time, number of context switches
this thread went through and number of major and minor page faults.
.B IO depths
Distribution of I/O depths. Each depth includes everything less than (or equal)
to it, but greater than the previous depth.
.B IO issued
Number of read/write requests issued, and number of short read/write requests.
.B IO latencies
Distribution of I/O completion latencies. The numbers follow the same pattern
as \fBIO depths\fR.
The group statistics show:
Number of megabytes I/O performed.
Aggregate bandwidth of threads in the group.
Minimum average bandwidth a thread saw.
Maximum average bandwidth a thread saw.
Shortest runtime of threads in the group.
Longest runtime of threads in the group.
Finally, disk statistics are printed with reads first:
Number of I/Os performed by all groups.
Number of merges in the I/O scheduler.
Number of ticks we kept the disk busy.
Total time spent in the disk queue.
.SH TERSE OUTPUT
If the \fB\-\-minimal\fR option is given, the results will be printed in a
semicolon-delimited format suitable for scripted use. The fields are:
.B jobname, groupid, error
.B KB I/O, bandwidth \fR(KB/s)\fP, runtime \fR(ms)\fP
.B min, max, mean, standard deviation
.B min, max, mean, standard deviation
.B min, max, aggregate percentage of total, mean, standard deviation
.B KB I/O, bandwidth \fR(KB/s)\fP, runtime \fR(ms)\fP
.B min, max, mean, standard deviation
.B min, max, mean, standard deviation
.B min, max, aggregate percentage of total, mean, standard deviation
.B user, system, context switches, major page faults, minor page faults
IO depth distribution:
.B <=1, 2, 4, 8, 16, 32, >=64
IO latency distribution (ms):
.B <=2, 4, 10, 20, 50, 100, 250, 500, 750, 1000, >=2000
.B text description
was written by Jens Axboe <firstname.lastname@example.org>.
This man page was written by Aaron Carroll <email@example.com> based
on documentation by Jens Axboe.
.SH "REPORTING BUGS"
Report bugs to the \fBfio\fR mailing list <firstname.lastname@example.org>.
.SH "SEE ALSO"
For further documentation see \fBHOWTO\fR and \fBREADME\fR.
Sample jobfiles are available in the \fBexamples\fR directory.