4 The first step in getting fio to simulate a desired I/O workload, is writing a
5 job file describing that specific setup. A job file may contain any number of
6 threads and/or files -- the typical contents of the job file is a *global*
7 section defining shared parameters, and one or more job sections describing the
8 jobs involved. When run, fio parses this file and sets everything up as
9 described. If we break down a job from top to bottom, it contains the following
14 Defines the I/O pattern issued to the file(s). We may only be reading
15 sequentially from this file(s), or we may be writing randomly. Or even
16 mixing reads and writes, sequentially or randomly.
17 Should we be doing buffered I/O, or direct/raw I/O?
21 In how large chunks are we issuing I/O? This may be a single value,
22 or it may describe a range of block sizes.
26 How much data are we going to be reading/writing.
30 How do we issue I/O? We could be memory mapping the file, we could be
31 using regular read/write, we could be using splice, async I/O, or even
36 If the I/O engine is async, how large a queuing depth do we want to
42 How many files are we spreading the workload over.
44 `Threads, processes and job synchronization`_
46 How many threads or processes should we spread this workload over.
48 The above are the basic parameters defined for a workload, in addition there's a
49 multitude of parameters that modify other aspects of how this job behaves.
55 .. option:: --debug=type
57 Enable verbose tracing `type` of various fio actions. May be ``all`` for all types
58 or individual types separated by a comma (e.g. ``--debug=file,mem`` will
59 enable file and memory debugging). Currently, additional logging is
63 Dump info related to processes.
65 Dump info related to file actions.
67 Dump info related to I/O queuing.
69 Dump info related to memory allocations.
71 Dump info related to blktrace setup.
73 Dump info related to I/O verification.
75 Enable all debug options.
77 Dump info related to random offset generation.
79 Dump info related to option matching and parsing.
81 Dump info related to disk utilization updates.
83 Dump info only related to job number x.
85 Dump info only related to mutex up/down ops.
87 Dump info related to profile extensions.
89 Dump info related to internal time keeping.
91 Dump info related to networking connections.
93 Dump info related to I/O rate switching.
95 Dump info related to log compress/decompress.
97 Dump info related to steadystate detection.
99 Dump info related to the helper thread.
101 Dump info related to support for zoned block devices.
103 Show available debug options.
105 .. option:: --parse-only
107 Parse options only, don't start any I/O.
109 .. option:: --merge-blktrace-only
111 Merge blktraces only, don't start any I/O.
113 .. option:: --output=filename
115 Write output to file `filename`.
117 .. option:: --output-format=format
119 Set the reporting `format` to `normal`, `terse`, `json`, or `json+`. Multiple
120 formats can be selected, separated by a comma. `terse` is a CSV based
121 format. `json+` is like `json`, except it adds a full dump of the latency
124 .. option:: --bandwidth-log
126 Generate aggregate bandwidth logs.
128 .. option:: --minimal
130 Print statistics in a terse, semicolon-delimited format.
132 .. option:: --append-terse
134 Print statistics in selected mode AND terse, semicolon-delimited format.
135 **Deprecated**, use :option:`--output-format` instead to select multiple
138 .. option:: --terse-version=version
140 Set terse `version` output format (default 3, or 2 or 4 or 5).
142 .. option:: --version
144 Print version information and exit.
148 Print a summary of the command line options and exit.
150 .. option:: --cpuclock-test
152 Perform test and validation of internal CPU clock.
154 .. option:: --crctest=[test]
156 Test the speed of the built-in checksumming functions. If no argument is
157 given, all of them are tested. Alternatively, a comma separated list can
158 be passed, in which case the given ones are tested.
160 .. option:: --cmdhelp=command
162 Print help information for `command`. May be ``all`` for all commands.
164 .. option:: --enghelp=[ioengine[,command]]
166 List all commands defined by `ioengine`, or print help for `command`
167 defined by `ioengine`. If no `ioengine` is given, list all
170 .. option:: --showcmd
172 Convert given job files to a set of command-line options.
174 .. option:: --readonly
176 Turn on safety read-only checks, preventing writes and trims. The
177 ``--readonly`` option is an extra safety guard to prevent users from
178 accidentally starting a write or trim workload when that is not desired.
179 Fio will only modify the device under test if
180 `rw=write/randwrite/rw/randrw/trim/randtrim/trimwrite` is given. This
181 safety net can be used as an extra precaution.
183 .. option:: --eta=when
185 Specifies when real-time ETA estimate should be printed. `when` may be
186 `always`, `never` or `auto`. `auto` is the default, it prints ETA
187 when requested if the output is a TTY. `always` disregards the output
188 type, and prints ETA when requested. `never` never prints ETA.
190 .. option:: --eta-interval=time
192 By default, fio requests client ETA status roughly every second. With
193 this option, the interval is configurable. Fio imposes a minimum
194 allowed time to avoid flooding the console, less than 250 msec is
197 .. option:: --eta-newline=time
199 Force a new line for every `time` period passed. When the unit is omitted,
200 the value is interpreted in seconds.
202 .. option:: --status-interval=time
204 Force a full status dump of cumulative (from job start) values at `time`
205 intervals. This option does *not* provide per-period measurements. So
206 values such as bandwidth are running averages. When the time unit is omitted,
207 `time` is interpreted in seconds. Note that using this option with
208 ``--output-format=json`` will yield output that technically isn't valid
209 json, since the output will be collated sets of valid json. It will need
210 to be split into valid sets of json after the run.
212 .. option:: --section=name
214 Only run specified section `name` in job file. Multiple sections can be specified.
215 The ``--section`` option allows one to combine related jobs into one file.
216 E.g. one job file could define light, moderate, and heavy sections. Tell
217 fio to run only the "heavy" section by giving ``--section=heavy``
218 command line option. One can also specify the "write" operations in one
219 section and "verify" operation in another section. The ``--section`` option
220 only applies to job sections. The reserved *global* section is always
223 .. option:: --alloc-size=kb
225 Allocate additional internal smalloc pools of size `kb` in KiB. The
226 ``--alloc-size`` option increases shared memory set aside for use by fio.
227 If running large jobs with randommap enabled, fio can run out of memory.
228 Smalloc is an internal allocator for shared structures from a fixed size
229 memory pool and can grow to 16 pools. The pool size defaults to 16MiB.
231 NOTE: While running :file:`.fio_smalloc.*` backing store files are visible
234 .. option:: --warnings-fatal
236 All fio parser warnings are fatal, causing fio to exit with an
239 .. option:: --max-jobs=nr
241 Set the maximum number of threads/processes to support to `nr`.
242 NOTE: On Linux, it may be necessary to increase the shared-memory
243 limit (:file:`/proc/sys/kernel/shmmax`) if fio runs into errors while
246 .. option:: --server=args
248 Start a backend server, with `args` specifying what to listen to.
249 See `Client/Server`_ section.
251 .. option:: --daemonize=pidfile
253 Background a fio server, writing the pid to the given `pidfile` file.
255 .. option:: --client=hostname
257 Instead of running the jobs locally, send and run them on the given `hostname`
258 or set of `hostname`\s. See `Client/Server`_ section.
260 .. option:: --remote-config=file
262 Tell fio server to load this local `file`.
264 .. option:: --idle-prof=option
266 Report CPU idleness. `option` is one of the following:
269 Run unit work calibration only and exit.
272 Show aggregate system idleness and unit work.
275 As **system** but also show per CPU idleness.
277 .. option:: --inflate-log=log
279 Inflate and output compressed `log`.
281 .. option:: --trigger-file=file
283 Execute trigger command when `file` exists.
285 .. option:: --trigger-timeout=time
287 Execute trigger at this `time`.
289 .. option:: --trigger=command
291 Set this `command` as local trigger.
293 .. option:: --trigger-remote=command
295 Set this `command` as remote trigger.
297 .. option:: --aux-path=path
299 Use the directory specified by `path` for generated state files instead
300 of the current working directory.
302 Any parameters following the options will be assumed to be job files, unless
303 they match a job file parameter. Multiple job files can be listed and each job
304 file will be regarded as a separate group. Fio will :option:`stonewall`
305 execution between each group.
311 As previously described, fio accepts one or more job files describing what it is
312 supposed to do. The job file format is the classic ini file, where the names
313 enclosed in [] brackets define the job name. You are free to use any ASCII name
314 you want, except *global* which has special meaning. Following the job name is
315 a sequence of zero or more parameters, one per line, that define the behavior of
316 the job. If the first character in a line is a ';' or a '#', the entire line is
317 discarded as a comment.
319 A *global* section sets defaults for the jobs described in that file. A job may
320 override a *global* section parameter, and a job file may even have several
321 *global* sections if so desired. A job is only affected by a *global* section
324 The :option:`--cmdhelp` option also lists all options. If used with a `command`
325 argument, :option:`--cmdhelp` will detail the given `command`.
327 See the `examples/` directory for inspiration on how to write job files. Note
328 the copyright and license requirements currently apply to `examples/` files.
330 So let's look at a really simple job file that defines two processes, each
331 randomly reading from a 128MiB file:
335 ; -- start job file --
346 As you can see, the job file sections themselves are empty as all the described
347 parameters are shared. As no :option:`filename` option is given, fio makes up a
348 `filename` for each of the jobs as it sees fit. On the command line, this job
349 would look as follows::
351 $ fio --name=global --rw=randread --size=128m --name=job1 --name=job2
354 Let's look at an example that has a number of processes writing randomly to
359 ; -- start job file --
370 Here we have no *global* section, as we only have one job defined anyway. We
371 want to use async I/O here, with a depth of 4 for each file. We also increased
372 the buffer size used to 32KiB and define numjobs to 4 to fork 4 identical
373 jobs. The result is 4 processes each randomly writing to their own 64MiB
374 file. Instead of using the above job file, you could have given the parameters
375 on the command line. For this case, you would specify::
377 $ fio --name=random-writers --ioengine=libaio --iodepth=4 --rw=randwrite --bs=32k --direct=0 --size=64m --numjobs=4
379 When fio is utilized as a basis of any reasonably large test suite, it might be
380 desirable to share a set of standardized settings across multiple job files.
381 Instead of copy/pasting such settings, any section may pull in an external
382 :file:`filename.fio` file with *include filename* directive, as in the following
385 ; -- start job file including.fio --
389 include glob-include.fio
396 include test-include.fio
397 ; -- end job file including.fio --
401 ; -- start job file glob-include.fio --
404 ; -- end job file glob-include.fio --
408 ; -- start job file test-include.fio --
411 ; -- end job file test-include.fio --
413 Settings pulled into a section apply to that section only (except *global*
414 section). Include directives may be nested in that any included file may contain
415 further include directive(s). Include files may not contain [] sections.
418 Environment variables
419 ~~~~~~~~~~~~~~~~~~~~~
421 Fio also supports environment variable expansion in job files. Any sub-string of
422 the form ``${VARNAME}`` as part of an option value (in other words, on the right
423 of the '='), will be expanded to the value of the environment variable called
424 `VARNAME`. If no such environment variable is defined, or `VARNAME` is the
425 empty string, the empty string will be substituted.
427 As an example, let's look at a sample fio invocation and job file::
429 $ SIZE=64m NUMJOBS=4 fio jobfile.fio
433 ; -- start job file --
440 This will expand to the following equivalent job file at runtime:
444 ; -- start job file --
451 Fio ships with a few example job files, you can also look there for inspiration.
456 Additionally, fio has a set of reserved keywords that will be replaced
457 internally with the appropriate value. Those keywords are:
461 The architecture page size of the running system.
465 Megabytes of total memory in the system.
469 Number of online available CPUs.
471 These can be used on the command line or in the job file, and will be
472 automatically substituted with the current system values when the job is
473 run. Simple math is also supported on these keywords, so you can perform actions
478 and get that properly expanded to 8 times the size of memory in the machine.
484 This section describes in details each parameter associated with a job. Some
485 parameters take an option of a given type, such as an integer or a
486 string. Anywhere a numeric value is required, an arithmetic expression may be
487 used, provided it is surrounded by parentheses. Supported operators are:
496 For time values in expressions, units are microseconds by default. This is
497 different than for time values not in expressions (not enclosed in
498 parentheses). The following types are used:
505 String: A sequence of alphanumeric characters.
508 Integer with possible time suffix. Without a unit value is interpreted as
509 seconds unless otherwise specified. Accepts a suffix of 'd' for days, 'h' for
510 hours, 'm' for minutes, 's' for seconds, 'ms' (or 'msec') for milliseconds and
511 'us' (or 'usec') for microseconds. For example, use 10m for 10 minutes.
516 Integer. A whole number value, which may contain an integer prefix
517 and an integer suffix:
519 [*integer prefix*] **number** [*integer suffix*]
521 The optional *integer prefix* specifies the number's base. The default
522 is decimal. *0x* specifies hexadecimal.
524 The optional *integer suffix* specifies the number's units, and includes an
525 optional unit prefix and an optional unit. For quantities of data, the
526 default unit is bytes. For quantities of time, the default unit is seconds
527 unless otherwise specified.
529 With :option:`kb_base`\=1000, fio follows international standards for unit
530 prefixes. To specify power-of-10 decimal values defined in the
531 International System of Units (SI):
533 * *K* -- means kilo (K) or 1000
534 * *M* -- means mega (M) or 1000**2
535 * *G* -- means giga (G) or 1000**3
536 * *T* -- means tera (T) or 1000**4
537 * *P* -- means peta (P) or 1000**5
539 To specify power-of-2 binary values defined in IEC 80000-13:
541 * *Ki* -- means kibi (Ki) or 1024
542 * *Mi* -- means mebi (Mi) or 1024**2
543 * *Gi* -- means gibi (Gi) or 1024**3
544 * *Ti* -- means tebi (Ti) or 1024**4
545 * *Pi* -- means pebi (Pi) or 1024**5
547 For Zone Block Device Mode:
550 With :option:`kb_base`\=1024 (the default), the unit prefixes are opposite
551 from those specified in the SI and IEC 80000-13 standards to provide
552 compatibility with old scripts. For example, 4k means 4096.
554 For quantities of data, an optional unit of 'B' may be included
555 (e.g., 'kB' is the same as 'k').
557 The *integer suffix* is not case sensitive (e.g., m/mi mean mebi/mega,
558 not milli). 'b' and 'B' both mean byte, not bit.
560 Examples with :option:`kb_base`\=1000:
562 * *4 KiB*: 4096, 4096b, 4096B, 4ki, 4kib, 4kiB, 4Ki, 4KiB
563 * *1 MiB*: 1048576, 1mi, 1024ki
564 * *1 MB*: 1000000, 1m, 1000k
565 * *1 TiB*: 1099511627776, 1ti, 1024gi, 1048576mi
566 * *1 TB*: 1000000000, 1t, 1000m, 1000000k
568 Examples with :option:`kb_base`\=1024 (default):
570 * *4 KiB*: 4096, 4096b, 4096B, 4k, 4kb, 4kB, 4K, 4KB
571 * *1 MiB*: 1048576, 1m, 1024k
572 * *1 MB*: 1000000, 1mi, 1000ki
573 * *1 TiB*: 1099511627776, 1t, 1024g, 1048576m
574 * *1 TB*: 1000000000, 1ti, 1000mi, 1000000ki
576 To specify times (units are not case sensitive):
580 * *M* -- means minutes
581 * *s* -- or sec means seconds (default)
582 * *ms* -- or *msec* means milliseconds
583 * *us* -- or *usec* means microseconds
585 If the option accepts an upper and lower range, use a colon ':' or
586 minus '-' to separate such values. See :ref:`irange <irange>`.
587 If the lower value specified happens to be larger than the upper value
588 the two values are swapped.
593 Boolean. Usually parsed as an integer, however only defined for
594 true and false (1 and 0).
599 Integer range with suffix. Allows value range to be given, such as
600 1024-4096. A colon may also be used as the separator, e.g. 1k:4k. If the
601 option allows two sets of ranges, they can be specified with a ',' or '/'
602 delimiter: 1k-4k/8k-32k. Also see :ref:`int <int>`.
605 A list of floating point numbers, separated by a ':' character.
607 With the above in mind, here follows the complete list of fio job parameters.
613 .. option:: kb_base=int
615 Select the interpretation of unit prefixes in input parameters.
618 Inputs comply with IEC 80000-13 and the International
619 System of Units (SI). Use:
621 - power-of-2 values with IEC prefixes (e.g., KiB)
622 - power-of-10 values with SI prefixes (e.g., kB)
625 Compatibility mode (default). To avoid breaking old scripts:
627 - power-of-2 values with SI prefixes
628 - power-of-10 values with IEC prefixes
630 See :option:`bs` for more details on input parameters.
632 Outputs always use correct prefixes. Most outputs include both
635 bw=2383.3kB/s (2327.4KiB/s)
637 If only one value is reported, then kb_base selects the one to use:
639 **1000** -- SI prefixes
641 **1024** -- IEC prefixes
643 .. option:: unit_base=int
645 Base unit for reporting. Allowed values are:
648 Use auto-detection (default).
660 ASCII name of the job. This may be used to override the name printed by fio
661 for this job. Otherwise the job name is used. On the command line this
662 parameter has the special purpose of also signaling the start of a new job.
664 .. option:: description=str
666 Text description of the job. Doesn't do anything except dump this text
667 description when this job is run. It's not parsed.
669 .. option:: loops=int
671 Run the specified number of iterations of this job. Used to repeat the same
672 workload a given number of times. Defaults to 1.
674 .. option:: numjobs=int
676 Create the specified number of clones of this job. Each clone of job
677 is spawned as an independent thread or process. May be used to setup a
678 larger number of threads/processes doing the same thing. Each thread is
679 reported separately; to see statistics for all clones as a whole, use
680 :option:`group_reporting` in conjunction with :option:`new_group`.
681 See :option:`--max-jobs`. Default: 1.
684 Time related parameters
685 ~~~~~~~~~~~~~~~~~~~~~~~
687 .. option:: runtime=time
689 Limit runtime. The test will run until it completes the configured I/O
690 workload or until it has run for this specified amount of time, whichever
691 occurs first. It can be quite hard to determine for how long a specified
692 job will run, so this parameter is handy to cap the total runtime to a
693 given time. When the unit is omitted, the value is interpreted in
696 .. option:: time_based
698 If set, fio will run for the duration of the :option:`runtime` specified
699 even if the file(s) are completely read or written. It will simply loop over
700 the same workload as many times as the :option:`runtime` allows.
702 .. option:: startdelay=irange(time)
704 Delay the start of job for the specified amount of time. Can be a single
705 value or a range. When given as a range, each thread will choose a value
706 randomly from within the range. Value is in seconds if a unit is omitted.
708 .. option:: ramp_time=time
710 If set, fio will run the specified workload for this amount of time before
711 logging any performance numbers. Useful for letting performance settle
712 before logging results, thus minimizing the runtime required for stable
713 results. Note that the ``ramp_time`` is considered lead in time for a job,
714 thus it will increase the total runtime if a special timeout or
715 :option:`runtime` is specified. When the unit is omitted, the value is
718 .. option:: clocksource=str
720 Use the given clocksource as the base of timing. The supported options are:
723 :manpage:`gettimeofday(2)`
726 :manpage:`clock_gettime(2)`
729 Internal CPU clock source
731 cpu is the preferred clocksource if it is reliable, as it is very fast (and
732 fio is heavy on time calls). Fio will automatically use this clocksource if
733 it's supported and considered reliable on the system it is running on,
734 unless another clocksource is specifically set. For x86/x86-64 CPUs, this
735 means supporting TSC Invariant.
737 .. option:: gtod_reduce=bool
739 Enable all of the :manpage:`gettimeofday(2)` reducing options
740 (:option:`disable_clat`, :option:`disable_slat`, :option:`disable_bw_measurement`) plus
741 reduce precision of the timeout somewhat to really shrink the
742 :manpage:`gettimeofday(2)` call count. With this option enabled, we only do
743 about 0.4% of the :manpage:`gettimeofday(2)` calls we would have done if all
744 time keeping was enabled.
746 .. option:: gtod_cpu=int
748 Sometimes it's cheaper to dedicate a single thread of execution to just
749 getting the current time. Fio (and databases, for instance) are very
750 intensive on :manpage:`gettimeofday(2)` calls. With this option, you can set
751 one CPU aside for doing nothing but logging current time to a shared memory
752 location. Then the other threads/processes that run I/O workloads need only
753 copy that segment, instead of entering the kernel with a
754 :manpage:`gettimeofday(2)` call. The CPU set aside for doing these time
755 calls will be excluded from other uses. Fio will manually clear it from the
756 CPU mask of other jobs.
758 .. option:: job_start_clock_id=int
760 The clock_id passed to the call to `clock_gettime` used to record
761 job_start in the `json` output format. Default is 0, or CLOCK_REALTIME.
767 .. option:: directory=str
769 Prefix filenames with this directory. Used to place files in a different
770 location than :file:`./`. You can specify a number of directories by
771 separating the names with a ':' character. These directories will be
772 assigned equally distributed to job clones created by :option:`numjobs` as
773 long as they are using generated filenames. If specific `filename(s)` are
774 set fio will use the first listed directory, and thereby matching the
775 `filename` semantic (which generates a file for each clone if not
776 specified, but lets all clones use the same file if set).
778 See the :option:`filename` option for information on how to escape "``:``"
779 characters within the directory path itself.
781 Note: To control the directory fio will use for internal state files
782 use :option:`--aux-path`.
784 .. option:: filename=str
786 Fio normally makes up a `filename` based on the job name, thread number, and
787 file number (see :option:`filename_format`). If you want to share files
788 between threads in a job or several
789 jobs with fixed file paths, specify a `filename` for each of them to override
790 the default. If the ioengine is file based, you can specify a number of files
791 by separating the names with a ':' colon. So if you wanted a job to open
792 :file:`/dev/sda` and :file:`/dev/sdb` as the two working files, you would use
793 ``filename=/dev/sda:/dev/sdb``. This also means that whenever this option is
794 specified, :option:`nrfiles` is ignored. The size of regular files specified
795 by this option will be :option:`size` divided by number of files unless an
796 explicit size is specified by :option:`filesize`.
798 Each colon in the wanted path must be escaped with a ``\``
799 character. For instance, if the path is :file:`/dev/dsk/foo@3,0:c` then you
800 would use ``filename=/dev/dsk/foo@3,0\:c`` and if the path is
801 :file:`F:\\filename` then you would use ``filename=F\:\filename``.
803 On Windows, disk devices are accessed as :file:`\\\\.\\PhysicalDrive0` for
804 the first device, :file:`\\\\.\\PhysicalDrive1` for the second etc.
805 Note: Windows and FreeBSD (refer to geom(4)) prevent write access to areas
806 of the disk containing in-use data (e.g. filesystems).
808 The filename "`-`" is a reserved name, meaning *stdin* or *stdout*. Which
809 of the two depends on the read/write direction set.
811 .. option:: filename_format=str
813 If sharing multiple files between jobs, it is usually necessary to have fio
814 generate the exact names that you want. By default, fio will name a file
815 based on the default file format specification of
816 :file:`jobname.jobnumber.filenumber`. With this option, that can be
817 customized. Fio will recognize and replace the following keywords in this
821 The name of the worker thread or process.
823 IP of the fio process when using client/server mode.
825 The incremental number of the worker thread or process.
827 The incremental number of the file for that worker thread or
830 To have dependent jobs share a set of files, this option can be set to have
831 fio generate filenames that are shared between the two. For instance, if
832 :file:`testfiles.$filenum` is specified, file number 4 for any job will be
833 named :file:`testfiles.4`. The default of :file:`$jobname.$jobnum.$filenum`
834 will be used if no other format specifier is given.
836 If you specify a path then the directories will be created up to the
837 main directory for the file. So for example if you specify
838 ``filename_format=a/b/c/$jobnum`` then the directories a/b/c will be
839 created before the file setup part of the job. If you specify
840 :option:`directory` then the path will be relative that directory,
841 otherwise it is treated as the absolute path.
843 .. option:: unique_filename=bool
845 To avoid collisions between networked clients, fio defaults to prefixing any
846 generated filenames (with a directory specified) with the source of the
847 client connecting. To disable this behavior, set this option to 0.
849 .. option:: opendir=str
851 Recursively open any files below directory `str`. This accepts only a
852 single directory and unlike related options, colons appearing in the
853 path must not be escaped.
855 .. option:: lockfile=str
857 Fio defaults to not locking any files before it does I/O to them. If a file
858 or file descriptor is shared, fio can serialize I/O to that file to make the
859 end result consistent. This is usual for emulating real workloads that share
860 files. The lock modes are:
863 No locking. The default.
865 Only one thread or process may do I/O at a time, excluding all
868 Read-write locking on the file. Many readers may
869 access the file at the same time, but writes get exclusive access.
871 .. option:: nrfiles=int
873 Number of files to use for this job. Defaults to 1. The size of files
874 will be :option:`size` divided by this unless explicit size is specified by
875 :option:`filesize`. Files are created for each thread separately, and each
876 file will have a file number within its name by default, as explained in
877 :option:`filename` section.
880 .. option:: openfiles=int
882 Number of files to keep open at the same time. Defaults to the same as
883 :option:`nrfiles`, can be set smaller to limit the number simultaneous
886 .. option:: file_service_type=str
888 Defines how fio decides which file from a job to service next. The following
892 Choose a file at random.
895 Round robin over opened files. This is the default.
898 Finish one file before moving on to the next. Multiple files can
899 still be open depending on :option:`openfiles`.
902 Use a *Zipf* distribution to decide what file to access.
905 Use a *Pareto* distribution to decide what file to access.
908 Use a *Gaussian* (normal) distribution to decide what file to
914 For *random*, *roundrobin*, and *sequential*, a postfix can be appended to
915 tell fio how many I/Os to issue before switching to a new file. For example,
916 specifying ``file_service_type=random:8`` would cause fio to issue
917 8 I/Os before selecting a new file at random. For the non-uniform
918 distributions, a floating point postfix can be given to influence how the
919 distribution is skewed. See :option:`random_distribution` for a description
920 of how that would work.
922 .. option:: ioscheduler=str
924 Attempt to switch the device hosting the file to the specified I/O scheduler
927 .. option:: create_serialize=bool
929 If true, serialize the file creation for the jobs. This may be handy to
930 avoid interleaving of data files, which may greatly depend on the filesystem
931 used and even the number of processors in the system. Default: true.
933 .. option:: create_fsync=bool
935 :manpage:`fsync(2)` the data file after creation. This is the default.
937 .. option:: create_on_open=bool
939 If true, don't pre-create files but allow the job's open() to create a file
940 when it's time to do I/O. Default: false -- pre-create all necessary files
943 .. option:: create_only=bool
945 If true, fio will only run the setup phase of the job. If files need to be
946 laid out or updated on disk, only that will be done -- the actual job contents
947 are not executed. Default: false.
949 .. option:: allow_file_create=bool
951 If true, fio is permitted to create files as part of its workload. If this
952 option is false, then fio will error out if
953 the files it needs to use don't already exist. Default: true.
955 .. option:: allow_mounted_write=bool
957 If this isn't set, fio will abort jobs that are destructive (e.g. that write)
958 to what appears to be a mounted device or partition. This should help catch
959 creating inadvertently destructive tests, not realizing that the test will
960 destroy data on the mounted file system. Note that some platforms don't allow
961 writing against a mounted device regardless of this option. Default: false.
963 .. option:: pre_read=bool
965 If this is given, files will be pre-read into memory before starting the
966 given I/O operation. This will also clear the :option:`invalidate` flag,
967 since it is pointless to pre-read and then drop the cache. This will only
968 work for I/O engines that are seek-able, since they allow you to read the
969 same data multiple times. Thus it will not work on non-seekable I/O engines
970 (e.g. network, splice). Default: false.
972 .. option:: unlink=bool
974 Unlink (delete) the job files when done. Not the default, as repeated runs of that
975 job would then waste time recreating the file set again and again. Default:
978 .. option:: unlink_each_loop=bool
980 Unlink (delete) job files after each iteration or loop. Default: false.
982 .. option:: zonemode=str
987 The :option:`zonerange`, :option:`zonesize`,
988 :option:`zonecapacity` and :option:`zoneskip`
989 parameters are ignored.
991 I/O happens in a single zone until
992 :option:`zonesize` bytes have been transferred.
993 After that number of bytes has been
994 transferred processing of the next zone
995 starts. :option:`zonecapacity` is ignored.
997 Zoned block device mode. I/O happens
998 sequentially in each zone, even if random I/O
999 has been selected. Random I/O happens across
1000 all zones instead of being restricted to a
1001 single zone. The :option:`zoneskip` parameter
1002 is ignored. :option:`zonerange` and
1003 :option:`zonesize` must be identical.
1004 Trim is handled using a zone reset operation.
1005 Trim only considers non-empty sequential write
1006 required and sequential write preferred zones.
1008 .. option:: zonerange=int
1010 Size of a single zone. See also :option:`zonesize` and
1013 .. option:: zonesize=int
1015 For :option:`zonemode` =strided, this is the number of bytes to
1016 transfer before skipping :option:`zoneskip` bytes. If this parameter
1017 is smaller than :option:`zonerange` then only a fraction of each zone
1018 with :option:`zonerange` bytes will be accessed. If this parameter is
1019 larger than :option:`zonerange` then each zone will be accessed
1020 multiple times before skipping to the next zone.
1022 For :option:`zonemode` =zbd, this is the size of a single zone. The
1023 :option:`zonerange` parameter is ignored in this mode.
1026 .. option:: zonecapacity=int
1028 For :option:`zonemode` =zbd, this defines the capacity of a single zone,
1029 which is the accessible area starting from the zone start address.
1030 This parameter only applies when using :option:`zonemode` =zbd in
1031 combination with regular block devices. If not specified it defaults to
1032 the zone size. If the target device is a zoned block device, the zone
1033 capacity is obtained from the device information and this option is
1036 .. option:: zoneskip=int
1038 For :option:`zonemode` =strided, the number of bytes to skip after
1039 :option:`zonesize` bytes of data have been transferred. This parameter
1040 must be zero for :option:`zonemode` =zbd.
1042 .. option:: read_beyond_wp=bool
1044 This parameter applies to :option:`zonemode` =zbd only.
1046 Zoned block devices are block devices that consist of multiple zones.
1047 Each zone has a type, e.g. conventional or sequential. A conventional
1048 zone can be written at any offset that is a multiple of the block
1049 size. Sequential zones must be written sequentially. The position at
1050 which a write must occur is called the write pointer. A zoned block
1051 device can be either drive managed, host managed or host aware. For
1052 host managed devices the host must ensure that writes happen
1053 sequentially. Fio recognizes host managed devices and serializes
1054 writes to sequential zones for these devices.
1056 If a read occurs in a sequential zone beyond the write pointer then
1057 the zoned block device will complete the read without reading any data
1058 from the storage medium. Since such reads lead to unrealistically high
1059 bandwidth and IOPS numbers fio only reads beyond the write pointer if
1060 explicitly told to do so. Default: false.
1062 .. option:: max_open_zones=int
1064 When a zone of a zoned block device is partially written (i.e. not all
1065 sectors of the zone have been written), the zone is in one of three
1066 conditions: 'implicit open', 'explicit open' or 'closed'. Zoned block
1067 devices may have a limit called 'max_open_zones' (same name as the
1068 parameter) on the total number of zones that can simultaneously be in
1069 the 'implicit open' or 'explicit open' conditions. Zoned block devices
1070 may have another limit called 'max_active_zones', on the total number of
1071 zones that can simultaneously be in the three conditions. The
1072 :option:`max_open_zones` parameter limits the number of zones to which
1073 write commands are issued by all fio jobs, that is, limits the number of
1074 zones that will be in the conditions. When the device has the
1075 max_open_zones limit and does not have the max_active_zones limit, the
1076 :option:`max_open_zones` parameter limits the number of zones in the two
1077 open conditions up to the limit. In this case, fio includes zones in the
1078 two open conditions to the write target zones at fio start. When the
1079 device has both the max_open_zones and the max_active_zones limits, the
1080 :option:`max_open_zones` parameter limits the number of zones in the
1081 three conditions up to the limit. In this case, fio includes zones in
1082 the three conditions to the write target zones at fio start.
1084 This parameter is relevant only if the :option:`zonemode` =zbd is used.
1085 The default value is always equal to the max_open_zones limit of the
1086 target zoned block device and a value higher than this limit cannot be
1087 specified by users unless the option :option:`ignore_zone_limits` is
1088 specified. When :option:`ignore_zone_limits` is specified or the target
1089 device does not have the max_open_zones limit, :option:`max_open_zones`
1090 can specify 0 to disable any limit on the number of zones that can be
1091 simultaneously written to by all jobs.
1093 .. option:: job_max_open_zones=int
1095 In the same manner as :option:`max_open_zones`, limit the number of open
1096 zones per fio job, that is, the number of zones that a single job can
1097 simultaneously write to. A value of zero indicates no limit.
1100 .. option:: ignore_zone_limits=bool
1102 If this option is used, fio will ignore the maximum number of open
1103 zones limit of the zoned block device in use, thus allowing the
1104 option :option:`max_open_zones` value to be larger than the device
1105 reported limit. Default: false.
1107 .. option:: zone_reset_threshold=float
1109 A number between zero and one that indicates the ratio of written bytes
1110 in the zones with write pointers in the IO range to the size of the IO
1111 range. When current ratio is above this ratio, zones are reset
1112 periodically as :option:`zone_reset_frequency` specifies. If there are
1113 multiple jobs when using this option, the IO range for all write jobs
1116 .. option:: zone_reset_frequency=float
1118 A number between zero and one that indicates how often a zone reset
1119 should be issued if the zone reset threshold has been exceeded. A zone
1120 reset is submitted after each (1 / zone_reset_frequency) write
1121 requests. This and the previous parameter can be used to simulate
1122 garbage collection activity.
1128 .. option:: direct=bool
1130 If value is true, use non-buffered I/O. This is usually O_DIRECT. Note that
1131 OpenBSD and ZFS on Solaris don't support direct I/O. On Windows the synchronous
1132 ioengines don't support direct I/O. Default: false.
1134 .. option:: buffered=bool
1136 If value is true, use buffered I/O. This is the opposite of the
1137 :option:`direct` option. Defaults to true.
1139 .. option:: readwrite=str, rw=str
1141 Type of I/O pattern. Accepted values are:
1148 Sequential trims (Linux block devices and SCSI
1149 character devices only).
1155 Random trims (Linux block devices and SCSI
1156 character devices only).
1158 Sequential mixed reads and writes.
1160 Random mixed reads and writes.
1162 Sequential trim+write sequences. Blocks will be trimmed first,
1163 then the same blocks will be written to. So if ``io_size=64K``
1164 is specified, Fio will trim a total of 64K bytes and also
1165 write 64K bytes on the same trimmed blocks. This behaviour
1166 will be consistent with ``number_ios`` or other Fio options
1167 limiting the total bytes or number of I/O's.
1169 Like trimwrite, but uses random offsets rather
1170 than sequential writes.
1172 Fio defaults to read if the option is not specified. For the mixed I/O
1173 types, the default is to split them 50/50. For certain types of I/O the
1174 result may still be skewed a bit, since the speed may be different.
1176 It is possible to specify the number of I/Os to do before getting a new
1177 offset by appending ``:<nr>`` to the end of the string given. For a
1178 random read, it would look like ``rw=randread:8`` for passing in an offset
1179 modifier with a value of 8. If the suffix is used with a sequential I/O
1180 pattern, then the *<nr>* value specified will be **added** to the generated
1181 offset for each I/O turning sequential I/O into sequential I/O with holes.
1182 For instance, using ``rw=write:4k`` will skip 4k for every write. Also see
1183 the :option:`rw_sequencer` option.
1185 .. option:: rw_sequencer=str
1187 If an offset modifier is given by appending a number to the ``rw=<str>``
1188 line, then this option controls how that number modifies the I/O offset
1189 being generated. Accepted values are:
1192 Generate sequential offset.
1194 Generate the same offset.
1196 ``sequential`` is only useful for random I/O, where fio would normally
1197 generate a new random offset for every I/O. If you append e.g. 8 to
1198 randread, i.e. ``rw=randread:8`` you would get a new random offset for
1199 every 8 I/Os. The result would be a sequence of 8 sequential offsets
1200 with a random starting point. However this behavior may change if a
1201 sequential I/O reaches end of the file. As sequential I/O is already
1202 sequential, setting ``sequential`` for that would not result in any
1203 difference. ``identical`` behaves in a similar fashion, except it sends
1204 the same offset 8 number of times before generating a new offset.
1209 rw_sequencer=sequential
1212 The generated sequence of offsets will look like this:
1213 4k, 8k, 12k, 16k, 20k, 24k, 28k, 32k, 92k, 96k, 100k, 104k, 108k,
1214 112k, 116k, 120k, 48k, 52k ...
1219 rw_sequencer=identical
1222 The generated sequence of offsets will look like this:
1223 4k, 4k, 4k, 4k, 4k, 4k, 4k, 4k, 92k, 92k, 92k, 92k, 92k, 92k, 92k, 92k,
1226 .. option:: unified_rw_reporting=str
1228 Fio normally reports statistics on a per data direction basis, meaning that
1229 reads, writes, and trims are accounted and reported separately. This option
1230 determines whether fio reports the results normally, summed together, or as
1232 Accepted values are:
1235 Normal statistics reporting.
1238 Statistics are summed per data direction and reported together.
1241 Statistics are reported normally, followed by the mixed statistics.
1244 Backward-compatible alias for **none**.
1247 Backward-compatible alias for **mixed**.
1252 .. option:: randrepeat=bool
1254 Seed all random number generators in a predictable way so the pattern
1255 is repeatable across runs. Default: true.
1257 .. option:: allrandrepeat=bool
1259 Alias for :option:`randrepeat`. Default: true.
1261 .. option:: randseed=int
1263 Seed the random number generators based on this seed value, to be able to
1264 control what sequence of output is being generated. If not set, the random
1265 sequence depends on the :option:`randrepeat` setting.
1267 .. option:: fallocate=str
1269 Whether pre-allocation is performed when laying down files.
1270 Accepted values are:
1273 Do not pre-allocate space.
1276 Use a platform's native pre-allocation call but fall back to
1277 **none** behavior if it fails/is not implemented.
1280 Pre-allocate via :manpage:`posix_fallocate(3)`.
1283 Pre-allocate via :manpage:`fallocate(2)` with
1284 FALLOC_FL_KEEP_SIZE set.
1287 Extend file to final size via :manpage:`ftruncate(2)`
1288 instead of allocating.
1291 Backward-compatible alias for **none**.
1294 Backward-compatible alias for **posix**.
1296 May not be available on all supported platforms. **keep** is only available
1297 on Linux. If using ZFS on Solaris this cannot be set to **posix**
1298 because ZFS doesn't support pre-allocation. Default: **native** if any
1299 pre-allocation methods except **truncate** are available, **none** if not.
1301 Note that using **truncate** on Windows will interact surprisingly
1302 with non-sequential write patterns. When writing to a file that has
1303 been extended by setting the end-of-file information, Windows will
1304 backfill the unwritten portion of the file up to that offset with
1305 zeroes before issuing the new write. This means that a single small
1306 write to the end of an extended file will stall until the entire
1307 file has been filled with zeroes.
1309 .. option:: fadvise_hint=str
1311 Use :manpage:`posix_fadvise(2)` or :manpage:`posix_fadvise(2)` to
1312 advise the kernel on what I/O patterns are likely to be issued.
1313 Accepted values are:
1316 Backwards-compatible hint for "no hint".
1319 Backwards compatible hint for "advise with fio workload type". This
1320 uses **FADV_RANDOM** for a random workload, and **FADV_SEQUENTIAL**
1321 for a sequential workload.
1324 Advise using **FADV_SEQUENTIAL**.
1327 Advise using **FADV_RANDOM**.
1330 Advise using **FADV_NOREUSE**. This may be a no-op on older Linux
1331 kernels. Since Linux 6.3, it provides a hint to the LRU algorithm.
1332 See the :manpage:`posix_fadvise(2)` man page.
1334 .. option:: write_hint=str
1336 Use :manpage:`fcntl(2)` to advise the kernel what life time to expect
1337 from a write. Only supported on Linux, as of version 4.13. Accepted
1341 No particular life time associated with this file.
1344 Data written to this file has a short life time.
1347 Data written to this file has a medium life time.
1350 Data written to this file has a long life time.
1353 Data written to this file has a very long life time.
1355 The values are all relative to each other, and no absolute meaning
1356 should be associated with them.
1358 .. option:: offset=int
1360 Start I/O at the provided offset in the file, given as either a fixed size in
1361 bytes, zones or a percentage. If a percentage is given, the generated offset will be
1362 aligned to the minimum ``blocksize`` or to the value of ``offset_align`` if
1363 provided. Data before the given offset will not be touched. This
1364 effectively caps the file size at `real_size - offset`. Can be combined with
1365 :option:`size` to constrain the start and end range of the I/O workload.
1366 A percentage can be specified by a number between 1 and 100 followed by '%',
1367 for example, ``offset=20%`` to specify 20%. In ZBD mode, value can be set as
1368 number of zones using 'z'.
1370 .. option:: offset_align=int
1372 If set to non-zero value, the byte offset generated by a percentage ``offset``
1373 is aligned upwards to this value. Defaults to 0 meaning that a percentage
1374 offset is aligned to the minimum block size.
1376 .. option:: offset_increment=int
1378 If this is provided, then the real offset becomes `offset + offset_increment
1379 * thread_number`, where the thread number is a counter that starts at 0 and
1380 is incremented for each sub-job (i.e. when :option:`numjobs` option is
1381 specified). This option is useful if there are several jobs which are
1382 intended to operate on a file in parallel disjoint segments, with even
1383 spacing between the starting points. Percentages can be used for this option.
1384 If a percentage is given, the generated offset will be aligned to the minimum
1385 ``blocksize`` or to the value of ``offset_align`` if provided. In ZBD mode, value can
1386 also be set as number of zones using 'z'.
1388 .. option:: number_ios=int
1390 Fio will normally perform I/Os until it has exhausted the size of the region
1391 set by :option:`size`, or if it exhaust the allocated time (or hits an error
1392 condition). With this setting, the range/size can be set independently of
1393 the number of I/Os to perform. When fio reaches this number, it will exit
1394 normally and report status. Note that this does not extend the amount of I/O
1395 that will be done, it will only stop fio if this condition is met before
1396 other end-of-job criteria.
1398 .. option:: fsync=int
1400 If writing to a file, issue an :manpage:`fsync(2)` (or its equivalent) of
1401 the dirty data for every number of blocks given. For example, if you give 32
1402 as a parameter, fio will sync the file after every 32 writes issued. If fio is
1403 using non-buffered I/O, we may not sync the file. The exception is the sg
1404 I/O engine, which synchronizes the disk cache anyway. Defaults to 0, which
1405 means fio does not periodically issue and wait for a sync to complete. Also
1406 see :option:`end_fsync` and :option:`fsync_on_close`.
1408 .. option:: fdatasync=int
1410 Like :option:`fsync` but uses :manpage:`fdatasync(2)` to only sync data and
1411 not metadata blocks. In Windows, DragonFlyBSD or OSX there is no
1412 :manpage:`fdatasync(2)` so this falls back to using :manpage:`fsync(2)`.
1413 Defaults to 0, which means fio does not periodically issue and wait for a
1414 data-only sync to complete.
1416 .. option:: write_barrier=int
1418 Make every `N-th` write a barrier write.
1420 .. option:: sync_file_range=str:int
1422 Use :manpage:`sync_file_range(2)` for every `int` number of write
1423 operations. Fio will track range of writes that have happened since the last
1424 :manpage:`sync_file_range(2)` call. `str` can currently be one or more of:
1427 SYNC_FILE_RANGE_WAIT_BEFORE
1429 SYNC_FILE_RANGE_WRITE
1431 SYNC_FILE_RANGE_WAIT_AFTER
1433 So if you do ``sync_file_range=wait_before,write:8``, fio would use
1434 ``SYNC_FILE_RANGE_WAIT_BEFORE | SYNC_FILE_RANGE_WRITE`` for every 8
1435 writes. Also see the :manpage:`sync_file_range(2)` man page. This option is
1438 .. option:: overwrite=bool
1440 If true, writes to a file will always overwrite existing data. If the file
1441 doesn't already exist, it will be created before the write phase begins. If
1442 the file exists and is large enough for the specified write phase, nothing
1443 will be done. Default: false.
1445 .. option:: end_fsync=bool
1447 If true, :manpage:`fsync(2)` file contents when a write stage has completed.
1450 .. option:: fsync_on_close=bool
1452 If true, fio will :manpage:`fsync(2)` a dirty file on close. This differs
1453 from :option:`end_fsync` in that it will happen on every file close, not
1454 just at the end of the job. Default: false.
1456 .. option:: rwmixread=int
1458 Percentage of a mixed workload that should be reads. Default: 50.
1460 .. option:: rwmixwrite=int
1462 Percentage of a mixed workload that should be writes. If both
1463 :option:`rwmixread` and :option:`rwmixwrite` is given and the values do not
1464 add up to 100%, the latter of the two will be used to override the
1465 first. This may interfere with a given rate setting, if fio is asked to
1466 limit reads or writes to a certain rate. If that is the case, then the
1467 distribution may be skewed. Default: 50.
1469 .. option:: random_distribution=str:float[:float][,str:float][,str:float]
1471 By default, fio will use a completely uniform random distribution when asked
1472 to perform random I/O. Sometimes it is useful to skew the distribution in
1473 specific ways, ensuring that some parts of the data is more hot than others.
1474 fio includes the following distribution models:
1477 Uniform random distribution
1486 Normal (Gaussian) distribution
1489 Zoned random distribution
1492 Zone absolute random distribution
1494 When using a **zipf** or **pareto** distribution, an input value is also
1495 needed to define the access pattern. For **zipf**, this is the `Zipf
1496 theta`. For **pareto**, it's the `Pareto power`. Fio includes a test
1497 program, :command:`fio-genzipf`, that can be used visualize what the given input
1498 values will yield in terms of hit rates. If you wanted to use **zipf** with
1499 a `theta` of 1.2, you would use ``random_distribution=zipf:1.2`` as the
1500 option. If a non-uniform model is used, fio will disable use of the random
1501 map. For the **normal** distribution, a normal (Gaussian) deviation is
1502 supplied as a value between 0 and 100.
1504 The second, optional float is allowed for **pareto**, **zipf** and **normal** distributions.
1505 It allows one to set base of distribution in non-default place, giving more control
1506 over most probable outcome. This value is in range [0-1] which maps linearly to
1507 range of possible random values.
1508 Defaults are: random for **pareto** and **zipf**, and 0.5 for **normal**.
1509 If you wanted to use **zipf** with a `theta` of 1.2 centered on 1/4 of allowed value range,
1510 you would use ``random_distribution=zipf:1.2:0.25``.
1512 For a **zoned** distribution, fio supports specifying percentages of I/O
1513 access that should fall within what range of the file or device. For
1514 example, given a criteria of:
1516 * 60% of accesses should be to the first 10%
1517 * 30% of accesses should be to the next 20%
1518 * 8% of accesses should be to the next 30%
1519 * 2% of accesses should be to the next 40%
1521 we can define that through zoning of the random accesses. For the above
1522 example, the user would do::
1524 random_distribution=zoned:60/10:30/20:8/30:2/40
1526 A **zoned_abs** distribution works exactly like the **zoned**, except
1527 that it takes absolute sizes. For example, let's say you wanted to
1528 define access according to the following criteria:
1530 * 60% of accesses should be to the first 20G
1531 * 30% of accesses should be to the next 100G
1532 * 10% of accesses should be to the next 500G
1534 we can define an absolute zoning distribution with:
1536 random_distribution=zoned_abs=60/20G:30/100G:10/500g
1538 For both **zoned** and **zoned_abs**, fio supports defining up to
1541 Similarly to how :option:`bssplit` works for setting ranges and
1542 percentages of block sizes. Like :option:`bssplit`, it's possible to
1543 specify separate zones for reads, writes, and trims. If just one set
1544 is given, it'll apply to all of them. This goes for both **zoned**
1545 **zoned_abs** distributions.
1547 .. option:: percentage_random=int[,int][,int]
1549 For a random workload, set how big a percentage should be random. This
1550 defaults to 100%, in which case the workload is fully random. It can be set
1551 from anywhere from 0 to 100. Setting it to 0 would make the workload fully
1552 sequential. Any setting in between will result in a random mix of sequential
1553 and random I/O, at the given percentages. Comma-separated values may be
1554 specified for reads, writes, and trims as described in :option:`blocksize`.
1556 .. option:: norandommap
1558 Normally fio will cover every block of the file when doing random I/O. If
1559 this option is given, fio will just get a new random offset without looking
1560 at past I/O history. This means that some blocks may not be read or written,
1561 and that some blocks may be read/written more than once. If this option is
1562 used with :option:`verify` and multiple blocksizes (via :option:`bsrange`),
1563 only intact blocks are verified, i.e., partially-overwritten blocks are
1564 ignored. With an async I/O engine and an I/O depth > 1, it is possible for
1565 the same block to be overwritten, which can cause verification errors. Either
1566 do not use norandommap in this case, or also use the lfsr random generator.
1568 .. option:: softrandommap=bool
1570 See :option:`norandommap`. If fio runs with the random block map enabled and
1571 it fails to allocate the map, if this option is set it will continue without
1572 a random block map. As coverage will not be as complete as with random maps,
1573 this option is disabled by default.
1575 .. option:: random_generator=str
1577 Fio supports the following engines for generating I/O offsets for random I/O:
1580 Strong 2^88 cycle random number generator.
1582 Linear feedback shift register generator.
1584 Strong 64-bit 2^258 cycle random number generator.
1586 **tausworthe** is a strong random number generator, but it requires tracking
1587 on the side if we want to ensure that blocks are only read or written
1588 once. **lfsr** guarantees that we never generate the same offset twice, and
1589 it's also less computationally expensive. It's not a true random generator,
1590 however, though for I/O purposes it's typically good enough. **lfsr** only
1591 works with single block sizes, not with workloads that use multiple block
1592 sizes. If used with such a workload, fio may read or write some blocks
1593 multiple times. The default value is **tausworthe**, unless the required
1594 space exceeds 2^32 blocks. If it does, then **tausworthe64** is
1595 selected automatically.
1601 .. option:: blocksize=int[,int][,int], bs=int[,int][,int]
1603 The block size in bytes used for I/O units. Default: 4096. A single value
1604 applies to reads, writes, and trims. Comma-separated values may be
1605 specified for reads, writes, and trims. A value not terminated in a comma
1606 applies to subsequent types.
1611 means 256k for reads, writes and trims.
1614 means 8k for reads, 32k for writes and trims.
1617 means 8k for reads, 32k for writes, and default for trims.
1620 means default for reads, 8k for writes and trims.
1623 means default for reads, 8k for writes, and default for trims.
1625 .. option:: blocksize_range=irange[,irange][,irange], bsrange=irange[,irange][,irange]
1627 A range of block sizes in bytes for I/O units. The issued I/O unit will
1628 always be a multiple of the minimum size, unless
1629 :option:`blocksize_unaligned` is set.
1631 Comma-separated ranges may be specified for reads, writes, and trims as
1632 described in :option:`blocksize`.
1634 Example: ``bsrange=1k-4k,2k-8k`` also the ':' delimiter ``bsrange=1k:4k,2k:8k``.
1636 .. option:: bssplit=str[,str][,str]
1638 Sometimes you want even finer grained control of the block sizes
1639 issued, not just an even split between them. This option allows you to
1640 weight various block sizes, so that you are able to define a specific
1641 amount of block sizes issued. The format for this option is::
1643 bssplit=blocksize/percentage:blocksize/percentage
1645 for as many block sizes as needed. So if you want to define a workload
1646 that has 50% 64k blocks, 10% 4k blocks, and 40% 32k blocks, you would
1649 bssplit=4k/10:64k/50:32k/40
1651 Ordering does not matter. If the percentage is left blank, fio will
1652 fill in the remaining values evenly. So a bssplit option like this one::
1654 bssplit=4k/50:1k/:32k/
1656 would have 50% 4k ios, and 25% 1k and 32k ios. The percentages always
1657 add up to 100, if bssplit is given a range that adds up to more, it
1660 Comma-separated values may be specified for reads, writes, and trims as
1661 described in :option:`blocksize`.
1663 If you want a workload that has 50% 2k reads and 50% 4k reads, while
1664 having 90% 4k writes and 10% 8k writes, you would specify::
1666 bssplit=2k/50:4k/50,4k/90:8k/10
1668 Fio supports defining up to 64 different weights for each data
1671 .. option:: blocksize_unaligned, bs_unaligned
1673 If set, fio will issue I/O units with any size within
1674 :option:`blocksize_range`, not just multiples of the minimum size. This
1675 typically won't work with direct I/O, as that normally requires sector
1678 .. option:: bs_is_seq_rand=bool
1680 If this option is set, fio will use the normal read,write blocksize settings
1681 as sequential,random blocksize settings instead. Any random read or write
1682 will use the WRITE blocksize settings, and any sequential read or write will
1683 use the READ blocksize settings.
1685 .. option:: blockalign=int[,int][,int], ba=int[,int][,int]
1687 Boundary to which fio will align random I/O units. Default:
1688 :option:`blocksize`. Minimum alignment is typically 512b for using direct
1689 I/O, though it usually depends on the hardware block size. This option is
1690 mutually exclusive with using a random map for files, so it will turn off
1691 that option. Comma-separated values may be specified for reads, writes, and
1692 trims as described in :option:`blocksize`.
1698 .. option:: zero_buffers
1700 Initialize buffers with all zeros. Default: fill buffers with random data.
1702 .. option:: refill_buffers
1704 If this option is given, fio will refill the I/O buffers on every
1705 submit. Only makes sense if :option:`zero_buffers` isn't specified,
1706 naturally. Defaults to being unset i.e., the buffer is only filled at
1707 init time and the data in it is reused when possible but if any of
1708 :option:`verify`, :option:`buffer_compress_percentage` or
1709 :option:`dedupe_percentage` are enabled then `refill_buffers` is also
1710 automatically enabled.
1712 .. option:: scramble_buffers=bool
1714 If :option:`refill_buffers` is too costly and the target is using data
1715 deduplication, then setting this option will slightly modify the I/O buffer
1716 contents to defeat normal de-dupe attempts. This is not enough to defeat
1717 more clever block compression attempts, but it will stop naive dedupe of
1718 blocks. Default: true.
1720 .. option:: buffer_compress_percentage=int
1722 If this is set, then fio will attempt to provide I/O buffer content
1723 (on WRITEs) that compresses to the specified level. Fio does this by
1724 providing a mix of random data followed by fixed pattern data. The
1725 fixed pattern is either zeros, or the pattern specified by
1726 :option:`buffer_pattern`. If the `buffer_pattern` option is used, it
1727 might skew the compression ratio slightly. Setting
1728 `buffer_compress_percentage` to a value other than 100 will also
1729 enable :option:`refill_buffers` in order to reduce the likelihood that
1730 adjacent blocks are so similar that they over compress when seen
1731 together. See :option:`buffer_compress_chunk` for how to set a finer or
1732 coarser granularity for the random/fixed data region. Defaults to unset
1733 i.e., buffer data will not adhere to any compression level.
1735 .. option:: buffer_compress_chunk=int
1737 This setting allows fio to manage how big the random/fixed data region
1738 is when using :option:`buffer_compress_percentage`. When
1739 `buffer_compress_chunk` is set to some non-zero value smaller than the
1740 block size, fio can repeat the random/fixed region throughout the I/O
1741 buffer at the specified interval (which particularly useful when
1742 bigger block sizes are used for a job). When set to 0, fio will use a
1743 chunk size that matches the block size resulting in a single
1744 random/fixed region within the I/O buffer. Defaults to 512. When the
1745 unit is omitted, the value is interpreted in bytes.
1747 .. option:: buffer_pattern=str
1749 If set, fio will fill the I/O buffers with this pattern or with the contents
1750 of a file. If not set, the contents of I/O buffers are defined by the other
1751 options related to buffer contents. The setting can be any pattern of bytes,
1752 and can be prefixed with 0x for hex values. It may also be a string, where
1753 the string must then be wrapped with ``""``. Or it may also be a filename,
1754 where the filename must be wrapped with ``''`` in which case the file is
1755 opened and read. Note that not all the file contents will be read if that
1756 would cause the buffers to overflow. So, for example::
1758 buffer_pattern='filename'
1762 buffer_pattern="abcd"
1770 buffer_pattern=0xdeadface
1772 Also you can combine everything together in any order::
1774 buffer_pattern=0xdeadface"abcd"-12'filename'
1776 .. option:: dedupe_percentage=int
1778 If set, fio will generate this percentage of identical buffers when
1779 writing. These buffers will be naturally dedupable. The contents of the
1780 buffers depend on what other buffer compression settings have been set. It's
1781 possible to have the individual buffers either fully compressible, or not at
1782 all -- this option only controls the distribution of unique buffers. Setting
1783 this option will also enable :option:`refill_buffers` to prevent every buffer
1786 .. option:: dedupe_mode=str
1788 If ``dedupe_percentage=<int>`` is given, then this option controls how fio
1789 generates the dedupe buffers.
1792 Generate dedupe buffers by repeating previous writes
1794 Generate dedupe buffers from working set
1796 ``repeat`` is the default option for fio. Dedupe buffers are generated
1797 by repeating previous unique write.
1799 ``working_set`` is a more realistic workload.
1800 With ``working_set``, ``dedupe_working_set_percentage=<int>`` should be provided.
1801 Given that, fio will use the initial unique write buffers as its working set.
1802 Upon deciding to dedupe, fio will randomly choose a buffer from the working set.
1803 Note that by using ``working_set`` the dedupe percentage will converge
1804 to the desired over time while ``repeat`` maintains the desired percentage
1807 .. option:: dedupe_working_set_percentage=int
1809 If ``dedupe_mode=<str>`` is set to ``working_set``, then this controls
1810 the percentage of size of the file or device used as the buffers
1811 fio will choose to generate the dedupe buffers from
1813 Note that size needs to be explicitly provided and only 1 file per
1816 .. option:: dedupe_global=bool
1818 This controls whether the deduplication buffers will be shared amongst
1819 all jobs that have this option set. The buffers are spread evenly between
1822 .. option:: invalidate=bool
1824 Invalidate the buffer/page cache parts of the files to be used prior to
1825 starting I/O if the platform and file type support it. Defaults to true.
1826 This will be ignored if :option:`pre_read` is also specified for the
1829 .. option:: sync=str
1831 Whether, and what type, of synchronous I/O to use for writes. The allowed
1835 Do not use synchronous IO, the default.
1841 Use synchronous file IO. For the majority of I/O engines,
1842 this means using O_SYNC.
1848 Use synchronous data IO. For the majority of I/O engines,
1849 this means using O_DSYNC.
1852 .. option:: iomem=str, mem=str
1854 Fio can use various types of memory as the I/O unit buffer. The allowed
1858 Use memory from :manpage:`malloc(3)` as the buffers. Default memory
1862 Use shared memory as the buffers. Allocated through
1863 :manpage:`shmget(2)`.
1866 Same as shm, but use huge pages as backing.
1869 Use :manpage:`mmap(2)` to allocate buffers. May either be anonymous memory, or can
1870 be file backed if a filename is given after the option. The format
1871 is `mem=mmap:/path/to/file`.
1874 Use a memory mapped huge file as the buffer backing. Append filename
1875 after mmaphuge, ala `mem=mmaphuge:/hugetlbfs/file`.
1878 Same as mmap, but use a MMAP_SHARED mapping.
1881 Use GPU memory as the buffers for GPUDirect RDMA benchmark.
1882 The :option:`ioengine` must be `rdma`.
1884 The area allocated is a function of the maximum allowed bs size for the job,
1885 multiplied by the I/O depth given. Note that for **shmhuge** and
1886 **mmaphuge** to work, the system must have free huge pages allocated. This
1887 can normally be checked and set by reading/writing
1888 :file:`/proc/sys/vm/nr_hugepages` on a Linux system. Fio assumes a huge page
1889 is 2 or 4MiB in size depending on the platform. So to calculate the
1890 number of huge pages you need for a given job file, add up the I/O
1891 depth of all jobs (normally one unless :option:`iodepth` is used) and
1892 multiply by the maximum bs set. Then divide that number by the huge
1893 page size. You can see the size of the huge pages in
1894 :file:`/proc/meminfo`. If no huge pages are allocated by having a
1895 non-zero number in `nr_hugepages`, using **mmaphuge** or **shmhuge**
1896 will fail. Also see :option:`hugepage-size`.
1898 **mmaphuge** also needs to have hugetlbfs mounted and the file location
1899 should point there. So if it's mounted in :file:`/huge`, you would use
1900 `mem=mmaphuge:/huge/somefile`.
1902 .. option:: iomem_align=int, mem_align=int
1904 This indicates the memory alignment of the I/O memory buffers. Note that
1905 the given alignment is applied to the first I/O unit buffer, if using
1906 :option:`iodepth` the alignment of the following buffers are given by the
1907 :option:`bs` used. In other words, if using a :option:`bs` that is a
1908 multiple of the page sized in the system, all buffers will be aligned to
1909 this value. If using a :option:`bs` that is not page aligned, the alignment
1910 of subsequent I/O memory buffers is the sum of the :option:`iomem_align` and
1913 .. option:: hugepage-size=int
1915 Defines the size of a huge page. Must at least be equal to the system
1916 setting, see :file:`/proc/meminfo` and
1917 :file:`/sys/kernel/mm/hugepages/`. Defaults to 2 or 4MiB depending on
1918 the platform. Should probably always be a multiple of megabytes, so
1919 using ``hugepage-size=Xm`` is the preferred way to set this to avoid
1920 setting a non-pow-2 bad value.
1922 .. option:: lockmem=int
1924 Pin the specified amount of memory with :manpage:`mlock(2)`. Can be used to
1925 simulate a smaller amount of memory. The amount specified is per worker.
1931 .. option:: size=int
1933 The total size of file I/O for each thread of this job. Fio will run until
1934 this many bytes has been transferred, unless runtime is altered by other means
1935 such as (1) :option:`runtime`, (2) :option:`io_size` (3) :option:`number_ios`,
1936 (4) gaps/holes while doing I/O's such as ``rw=read:16K``, or (5) sequential
1937 I/O reaching end of the file which is possible when :option:`percentage_random`
1939 Fio will divide this size between the available files determined by options
1940 such as :option:`nrfiles`, :option:`filename`, unless :option:`filesize` is
1941 specified by the job. If the result of division happens to be 0, the size is
1942 set to the physical size of the given files or devices if they exist.
1943 If this option is not specified, fio will use the full size of the given
1944 files or devices. If the files do not exist, size must be given. It is also
1945 possible to give size as a percentage between 1 and 100. If ``size=20%`` is
1946 given, fio will use 20% of the full size of the given files or devices.
1947 In ZBD mode, value can also be set as number of zones using 'z'.
1948 Can be combined with :option:`offset` to constrain the start and end range
1949 that I/O will be done within.
1951 .. option:: io_size=int, io_limit=int
1953 Normally fio operates within the region set by :option:`size`, which means
1954 that the :option:`size` option sets both the region and size of I/O to be
1955 performed. Sometimes that is not what you want. With this option, it is
1956 possible to define just the amount of I/O that fio should do. For instance,
1957 if :option:`size` is set to 20GiB and :option:`io_size` is set to 5GiB, fio
1958 will perform I/O within the first 20GiB but exit when 5GiB have been
1959 done. The opposite is also possible -- if :option:`size` is set to 20GiB,
1960 and :option:`io_size` is set to 40GiB, then fio will do 40GiB of I/O within
1961 the 0..20GiB region.
1963 .. option:: filesize=irange(int)
1965 Individual file sizes. May be a range, in which case fio will select sizes for
1966 files at random within the given range. If not given, each created file is the
1967 same size. This option overrides :option:`size` in terms of file size, i.e. if
1968 :option:`filesize` is specified then :option:`size` becomes merely the default
1969 for :option:`io_size` and has no effect at all if :option:`io_size` is set
1972 .. option:: file_append=bool
1974 Perform I/O after the end of the file. Normally fio will operate within the
1975 size of a file. If this option is set, then fio will append to the file
1976 instead. This has identical behavior to setting :option:`offset` to the size
1977 of a file. This option is ignored on non-regular files.
1979 .. option:: fill_device=bool, fill_fs=bool
1981 Sets size to something really large and waits for ENOSPC (no space left on
1982 device) or EDQUOT (disk quota exceeded)
1983 as the terminating condition. Only makes sense with sequential
1984 write. For a read workload, the mount point will be filled first then I/O
1985 started on the result. This option doesn't make sense if operating on a raw
1986 device node, since the size of that is already known by the file system.
1987 Additionally, writing beyond end-of-device will not return ENOSPC there.
1993 .. option:: ioengine=str
1995 fio supports 2 kinds of performance measurement: I/O and file/directory operation.
1997 I/O engines define how the job issues I/O to the file. The following types are defined:
2000 Basic :manpage:`read(2)` or :manpage:`write(2)`
2001 I/O. :manpage:`lseek(2)` is used to position the I/O location.
2002 See :option:`fsync` and :option:`fdatasync` for syncing write I/Os.
2005 Basic :manpage:`pread(2)` or :manpage:`pwrite(2)` I/O. Default on
2006 all supported operating systems except for Windows.
2009 Basic :manpage:`readv(2)` or :manpage:`writev(2)` I/O. Will emulate
2010 queuing by coalescing adjacent I/Os into a single submission.
2013 Basic :manpage:`preadv(2)` or :manpage:`pwritev(2)` I/O.
2016 Basic :manpage:`preadv2(2)` or :manpage:`pwritev2(2)` I/O.
2019 Fast Linux native asynchronous I/O. Supports async IO
2020 for both direct and buffered IO.
2021 This engine defines engine specific options.
2024 Fast Linux native asynchronous I/O for pass through commands.
2025 This engine defines engine specific options.
2028 Linux native asynchronous I/O. Note that Linux may only support
2029 queued behavior with non-buffered I/O (set ``direct=1`` or
2031 This engine defines engine specific options.
2034 POSIX asynchronous I/O using :manpage:`aio_read(3)` and
2035 :manpage:`aio_write(3)`.
2038 Solaris native asynchronous I/O.
2041 Windows native asynchronous I/O. Default on Windows.
2044 File is memory mapped with :manpage:`mmap(2)` and data copied
2045 to/from using :manpage:`memcpy(3)`.
2048 :manpage:`splice(2)` is used to transfer the data and
2049 :manpage:`vmsplice(2)` to transfer data from user space to the
2053 SCSI generic sg v3 I/O. May either be synchronous using the SG_IO
2054 ioctl, or if the target is an sg character device we use
2055 :manpage:`read(2)` and :manpage:`write(2)` for asynchronous
2056 I/O. Requires :option:`filename` option to specify either block or
2057 character devices. This engine supports trim operations.
2058 The sg engine includes engine specific options.
2061 Read, write, trim and ZBC/ZAC operations to a zoned
2062 block device using libzbc library. The target can be
2063 either an SG character device or a block device file.
2066 Doesn't transfer any data, just pretends to. This is mainly used to
2067 exercise fio itself and for debugging/testing purposes.
2070 Transfer over the network to given ``host:port``. Depending on the
2071 :option:`protocol` used, the :option:`hostname`, :option:`port`,
2072 :option:`listen` and :option:`filename` options are used to specify
2073 what sort of connection to make, while the :option:`protocol` option
2074 determines which protocol will be used. This engine defines engine
2078 Like **net**, but uses :manpage:`splice(2)` and
2079 :manpage:`vmsplice(2)` to map data and send/receive.
2080 This engine defines engine specific options.
2083 Doesn't transfer any data, but burns CPU cycles according to the
2084 :option:`cpuload`, :option:`cpuchunks` and :option:`cpumode` options.
2085 Setting :option:`cpuload`\=85 will cause that job to do nothing but burn 85%
2086 of the CPU. In case of SMP machines, use :option:`numjobs`\=<nr_of_cpu>
2087 to get desired CPU usage, as the cpuload only loads a
2088 single CPU at the desired rate. A job never finishes unless there is
2089 at least one non-cpuio job.
2090 Setting :option:`cpumode`\=qsort replace the default noop instructions loop
2091 by a qsort algorithm to consume more energy.
2094 The RDMA I/O engine supports both RDMA memory semantics
2095 (RDMA_WRITE/RDMA_READ) and channel semantics (Send/Recv) for the
2096 InfiniBand, RoCE and iWARP protocols. This engine defines engine
2100 I/O engine that does regular fallocate to simulate data transfer as
2104 does fallocate(,mode = FALLOC_FL_KEEP_SIZE,).
2107 does fallocate(,mode = 0).
2110 does fallocate(,mode = FALLOC_FL_KEEP_SIZE|FALLOC_FL_PUNCH_HOLE).
2113 I/O engine that sends :manpage:`ftruncate(2)` operations in response
2114 to write (DDIR_WRITE) events. Each ftruncate issued sets the file's
2115 size to the current block offset. :option:`blocksize` is ignored.
2118 I/O engine that does regular EXT4_IOC_MOVE_EXT ioctls to simulate
2119 defragment activity in request to DDIR_WRITE event.
2122 I/O engine supporting direct access to Ceph Reliable Autonomic
2123 Distributed Object Store (RADOS) via librados. This ioengine
2124 defines engine specific options.
2127 I/O engine supporting direct access to Ceph Rados Block Devices
2128 (RBD) via librbd without the need to use the kernel rbd driver. This
2129 ioengine defines engine specific options.
2132 I/O engine supporting GET/PUT requests over HTTP(S) with libcurl to
2133 a WebDAV or S3 endpoint. This ioengine defines engine specific options.
2135 This engine only supports direct IO of iodepth=1; you need to scale this
2136 via numjobs. blocksize defines the size of the objects to be created.
2138 TRIM is translated to object deletion.
2141 Using GlusterFS libgfapi sync interface to direct access to
2142 GlusterFS volumes without having to go through FUSE. This ioengine
2143 defines engine specific options.
2146 Using GlusterFS libgfapi async interface to direct access to
2147 GlusterFS volumes without having to go through FUSE. This ioengine
2148 defines engine specific options.
2151 Read and write through Hadoop (HDFS). The :option:`filename` option
2152 is used to specify host,port of the hdfs name-node to connect. This
2153 engine interprets offsets a little differently. In HDFS, files once
2154 created cannot be modified so random writes are not possible. To
2155 imitate this the libhdfs engine expects a bunch of small files to be
2156 created over HDFS and will randomly pick a file from them
2157 based on the offset generated by fio backend (see the example
2158 job file to create such files, use ``rw=write`` option). Please
2159 note, it may be necessary to set environment variables to work
2160 with HDFS/libhdfs properly. Each job uses its own connection to
2164 Read, write and erase an MTD character device (e.g.,
2165 :file:`/dev/mtd0`). Discards are treated as erases. Depending on the
2166 underlying device type, the I/O may have to go in a certain pattern,
2167 e.g., on NAND, writing sequentially to erase blocks and discarding
2168 before overwriting. The `trimwrite` mode works well for this
2172 Read and write using device DAX to a persistent memory device (e.g.,
2173 /dev/dax0.0) through the PMDK libpmem library.
2176 Prefix to specify loading an external I/O engine object file. Append
2177 the engine filename, e.g. ``ioengine=external:/tmp/foo.o`` to load
2178 ioengine :file:`foo.o` in :file:`/tmp`. The path can be either
2179 absolute or relative. See :file:`engines/skeleton_external.c` for
2180 details of writing an external I/O engine.
2183 Read and write using mmap I/O to a file on a filesystem
2184 mounted with DAX on a persistent memory device through the PMDK
2188 Synchronous read and write using DDN's Infinite Memory Engine (IME).
2189 This engine is very basic and issues calls to IME whenever an IO is
2193 Synchronous read and write using DDN's Infinite Memory Engine (IME).
2194 This engine uses iovecs and will try to stack as much IOs as possible
2195 (if the IOs are "contiguous" and the IO depth is not exceeded)
2196 before issuing a call to IME.
2199 Asynchronous read and write using DDN's Infinite Memory Engine (IME).
2200 This engine will try to stack as much IOs as possible by creating
2201 requests for IME. FIO will then decide when to commit these requests.
2204 Read and write iscsi lun with libiscsi.
2207 Read and write a Network Block Device (NBD).
2210 I/O engine supporting libcufile synchronous access to nvidia-fs and a
2211 GPUDirect Storage-supported filesystem. This engine performs
2212 I/O without transferring buffers between user-space and the kernel,
2213 unless :option:`verify` is set or :option:`cuda_io` is `posix`.
2214 :option:`iomem` must not be `cudamalloc`. This ioengine defines
2215 engine specific options.
2218 I/O engine supporting asynchronous read and write operations to the
2219 DAOS File System (DFS) via libdfs.
2222 I/O engine supporting asynchronous read and write operations to
2223 NFS filesystems from userspace via libnfs. This is useful for
2224 achieving higher concurrency and thus throughput than is possible
2228 Execute 3rd party tools. Could be used to perform monitoring during jobs runtime.
2231 I/O engine using the xNVMe C API, for NVMe devices. The xnvme engine provides
2232 flexibility to access GNU/Linux Kernel NVMe driver via libaio, IOCTLs, io_uring,
2233 the SPDK NVMe driver, or your own custom NVMe driver. The xnvme engine includes
2234 engine specific options. (See https://xnvme.io).
2237 Use the libblkio library
2238 (https://gitlab.com/libblkio/libblkio). The specific
2239 *driver* to use must be set using
2240 :option:`libblkio_driver`. If
2241 :option:`mem`/:option:`iomem` is not specified, memory
2242 allocation is delegated to libblkio (and so is
2243 guaranteed to work with the selected *driver*). One
2244 libblkio instance is used per process, so all jobs
2245 setting option :option:`thread` will share a single
2246 instance (with one queue per thread) and must specify
2247 compatible options. Note that some drivers don't allow
2248 several instances to access the same device or file
2249 simultaneously, but allow it for threads.
2251 File/directory operation engines define how the job operates file or directory. The
2252 following types are defined:
2255 Simply create the files and do no I/O to them. You still need to
2256 set `filesize` so that all the accounting still occurs, but no
2257 actual I/O will be done other than creating the file.
2258 Example job file: filecreate-ioengine.fio.
2261 Simply do stat() and do no I/O to the file. You need to set 'filesize'
2262 and 'nrfiles', so that files will be created.
2263 This engine is to measure file lookup and meta data access.
2264 Example job file: filestat-ioengine.fio.
2267 Simply delete the files by unlink() and do no I/O to them. You need to set 'filesize'
2268 and 'nrfiles', so that the files will be created.
2269 This engine is to measure file delete.
2270 Example job file: filedelete-ioengine.fio.
2273 Simply create the directories and do no I/O to them. You still need to
2274 set `filesize` so that all the accounting still occurs, but no
2275 actual I/O will be done other than creating the directories.
2276 Example job file: dircreate-ioengine.fio.
2279 Simply do stat() and do no I/O to the directories. You need to set 'filesize'
2280 and 'nrfiles', so that directories will be created.
2281 This engine is to measure directory lookup and meta data access.
2282 Example job file: dirstat-ioengine.fio.
2285 Simply delete the directories by rmdir() and do no I/O to them. You need to set 'filesize'
2286 and 'nrfiles', so that the directories will be created.
2287 This engine is to measure directory delete.
2288 Example job file: dirdelete-ioengine.fio.
2290 For file and directory operation engines, there is no I/O throughput, then the
2291 statistics data in report have different meanings. The meaningful output indexes are: 'iops' and 'clat'.
2292 'bw' is meaningless. Refer to section: "Interpreting the output" for more details.
2295 I/O engine specific parameters
2296 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2298 In addition, there are some parameters which are only valid when a specific
2299 :option:`ioengine` is in use. These are used identically to normal parameters,
2300 with the caveat that when used on the command line, they must come after the
2301 :option:`ioengine` that defines them is selected.
2303 .. option:: cmdprio_percentage=int[,int] : [io_uring] [libaio]
2305 Set the percentage of I/O that will be issued with the highest priority.
2306 Default: 0. A single value applies to reads and writes. Comma-separated
2307 values may be specified for reads and writes. For this option to be
2308 effective, NCQ priority must be supported and enabled, and the :option:`direct`
2309 option must be set. fio must also be run as the root user. Unlike
2310 slat/clat/lat stats, which can be tracked and reported independently, per
2311 priority stats only track and report a single type of latency. By default,
2312 completion latency (clat) will be reported, if :option:`lat_percentiles` is
2313 set, total latency (lat) will be reported.
2315 .. option:: cmdprio_class=int[,int] : [io_uring] [libaio]
2317 Set the I/O priority class to use for I/Os that must be issued with
2318 a priority when :option:`cmdprio_percentage` or
2319 :option:`cmdprio_bssplit` is set. If not specified when
2320 :option:`cmdprio_percentage` or :option:`cmdprio_bssplit` is set,
2321 this defaults to the highest priority class. A single value applies
2322 to reads and writes. Comma-separated values may be specified for
2323 reads and writes. See :manpage:`ionice(1)`. See also the
2324 :option:`prioclass` option.
2326 .. option:: cmdprio_hint=int[,int] : [io_uring] [libaio]
2328 Set the I/O priority hint to use for I/Os that must be issued with
2329 a priority when :option:`cmdprio_percentage` or
2330 :option:`cmdprio_bssplit` is set. If not specified when
2331 :option:`cmdprio_percentage` or :option:`cmdprio_bssplit` is set,
2332 this defaults to 0 (no hint). A single value applies to reads and
2333 writes. Comma-separated values may be specified for reads and writes.
2334 See also the :option:`priohint` option.
2336 .. option:: cmdprio=int[,int] : [io_uring] [libaio]
2338 Set the I/O priority value to use for I/Os that must be issued with
2339 a priority when :option:`cmdprio_percentage` or
2340 :option:`cmdprio_bssplit` is set. If not specified when
2341 :option:`cmdprio_percentage` or :option:`cmdprio_bssplit` is set,
2343 Linux limits us to a positive value between 0 and 7, with 0 being the
2344 highest. A single value applies to reads and writes. Comma-separated
2345 values may be specified for reads and writes. See :manpage:`ionice(1)`.
2346 Refer to an appropriate manpage for other operating systems since
2347 meaning of priority may differ. See also the :option:`prio` option.
2349 .. option:: cmdprio_bssplit=str[,str] : [io_uring] [libaio]
2351 To get a finer control over I/O priority, this option allows
2352 specifying the percentage of IOs that must have a priority set
2353 depending on the block size of the IO. This option is useful only
2354 when used together with the :option:`bssplit` option, that is,
2355 multiple different block sizes are used for reads and writes.
2357 The first accepted format for this option is the same as the format of
2358 the :option:`bssplit` option:
2360 cmdprio_bssplit=blocksize/percentage:blocksize/percentage
2362 In this case, each entry will use the priority class, priority hint
2363 and priority level defined by the options :option:`cmdprio_class`,
2364 :option:`cmdprio` and :option:`cmdprio_hint` respectively.
2366 The second accepted format for this option is:
2368 cmdprio_bssplit=blocksize/percentage/class/level:blocksize/percentage/class/level
2370 In this case, the priority class and priority level is defined inside
2371 each entry. In comparison with the first accepted format, the second
2372 accepted format does not restrict all entries to have the same priority
2373 class and priority level.
2375 The third accepted format for this option is:
2377 cmdprio_bssplit=blocksize/percentage/class/level/hint:...
2379 This is an extension of the second accepted format that allows one to
2380 also specify a priority hint.
2382 For all formats, only the read and write data directions are supported,
2383 values for trim IOs are ignored. This option is mutually exclusive with
2384 the :option:`cmdprio_percentage` option.
2386 .. option:: fixedbufs : [io_uring] [io_uring_cmd]
2388 If fio is asked to do direct IO, then Linux will map pages for each
2389 IO call, and release them when IO is done. If this option is set, the
2390 pages are pre-mapped before IO is started. This eliminates the need to
2391 map and release for each IO. This is more efficient, and reduces the
2394 .. option:: nonvectored=int : [io_uring] [io_uring_cmd]
2396 With this option, fio will use non-vectored read/write commands, where
2397 address must contain the address directly. Default is -1.
2399 .. option:: force_async=int : [io_uring] [io_uring_cmd]
2401 Normal operation for io_uring is to try and issue an sqe as
2402 non-blocking first, and if that fails, execute it in an async manner.
2403 With this option set to N, then every N request fio will ask sqe to
2404 be issued in an async manner. Default is 0.
2406 .. option:: registerfiles : [io_uring] [io_uring_cmd]
2408 With this option, fio registers the set of files being used with the
2409 kernel. This avoids the overhead of managing file counts in the kernel,
2410 making the submission and completion part more lightweight. Required
2411 for the below :option:`sqthread_poll` option.
2413 .. option:: sqthread_poll : [io_uring] [io_uring_cmd] [xnvme]
2415 Normally fio will submit IO by issuing a system call to notify the
2416 kernel of available items in the SQ ring. If this option is set, the
2417 act of submitting IO will be done by a polling thread in the kernel.
2418 This frees up cycles for fio, at the cost of using more CPU in the
2419 system. As submission is just the time it takes to fill in the sqe
2420 entries and any syscall required to wake up the idle kernel thread,
2421 fio will not report submission latencies.
2423 .. option:: sqthread_poll_cpu=int : [io_uring] [io_uring_cmd]
2425 When :option:`sqthread_poll` is set, this option provides a way to
2426 define which CPU should be used for the polling thread.
2428 .. option:: cmd_type=str : [io_uring_cmd]
2430 Specifies the type of uring passthrough command to be used. Supported
2431 value is nvme. Default is nvme.
2435 [io_uring] [io_uring_cmd] [xnvme]
2437 If this option is set, fio will attempt to use polled IO completions.
2438 Normal IO completions generate interrupts to signal the completion of
2439 IO, polled completions do not. Hence they are require active reaping
2440 by the application. The benefits are more efficient IO for high IOPS
2441 scenarios, and lower latencies for low queue depth IO.
2445 Use poll queues. This is incompatible with
2446 :option:`libblkio_wait_mode=eventfd <libblkio_wait_mode>` and
2447 :option:`libblkio_force_enable_completion_eventfd`.
2451 Set RWF_HIPRI on I/O, indicating to the kernel that it's of higher priority
2456 If this option is set, fio will attempt to use polled IO completions.
2457 This will have a similar effect as (io_uring)hipri. Only SCSI READ and
2458 WRITE commands will have the SGV4_FLAG_HIPRI set (not UNMAP (trim) nor
2459 VERIFY). Older versions of the Linux sg driver that do not support
2460 hipri will simply ignore this flag and do normal IO. The Linux SCSI
2461 Low Level Driver (LLD) that "owns" the device also needs to support
2462 hipri (also known as iopoll and mq_poll). The MegaRAID driver is an
2463 example of a SCSI LLD. Default: clear (0) which does normal
2464 (interrupted based) IO.
2466 .. option:: userspace_reap : [libaio]
2468 Normally, with the libaio engine in use, fio will use the
2469 :manpage:`io_getevents(2)` system call to reap newly returned events. With
2470 this flag turned on, the AIO ring will be read directly from user-space to
2471 reap events. The reaping mode is only enabled when polling for a minimum of
2472 0 events (e.g. when :option:`iodepth_batch_complete` `=0`).
2474 .. option:: hipri_percentage : [pvsync2]
2476 When hipri is set this determines the probability of a pvsync2 I/O being high
2477 priority. The default is 100%.
2479 .. option:: nowait=bool : [pvsync2] [libaio] [io_uring] [io_uring_cmd]
2481 By default if a request cannot be executed immediately (e.g. resource starvation,
2482 waiting on locks) it is queued and the initiating process will be blocked until
2483 the required resource becomes free.
2485 This option sets the RWF_NOWAIT flag (supported from the 4.14 Linux kernel) and
2486 the call will return instantly with EAGAIN or a partial result rather than waiting.
2488 It is useful to also use ignore_error=EAGAIN when using this option.
2490 Note: glibc 2.27, 2.28 have a bug in syscall wrappers preadv2, pwritev2.
2491 They return EOPNOTSUP instead of EAGAIN.
2493 For cached I/O, using this option usually means a request operates only with
2494 cached data. Currently the RWF_NOWAIT flag does not supported for cached write.
2496 For direct I/O, requests will only succeed if cache invalidation isn't required,
2497 file blocks are fully allocated and the disk request could be issued immediately.
2499 .. option:: fdp=bool : [io_uring_cmd] [xnvme]
2501 Enable Flexible Data Placement mode for write commands.
2503 .. option:: dataplacement=str : [io_uring_cmd] [xnvme]
2505 Specifies the data placement directive type to use for write commands.
2506 The following types are supported:
2509 Do not use a data placement directive. This is the
2513 Use Flexible Data Placement directives for write
2514 commands. This is equivalent to specifying
2518 Use Streams directives for write commands.
2520 .. option:: plid_select=str, fdp_pli_select=str : [io_uring_cmd] [xnvme]
2522 Defines how fio decides which placement ID to use next. The following
2526 Choose a placement ID at random (uniform).
2529 Round robin over available placement IDs. This is the
2532 The available placement ID (indices) are defined by the option
2535 .. option:: plids=str, fdp_pli=str : [io_uring_cmd] [xnvme]
2537 Select which Placement IDs (streams) or Placement ID Indices (FDP) this
2538 job is allowed to use for writes. For FDP by default, the job will
2539 cycle through all available Placement IDs, so use this to isolate these
2540 identifiers to specific jobs. If you want fio to use FDP placement
2541 identifiers only at indices 0, 2 and 5 specify ``plids=0,2,5``. For
2542 streams this should be a comma-separated list of Stream IDs.
2544 .. option:: md_per_io_size=int : [io_uring_cmd] [xnvme]
2546 Size in bytes for separate metadata buffer per IO. Default: 0.
2548 .. option:: pi_act=int : [io_uring_cmd] [xnvme]
2550 Action to take when nvme namespace is formatted with protection
2551 information. If this is set to 1 and namespace is formatted with
2552 metadata size equal to protection information size, fio won't use
2553 separate metadata buffer or extended logical block. If this is set to
2554 1 and namespace is formatted with metadata size greater than protection
2555 information size, fio will not generate or verify the protection
2556 information portion of metadata for write or read case respectively.
2557 If this is set to 0, fio generates protection information for
2558 write case and verifies for read case. Default: 1.
2560 For 16 bit CRC generation fio will use isa-l if available otherwise
2561 it will use the default slower generator.
2562 (see: https://github.com/intel/isa-l)
2564 .. option:: pi_chk=str[,str][,str] : [io_uring_cmd] [xnvme]
2566 Controls the protection information check. This can take one or more
2567 of these values. Default: none.
2570 Enables protection information checking of guard field.
2572 Enables protection information checking of logical block
2573 reference tag field.
2575 Enables protection information checking of application tag field.
2577 .. option:: apptag=int : [io_uring_cmd] [xnvme]
2579 Specifies logical block application tag value, if namespace is
2580 formatted to use end to end protection information. Default: 0x1234.
2582 .. option:: apptag_mask=int : [io_uring_cmd] [xnvme]
2584 Specifies logical block application tag mask value, if namespace is
2585 formatted to use end to end protection information. Default: 0xffff.
2587 .. option:: num_range=int : [io_uring_cmd]
2589 For trim command this will be the number of ranges to trim per I/O
2590 request. The number of logical blocks per range is determined by the
2591 :option:`bs` option which should be a multiple of logical block size.
2592 This cannot be used with read or write. Note that setting this
2593 option > 1, :option:`log_offset` will not be able to log all the
2594 offsets. Default: 1.
2596 .. option:: cpuload=int : [cpuio]
2598 Attempt to use the specified percentage of CPU cycles. This is a mandatory
2599 option when using cpuio I/O engine.
2601 .. option:: cpuchunks=int : [cpuio]
2603 Split the load into cycles of the given time. In microseconds.
2605 .. option:: cpumode=str : [cpuio]
2607 Specify how to stress the CPU. It can take these two values:
2610 This is the default where the CPU executes noop instructions.
2612 Replace the default noop instructions loop with a qsort algorithm to
2613 consume more energy.
2615 .. option:: exit_on_io_done=bool : [cpuio]
2617 Detect when I/O threads are done, then exit.
2619 .. option:: namenode=str : [libhdfs]
2621 The hostname or IP address of a HDFS cluster namenode to contact.
2623 .. option:: port=int
2627 The listening port of the HFDS cluster namenode.
2631 The TCP or UDP port to bind to or connect to. If this is used with
2632 :option:`numjobs` to spawn multiple instances of the same job type, then
2633 this will be the starting port number since fio will use a range of
2638 The port to use for RDMA-CM communication. This should be the same value
2639 on the client and the server side.
2641 .. option:: hostname=str : [netsplice] [net] [rdma]
2643 The hostname or IP address to use for TCP, UDP or RDMA-CM based I/O. If the job
2644 is a TCP listener or UDP reader, the hostname is not used and must be omitted
2645 unless it is a valid UDP multicast address.
2647 .. option:: serverip=str : [librpma_*]
2649 The IP address to be used for RDMA-CM based I/O.
2651 .. option:: direct_write_to_pmem=bool : [librpma_*]
2653 Set to 1 only when Direct Write to PMem from the remote host is possible.
2654 Otherwise, set to 0.
2656 .. option:: busy_wait_polling=bool : [librpma_*_server]
2658 Set to 0 to wait for completion instead of busy-wait polling completion.
2661 .. option:: interface=str : [netsplice] [net]
2663 The IP address of the network interface used to send or receive UDP
2666 .. option:: ttl=int : [netsplice] [net]
2668 Time-to-live value for outgoing UDP multicast packets. Default: 1.
2670 .. option:: nodelay=bool : [netsplice] [net]
2672 Set TCP_NODELAY on TCP connections.
2674 .. option:: protocol=str, proto=str : [netsplice] [net]
2676 The network protocol to use. Accepted values are:
2679 Transmission control protocol.
2681 Transmission control protocol V6.
2683 User datagram protocol.
2685 User datagram protocol V6.
2691 When the protocol is TCP, UDP or VSOCK, the port must also be given, as well as the
2692 hostname if the job is a TCP or VSOCK listener or UDP reader. For unix sockets, the
2693 normal :option:`filename` option should be used and the port is invalid.
2694 When the protocol is VSOCK, the :option:`hostname` is the CID of the remote VM.
2696 .. option:: listen : [netsplice] [net]
2698 For TCP network connections, tell fio to listen for incoming connections
2699 rather than initiating an outgoing connection. The :option:`hostname` must
2700 be omitted if this option is used.
2702 .. option:: pingpong : [netsplice] [net]
2704 Normally a network writer will just continue writing data, and a network
2705 reader will just consume packages. If ``pingpong=1`` is set, a writer will
2706 send its normal payload to the reader, then wait for the reader to send the
2707 same payload back. This allows fio to measure network latencies. The
2708 submission and completion latencies then measure local time spent sending or
2709 receiving, and the completion latency measures how long it took for the
2710 other end to receive and send back. For UDP multicast traffic
2711 ``pingpong=1`` should only be set for a single reader when multiple readers
2712 are listening to the same address.
2714 .. option:: window_size : [netsplice] [net]
2716 Set the desired socket buffer size for the connection.
2718 .. option:: mss : [netsplice] [net]
2720 Set the TCP maximum segment size (TCP_MAXSEG).
2722 .. option:: donorname=str : [e4defrag]
2724 File will be used as a block donor (swap extents between files).
2726 .. option:: inplace=int : [e4defrag]
2728 Configure donor file blocks allocation strategy:
2731 Default. Preallocate donor's file on init.
2733 Allocate space immediately inside defragment event, and free right
2736 .. option:: clustername=str : [rbd,rados]
2738 Specifies the name of the Ceph cluster.
2740 .. option:: rbdname=str : [rbd]
2742 Specifies the name of the RBD.
2744 .. option:: clientname=str : [rbd,rados]
2746 Specifies the username (without the 'client.' prefix) used to access the
2747 Ceph cluster. If the *clustername* is specified, the *clientname* shall be
2748 the full *type.id* string. If no type. prefix is given, fio will add
2749 'client.' by default.
2751 .. option:: conf=str : [rados]
2753 Specifies the configuration path of ceph cluster, so conf file does not
2754 have to be /etc/ceph/ceph.conf.
2756 .. option:: busy_poll=bool : [rbd,rados]
2758 Poll store instead of waiting for completion. Usually this provides better
2759 throughput at cost of higher(up to 100%) CPU utilization.
2761 .. option:: touch_objects=bool : [rados]
2763 During initialization, touch (create if do not exist) all objects (files).
2764 Touching all objects affects ceph caches and likely impacts test results.
2767 .. option:: pool=str :
2771 Specifies the name of the Ceph pool containing RBD or RADOS data.
2775 Specify the label or UUID of the DAOS pool to connect to.
2777 .. option:: cont=str : [dfs]
2779 Specify the label or UUID of the DAOS container to open.
2781 .. option:: chunk_size=int
2785 Specify a different chunk size (in bytes) for the dfs file.
2786 Use DAOS container's chunk size by default.
2790 The size of the chunk to use for each file.
2792 .. option:: object_class=str : [dfs]
2794 Specify a different object class for the dfs file.
2795 Use DAOS container's object class by default.
2797 .. option:: skip_bad=bool : [mtd]
2799 Skip operations against known bad blocks.
2801 .. option:: hdfsdirectory : [libhdfs]
2803 libhdfs will create chunk in this HDFS directory.
2805 .. option:: verb=str : [rdma]
2807 The RDMA verb to use on this side of the RDMA ioengine connection. Valid
2808 values are write, read, send and recv. These correspond to the equivalent
2809 RDMA verbs (e.g. write = rdma_write etc.). Note that this only needs to be
2810 specified on the client side of the connection. See the examples folder.
2812 .. option:: bindname=str : [rdma]
2814 The name to use to bind the local RDMA-CM connection to a local RDMA device.
2815 This could be a hostname or an IPv4 or IPv6 address. On the server side this
2816 will be passed into the rdma_bind_addr() function and on the client site it
2817 will be used in the rdma_resolve_add() function. This can be useful when
2818 multiple paths exist between the client and the server or in certain loopback
2821 .. option:: stat_type=str : [filestat]
2823 Specify stat system call type to measure lookup/getattr performance.
2824 Default is **stat** for :manpage:`stat(2)`.
2826 .. option:: readfua=bool : [sg]
2828 With readfua option set to 1, read operations include
2829 the force unit access (fua) flag. Default is 0.
2831 .. option:: writefua=bool : [sg]
2833 With writefua option set to 1, write operations include
2834 the force unit access (fua) flag. Default is 0.
2836 .. option:: sg_write_mode=str : [sg]
2838 Specify the type of write commands to issue. This option can take ten values:
2841 This is the default where write opcodes are issued as usual.
2842 **write_and_verify**
2843 Issue WRITE AND VERIFY commands. The BYTCHK bit is set to 0. This
2844 directs the device to carry out a medium verification with no data
2845 comparison. The writefua option is ignored with this selection.
2847 This option is deprecated. Use write_and_verify instead.
2849 Issue WRITE SAME commands. This transfers a single block to the device
2850 and writes this same block of data to a contiguous sequence of LBAs
2851 beginning at the specified offset. fio's block size parameter specifies
2852 the amount of data written with each command. However, the amount of data
2853 actually transferred to the device is equal to the device's block
2854 (sector) size. For a device with 512 byte sectors, blocksize=8k will
2855 write 16 sectors with each command. fio will still generate 8k of data
2856 for each command but only the first 512 bytes will be used and
2857 transferred to the device. The writefua option is ignored with this
2860 This option is deprecated. Use write_same instead.
2862 Issue WRITE SAME(16) commands as above but with the No Data Output
2863 Buffer (NDOB) bit set. No data will be transferred to the device with
2864 this bit set. Data written will be a pre-determined pattern such as
2867 Issue WRITE STREAM(16) commands. Use the **stream_id** option to specify
2868 the stream identifier.
2869 **verify_bytchk_00**
2870 Issue VERIFY commands with BYTCHK set to 00. This directs the
2871 device to carry out a medium verification with no data comparison.
2872 **verify_bytchk_01**
2873 Issue VERIFY commands with BYTCHK set to 01. This directs the device to
2874 compare the data on the device with the data transferred to the device.
2875 **verify_bytchk_11**
2876 Issue VERIFY commands with BYTCHK set to 11. This transfers a
2877 single block to the device and compares the contents of this block with the
2878 data on the device beginning at the specified offset. fio's block size
2879 parameter specifies the total amount of data compared with this command.
2880 However, only one block (sector) worth of data is transferred to the device.
2881 This is similar to the WRITE SAME command except that data is compared instead
2884 .. option:: stream_id=int : [sg]
2886 Set the stream identifier for WRITE STREAM commands. If this is set to 0 (which is not
2887 a valid stream identifier) fio will open a stream and then close it when done. Default
2890 .. option:: http_host=str : [http]
2892 Hostname to connect to. For S3, this could be the bucket hostname.
2893 Default is **localhost**
2895 .. option:: http_user=str : [http]
2897 Username for HTTP authentication.
2899 .. option:: http_pass=str : [http]
2901 Password for HTTP authentication.
2903 .. option:: https=str : [http]
2905 Enable HTTPS instead of http. *on* enables HTTPS; *insecure*
2906 will enable HTTPS, but disable SSL peer verification (use with
2907 caution!). Default is **off**
2909 .. option:: http_mode=str : [http]
2911 Which HTTP access mode to use: *webdav*, *swift*, or *s3*.
2912 Default is **webdav**
2914 .. option:: http_s3_region=str : [http]
2916 The S3 region/zone string.
2917 Default is **us-east-1**
2919 .. option:: http_s3_key=str : [http]
2923 .. option:: http_s3_keyid=str : [http]
2925 The S3 key/access id.
2927 .. option:: http_s3_sse_customer_key=str : [http]
2929 The encryption customer key in SSE server side.
2931 .. option:: http_s3_sse_customer_algorithm=str : [http]
2933 The encryption customer algorithm in SSE server side.
2934 Default is **AES256**
2936 .. option:: http_s3_storage_class=str : [http]
2938 Which storage class to access. User-customizable settings.
2939 Default is **STANDARD**
2941 .. option:: http_swift_auth_token=str : [http]
2943 The Swift auth token. See the example configuration file on how
2946 .. option:: http_verbose=int : [http]
2948 Enable verbose requests from libcurl. Useful for debugging. 1
2949 turns on verbose logging from libcurl, 2 additionally enables
2950 HTTP IO tracing. Default is **0**
2952 .. option:: uri=str : [nbd]
2954 Specify the NBD URI of the server to test. The string
2955 is a standard NBD URI
2956 (see https://github.com/NetworkBlockDevice/nbd/tree/master/doc).
2957 Example URIs: nbd://localhost:10809
2958 nbd+unix:///?socket=/tmp/socket
2959 nbds://tlshost/exportname
2961 .. option:: gpu_dev_ids=str : [libcufile]
2963 Specify the GPU IDs to use with CUDA. This is a colon-separated list of
2964 int. GPUs are assigned to workers roundrobin. Default is 0.
2966 .. option:: cuda_io=str : [libcufile]
2968 Specify the type of I/O to use with CUDA. Default is **cufile**.
2971 Use libcufile and nvidia-fs. This option performs I/O directly
2972 between a GPUDirect Storage filesystem and GPU buffers,
2973 avoiding use of a bounce buffer. If :option:`verify` is set,
2974 cudaMemcpy is used to copy verificaton data between RAM and GPU.
2975 Verification data is copied from RAM to GPU before a write
2976 and from GPU to RAM after a read. :option:`direct` must be 1.
2978 Use POSIX to perform I/O with a RAM buffer, and use cudaMemcpy
2979 to transfer data between RAM and the GPUs. Data is copied from
2980 GPU to RAM before a write and copied from RAM to GPU after a
2981 read. :option:`verify` does not affect use of cudaMemcpy.
2983 .. option:: nfs_url=str : [nfs]
2985 URL in libnfs format, eg nfs://<server|ipv4|ipv6>/path[?arg=val[&arg=val]*]
2986 Refer to the libnfs README for more details.
2988 .. option:: program=str : [exec]
2990 Specify the program to execute.
2992 .. option:: arguments=str : [exec]
2994 Specify arguments to pass to program.
2995 Some special variables can be expanded to pass fio's job details to the program.
2998 Replaced by the duration of the job in seconds.
3000 Replaced by the name of the job.
3002 .. option:: grace_time=int : [exec]
3004 Specify the time between the SIGTERM and SIGKILL signals. Default is 1 second.
3006 .. option:: std_redirect=bool : [exec]
3008 If set, stdout and stderr streams are redirected to files named from the job name. Default is true.
3010 .. option:: xnvme_async=str : [xnvme]
3012 Select the xnvme async command interface. This can take these values.
3015 This is default and use to emulate asynchronous I/O by using a
3016 single thread to create a queue pair on top of a synchronous
3017 I/O interface using the NVMe driver IOCTL.
3019 Emulate an asynchronous I/O interface with a pool of userspace
3020 threads on top of a synchronous I/O interface using the NVMe
3021 driver IOCTL. By default four threads are used.
3023 Linux native asynchronous I/O interface which supports both
3024 direct and buffered I/O.
3026 Fast Linux native asynchronous I/O interface for NVMe pass
3027 through commands. This only works with NVMe character device
3030 Use Linux aio for Asynchronous I/O.
3032 Use the posix asynchronous I/O interface to perform one or
3033 more I/O operations asynchronously.
3035 Use the user-space VFIO-based backend, implemented using
3036 libvfn instead of SPDK.
3038 Do not transfer any data; just pretend to. This is mainly used
3039 for introspective performance evaluation.
3041 .. option:: xnvme_sync=str : [xnvme]
3043 Select the xnvme synchronous command interface. This can take these values.
3046 This is default and uses Linux NVMe Driver ioctl() for
3049 This supports regular as well as vectored pread() and pwrite()
3052 This is the same as psync except that it also supports zone
3053 management commands using Linux block layer IOCTLs.
3055 .. option:: xnvme_admin=str : [xnvme]
3057 Select the xnvme admin command interface. This can take these values.
3060 This is default and uses linux NVMe Driver ioctl() for admin
3063 Use Linux Block Layer ioctl() and sysfs for admin commands.
3065 .. option:: xnvme_dev_nsid=int : [xnvme]
3067 xnvme namespace identifier for userspace NVMe driver, SPDK or vfio.
3069 .. option:: xnvme_dev_subnqn=str : [xnvme]
3071 Sets the subsystem NQN for fabrics. This is for xNVMe to utilize a
3072 fabrics target with multiple systems.
3074 .. option:: xnvme_mem=str : [xnvme]
3076 Select the xnvme memory backend. This can take these values.
3079 This is the default posix memory backend for linux NVMe driver.
3081 Use hugepages, instead of existing posix memory backend. The
3082 memory backend uses hugetlbfs. This require users to allocate
3083 hugepages, mount hugetlbfs and set an environment variable for
3086 Uses SPDK's memory allocator.
3088 Uses libvfn's memory allocator. This also specifies the use
3089 of libvfn backend instead of SPDK.
3091 .. option:: xnvme_iovec=int : [xnvme]
3093 If this option is set. xnvme will use vectored read/write commands.
3095 .. option:: libblkio_driver=str : [libblkio]
3097 The libblkio *driver* to use. Different drivers access devices through
3098 different underlying interfaces. Available drivers depend on the
3099 libblkio version in use and are listed at
3100 https://libblkio.gitlab.io/libblkio/blkio.html#drivers
3102 .. option:: libblkio_path=str : [libblkio]
3104 Sets the value of the driver-specific "path" property before connecting
3105 the libblkio instance, which identifies the target device or file on
3106 which to perform I/O. Its exact semantics are driver-dependent and not
3107 all drivers may support it; see
3108 https://libblkio.gitlab.io/libblkio/blkio.html#drivers
3110 .. option:: libblkio_pre_connect_props=str : [libblkio]
3112 A colon-separated list of additional libblkio properties to be set after
3113 creating but before connecting the libblkio instance. Each property must
3114 have the format ``<name>=<value>``. Colons can be escaped as ``\:``.
3115 These are set after the engine sets any other properties, so those can
3116 be overridden. Available properties depend on the libblkio version in use
3118 https://libblkio.gitlab.io/libblkio/blkio.html#properties
3120 .. option:: libblkio_num_entries=int : [libblkio]
3122 Sets the value of the driver-specific "num-entries" property before
3123 starting the libblkio instance. Its exact semantics are driver-dependent
3124 and not all drivers may support it; see
3125 https://libblkio.gitlab.io/libblkio/blkio.html#drivers
3127 .. option:: libblkio_queue_size=int : [libblkio]
3129 Sets the value of the driver-specific "queue-size" property before
3130 starting the libblkio instance. Its exact semantics are driver-dependent
3131 and not all drivers may support it; see
3132 https://libblkio.gitlab.io/libblkio/blkio.html#drivers
3134 .. option:: libblkio_pre_start_props=str : [libblkio]
3136 A colon-separated list of additional libblkio properties to be set after
3137 connecting but before starting the libblkio instance. Each property must
3138 have the format ``<name>=<value>``. Colons can be escaped as ``\:``.
3139 These are set after the engine sets any other properties, so those can
3140 be overridden. Available properties depend on the libblkio version in use
3142 https://libblkio.gitlab.io/libblkio/blkio.html#properties
3144 .. option:: libblkio_vectored : [libblkio]
3146 Submit vectored read and write requests.
3148 .. option:: libblkio_write_zeroes_on_trim : [libblkio]
3150 Submit trims as "write zeroes" requests instead of discard requests.
3152 .. option:: libblkio_wait_mode=str : [libblkio]
3154 How to wait for completions:
3157 Use a blocking call to ``blkioq_do_io()``.
3159 Use a blocking call to ``read()`` on the completion eventfd.
3161 Use a busy loop with a non-blocking call to ``blkioq_do_io()``.
3163 .. option:: libblkio_force_enable_completion_eventfd : [libblkio]
3165 Enable the queue's completion eventfd even when unused. This may impact
3166 performance. The default is to enable it only if
3167 :option:`libblkio_wait_mode=eventfd <libblkio_wait_mode>`.
3169 .. option:: no_completion_thread : [windowsaio]
3171 Avoid using a separate thread for completion polling.
3176 .. option:: iodepth=int
3178 Number of I/O units to keep in flight against the file. Note that
3179 increasing *iodepth* beyond 1 will not affect synchronous ioengines (except
3180 for small degrees when :option:`verify_async` is in use). Even async
3181 engines may impose OS restrictions causing the desired depth not to be
3182 achieved. This may happen on Linux when using libaio and not setting
3183 :option:`direct`\=1, since buffered I/O is not async on that OS. Keep an
3184 eye on the I/O depth distribution in the fio output to verify that the
3185 achieved depth is as expected. Default: 1.
3187 .. option:: iodepth_batch_submit=int, iodepth_batch=int
3189 This defines how many pieces of I/O to submit at once. It defaults to 1
3190 which means that we submit each I/O as soon as it is available, but can be
3191 raised to submit bigger batches of I/O at the time. If it is set to 0 the
3192 :option:`iodepth` value will be used.
3194 .. option:: iodepth_batch_complete_min=int, iodepth_batch_complete=int
3196 This defines how many pieces of I/O to retrieve at once. It defaults to 1
3197 which means that we'll ask for a minimum of 1 I/O in the retrieval process
3198 from the kernel. The I/O retrieval will go on until we hit the limit set by
3199 :option:`iodepth_low`. If this variable is set to 0, then fio will always
3200 check for completed events before queuing more I/O. This helps reduce I/O
3201 latency, at the cost of more retrieval system calls.
3203 .. option:: iodepth_batch_complete_max=int
3205 This defines maximum pieces of I/O to retrieve at once. This variable should
3206 be used along with :option:`iodepth_batch_complete_min`\=int variable,
3207 specifying the range of min and max amount of I/O which should be
3208 retrieved. By default it is equal to the :option:`iodepth_batch_complete_min`
3213 iodepth_batch_complete_min=1
3214 iodepth_batch_complete_max=<iodepth>
3216 which means that we will retrieve at least 1 I/O and up to the whole
3217 submitted queue depth. If none of I/O has been completed yet, we will wait.
3221 iodepth_batch_complete_min=0
3222 iodepth_batch_complete_max=<iodepth>
3224 which means that we can retrieve up to the whole submitted queue depth, but
3225 if none of I/O has been completed yet, we will NOT wait and immediately exit
3226 the system call. In this example we simply do polling.
3228 .. option:: iodepth_low=int
3230 The low water mark indicating when to start filling the queue
3231 again. Defaults to the same as :option:`iodepth`, meaning that fio will
3232 attempt to keep the queue full at all times. If :option:`iodepth` is set to
3233 e.g. 16 and *iodepth_low* is set to 4, then after fio has filled the queue of
3234 16 requests, it will let the depth drain down to 4 before starting to fill
3237 .. option:: serialize_overlap=bool
3239 Serialize in-flight I/Os that might otherwise cause or suffer from data races.
3240 When two or more I/Os are submitted simultaneously, there is no guarantee that
3241 the I/Os will be processed or completed in the submitted order. Further, if
3242 two or more of those I/Os are writes, any overlapping region between them can
3243 become indeterminate/undefined on certain storage. These issues can cause
3244 verification to fail erratically when at least one of the racing I/Os is
3245 changing data and the overlapping region has a non-zero size. Setting
3246 ``serialize_overlap`` tells fio to avoid provoking this behavior by explicitly
3247 serializing in-flight I/Os that have a non-zero overlap. Note that setting
3248 this option can reduce both performance and the :option:`iodepth` achieved.
3250 This option only applies to I/Os issued for a single job except when it is
3251 enabled along with :option:`io_submit_mode`\=offload. In offload mode, fio
3252 will check for overlap among all I/Os submitted by offload jobs with :option:`serialize_overlap`
3257 .. option:: io_submit_mode=str
3259 This option controls how fio submits the I/O to the I/O engine. The default
3260 is `inline`, which means that the fio job threads submit and reap I/O
3261 directly. If set to `offload`, the job threads will offload I/O submission
3262 to a dedicated pool of I/O threads. This requires some coordination and thus
3263 has a bit of extra overhead, especially for lower queue depth I/O where it
3264 can increase latencies. The benefit is that fio can manage submission rates
3265 independently of the device completion rates. This avoids skewed latency
3266 reporting if I/O gets backed up on the device side (the coordinated omission
3267 problem). Note that this option cannot reliably be used with async IO
3274 .. option:: thinkcycles=int
3276 Stall the job for the specified number of cycles after an I/O has completed before
3277 issuing the next. May be used to simulate processing being done by an application.
3278 This is not taken into account for the time to be waited on for :option:`thinktime`.
3279 Might not have any effect on some platforms, this can be checked by trying a setting
3280 a high enough amount of thinkcycles.
3282 .. option:: thinktime=time
3284 Stall the job for the specified period of time after an I/O has completed before issuing the
3285 next. May be used to simulate processing being done by an application.
3286 When the unit is omitted, the value is interpreted in microseconds. See
3287 :option:`thinktime_blocks`, :option:`thinktime_iotime` and :option:`thinktime_spin`.
3289 .. option:: thinktime_spin=time
3291 Only valid if :option:`thinktime` is set - pretend to spend CPU time doing
3292 something with the data received, before falling back to sleeping for the
3293 rest of the period specified by :option:`thinktime`. When the unit is
3294 omitted, the value is interpreted in microseconds.
3296 .. option:: thinktime_blocks=int
3298 Only valid if :option:`thinktime` is set - control how many blocks to issue,
3299 before waiting :option:`thinktime` usecs. If not set, defaults to 1 which will make
3300 fio wait :option:`thinktime` usecs after every block. This effectively makes any
3301 queue depth setting redundant, since no more than 1 I/O will be queued
3302 before we have to complete it and do our :option:`thinktime`. In other words, this
3303 setting effectively caps the queue depth if the latter is larger.
3305 .. option:: thinktime_blocks_type=str
3307 Only valid if :option:`thinktime` is set - control how :option:`thinktime_blocks`
3308 triggers. The default is `complete`, which triggers thinktime when fio completes
3309 :option:`thinktime_blocks` blocks. If this is set to `issue`, then the trigger happens
3312 .. option:: thinktime_iotime=time
3314 Only valid if :option:`thinktime` is set - control :option:`thinktime`
3315 interval by time. The :option:`thinktime` stall is repeated after IOs
3316 are executed for :option:`thinktime_iotime`. For example,
3317 ``--thinktime_iotime=9s --thinktime=1s`` repeat 10-second cycle with IOs
3318 for 9 seconds and stall for 1 second. When the unit is omitted,
3319 :option:`thinktime_iotime` is interpreted as a number of seconds. If
3320 this option is used together with :option:`thinktime_blocks`, the
3321 :option:`thinktime` stall is repeated after :option:`thinktime_iotime`
3322 or after :option:`thinktime_blocks` IOs, whichever happens first.
3324 .. option:: rate=int[,int][,int]
3326 Cap the bandwidth used by this job. The number is in bytes/sec, the normal
3327 suffix rules apply. Comma-separated values may be specified for reads,
3328 writes, and trims as described in :option:`blocksize`.
3330 For example, using `rate=1m,500k` would limit reads to 1MiB/sec and writes to
3331 500KiB/sec. Capping only reads or writes can be done with `rate=,500k` or
3332 `rate=500k,` where the former will only limit writes (to 500KiB/sec) and the
3333 latter will only limit reads.
3335 .. option:: rate_min=int[,int][,int]
3337 Tell fio to do whatever it can to maintain at least this bandwidth. Failing
3338 to meet this requirement will cause the job to exit. Comma-separated values
3339 may be specified for reads, writes, and trims as described in
3340 :option:`blocksize`.
3342 .. option:: rate_iops=int[,int][,int]
3344 Cap the bandwidth to this number of IOPS. Basically the same as
3345 :option:`rate`, just specified independently of bandwidth. If the job is
3346 given a block size range instead of a fixed value, the smallest block size
3347 is used as the metric. Comma-separated values may be specified for reads,
3348 writes, and trims as described in :option:`blocksize`.
3350 .. option:: rate_iops_min=int[,int][,int]
3352 If fio doesn't meet this rate of I/O, it will cause the job to exit.
3353 Comma-separated values may be specified for reads, writes, and trims as
3354 described in :option:`blocksize`.
3356 .. option:: rate_process=str
3358 This option controls how fio manages rated I/O submissions. The default is
3359 `linear`, which submits I/O in a linear fashion with fixed delays between
3360 I/Os that gets adjusted based on I/O completion rates. If this is set to
3361 `poisson`, fio will submit I/O based on a more real world random request
3362 flow, known as the Poisson process
3363 (https://en.wikipedia.org/wiki/Poisson_point_process). The lambda will be
3364 10^6 / IOPS for the given workload.
3366 .. option:: rate_ignore_thinktime=bool
3368 By default, fio will attempt to catch up to the specified rate setting,
3369 if any kind of thinktime setting was used. If this option is set, then
3370 fio will ignore the thinktime and continue doing IO at the specified
3371 rate, instead of entering a catch-up mode after thinktime is done.
3373 .. option:: rate_cycle=int
3375 Average bandwidth for :option:`rate_min` and :option:`rate_iops_min`
3376 over this number of milliseconds. Defaults to 1000.
3382 .. option:: latency_target=time
3384 If set, fio will attempt to find the max performance point that the given
3385 workload will run at while maintaining a latency below this target. When
3386 the unit is omitted, the value is interpreted in microseconds. See
3387 :option:`latency_window` and :option:`latency_percentile`.
3389 .. option:: latency_window=time
3391 Used with :option:`latency_target` to specify the sample window that the job
3392 is run at varying queue depths to test the performance. When the unit is
3393 omitted, the value is interpreted in microseconds.
3395 .. option:: latency_percentile=float
3397 The percentage of I/Os that must fall within the criteria specified by
3398 :option:`latency_target` and :option:`latency_window`. If not set, this
3399 defaults to 100.0, meaning that all I/Os must be equal or below to the value
3400 set by :option:`latency_target`.
3402 .. option:: latency_run=bool
3404 Used with :option:`latency_target`. If false (default), fio will find
3405 the highest queue depth that meets :option:`latency_target` and exit. If
3406 true, fio will continue running and try to meet :option:`latency_target`
3407 by adjusting queue depth.
3409 .. option:: max_latency=time[,time][,time]
3411 If set, fio will exit the job with an ETIMEDOUT error if it exceeds this
3412 maximum latency. When the unit is omitted, the value is interpreted in
3413 microseconds. Comma-separated values may be specified for reads, writes,
3414 and trims as described in :option:`blocksize`.
3420 .. option:: write_iolog=str
3422 Write the issued I/O patterns to the specified file. See
3423 :option:`read_iolog`. Specify a separate file for each job, otherwise the
3424 iologs will be interspersed and the file may be corrupt. This file will
3425 be opened in append mode.
3427 .. option:: read_iolog=str
3429 Open an iolog with the specified filename and replay the I/O patterns it
3430 contains. This can be used to store a workload and replay it sometime
3431 later. The iolog given may also be a blktrace binary file, which allows fio
3432 to replay a workload captured by :command:`blktrace`. See
3433 :manpage:`blktrace(8)` for how to capture such logging data. For blktrace
3434 replay, the file needs to be turned into a blkparse binary data file first
3435 (``blkparse <device> -o /dev/null -d file_for_fio.bin``).
3436 You can specify a number of files by separating the names with a ':'
3437 character. See the :option:`filename` option for information on how to
3438 escape ':' characters within the file names. These files will
3439 be sequentially assigned to job clones created by :option:`numjobs`.
3440 '-' is a reserved name, meaning read from stdin, notably if
3441 :option:`filename` is set to '-' which means stdin as well, then
3442 this flag can't be set to '-'.
3444 .. option:: read_iolog_chunked=bool
3446 Determines how iolog is read. If false(default) entire :option:`read_iolog`
3447 will be read at once. If selected true, input from iolog will be read
3448 gradually. Useful when iolog is very large, or it is generated.
3450 .. option:: merge_blktrace_file=str
3452 When specified, rather than replaying the logs passed to :option:`read_iolog`,
3453 the logs go through a merge phase which aggregates them into a single
3454 blktrace. The resulting file is then passed on as the :option:`read_iolog`
3455 parameter. The intention here is to make the order of events consistent.
3456 This limits the influence of the scheduler compared to replaying multiple
3457 blktraces via concurrent jobs.
3459 .. option:: merge_blktrace_scalars=float_list
3461 This is a percentage based option that is index paired with the list of
3462 files passed to :option:`read_iolog`. When merging is performed, scale
3463 the time of each event by the corresponding amount. For example,
3464 ``--merge_blktrace_scalars="50:100"`` runs the first trace in halftime
3465 and the second trace in realtime. This knob is separately tunable from
3466 :option:`replay_time_scale` which scales the trace during runtime and
3467 does not change the output of the merge unlike this option.
3469 .. option:: merge_blktrace_iters=float_list
3471 This is a whole number option that is index paired with the list of files
3472 passed to :option:`read_iolog`. When merging is performed, run each trace
3473 for the specified number of iterations. For example,
3474 ``--merge_blktrace_iters="2:1"`` runs the first trace for two iterations
3475 and the second trace for one iteration.
3477 .. option:: replay_no_stall=bool
3479 When replaying I/O with :option:`read_iolog` the default behavior is to
3480 attempt to respect the timestamps within the log and replay them with the
3481 appropriate delay between IOPS. By setting this variable fio will not
3482 respect the timestamps and attempt to replay them as fast as possible while
3483 still respecting ordering. The result is the same I/O pattern to a given
3484 device, but different timings.
3486 .. option:: replay_time_scale=int
3488 When replaying I/O with :option:`read_iolog`, fio will honor the
3489 original timing in the trace. With this option, it's possible to scale
3490 the time. It's a percentage option, if set to 50 it means run at 50%
3491 the original IO rate in the trace. If set to 200, run at twice the
3492 original IO rate. Defaults to 100.
3494 .. option:: replay_redirect=str
3496 While replaying I/O patterns using :option:`read_iolog` the default behavior
3497 is to replay the IOPS onto the major/minor device that each IOP was recorded
3498 from. This is sometimes undesirable because on a different machine those
3499 major/minor numbers can map to a different device. Changing hardware on the
3500 same system can also result in a different major/minor mapping.
3501 ``replay_redirect`` causes all I/Os to be replayed onto the single specified
3502 device regardless of the device it was recorded
3503 from. i.e. :option:`replay_redirect`\= :file:`/dev/sdc` would cause all I/O
3504 in the blktrace or iolog to be replayed onto :file:`/dev/sdc`. This means
3505 multiple devices will be replayed onto a single device, if the trace
3506 contains multiple devices. If you want multiple devices to be replayed
3507 concurrently to multiple redirected devices you must blkparse your trace
3508 into separate traces and replay them with independent fio invocations.
3509 Unfortunately this also breaks the strict time ordering between multiple
3512 .. option:: replay_align=int
3514 Force alignment of the byte offsets in a trace to this value. The value
3515 must be a power of 2.
3517 .. option:: replay_scale=int
3519 Scale byte offsets down by this factor when replaying traces. Should most
3520 likely use :option:`replay_align` as well.
3522 .. option:: replay_skip=str
3524 Sometimes it's useful to skip certain IO types in a replay trace.
3525 This could be, for instance, eliminating the writes in the trace.
3526 Or not replaying the trims/discards, if you are redirecting to
3527 a device that doesn't support them. This option takes a comma
3528 separated list of read, write, trim, sync.
3531 Threads, processes and job synchronization
3532 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3536 Fio defaults to creating jobs by using fork, however if this option is
3537 given, fio will create jobs by using POSIX Threads' function
3538 :manpage:`pthread_create(3)` to create threads instead.
3540 .. option:: wait_for=str
3542 If set, the current job won't be started until all workers of the specified
3543 waitee job are done.
3545 ``wait_for`` operates on the job name basis, so there are a few
3546 limitations. First, the waitee must be defined prior to the waiter job
3547 (meaning no forward references). Second, if a job is being referenced as a
3548 waitee, it must have a unique name (no duplicate waitees).
3550 .. option:: nice=int
3552 Run the job with the given nice value. See man :manpage:`nice(2)`.
3554 On Windows, values less than -15 set the process class to "High"; -1 through
3555 -15 set "Above Normal"; 1 through 15 "Below Normal"; and above 15 "Idle"
3558 .. option:: prio=int
3560 Set the I/O priority value of this job. Linux limits us to a positive value
3561 between 0 and 7, with 0 being the highest. See man
3562 :manpage:`ionice(1)`. Refer to an appropriate manpage for other operating
3563 systems since meaning of priority may differ. For per-command priority
3564 setting, see I/O engine specific :option:`cmdprio_percentage` and
3565 :option:`cmdprio` options.
3567 .. option:: prioclass=int
3569 Set the I/O priority class. See man :manpage:`ionice(1)`. For per-command
3570 priority setting, see I/O engine specific :option:`cmdprio_percentage`
3571 and :option:`cmdprio_class` options.
3573 .. option:: priohint=int
3575 Set the I/O priority hint. This is only applicable to platforms that
3576 support I/O priority classes and to devices with features controlled
3577 through priority hints, e.g. block devices supporting command duration
3578 limits, or CDL. CDL is a way to indicate the desired maximum latency
3579 of I/Os so that the device can optimize its internal command scheduling
3580 according to the latency limits indicated by the user.
3582 For per-I/O priority hint setting, see the I/O engine specific
3583 :option:`cmdprio_hint` option.
3585 .. option:: cpus_allowed=str
3587 Controls the same options as :option:`cpumask`, but accepts a textual
3588 specification of the permitted CPUs instead and CPUs are indexed from 0. So
3589 to use CPUs 0 and 5 you would specify ``cpus_allowed=0,5``. This option also
3590 allows a range of CPUs to be specified -- say you wanted a binding to CPUs
3591 0, 5, and 8 to 15, you would set ``cpus_allowed=0,5,8-15``.
3593 On Windows, when ``cpus_allowed`` is unset only CPUs from fio's current
3594 processor group will be used and affinity settings are inherited from the
3595 system. An fio build configured to target Windows 7 makes options that set
3596 CPUs processor group aware and values will set both the processor group
3597 and a CPU from within that group. For example, on a system where processor
3598 group 0 has 40 CPUs and processor group 1 has 32 CPUs, ``cpus_allowed``
3599 values between 0 and 39 will bind CPUs from processor group 0 and
3600 ``cpus_allowed`` values between 40 and 71 will bind CPUs from processor
3601 group 1. When using ``cpus_allowed_policy=shared`` all CPUs specified by a
3602 single ``cpus_allowed`` option must be from the same processor group. For
3603 Windows fio builds not built for Windows 7, CPUs will only be selected from
3604 (and be relative to) whatever processor group fio happens to be running in
3605 and CPUs from other processor groups cannot be used.
3607 .. option:: cpus_allowed_policy=str
3609 Set the policy of how fio distributes the CPUs specified by
3610 :option:`cpus_allowed` or :option:`cpumask`. Two policies are supported:
3613 All jobs will share the CPU set specified.
3615 Each job will get a unique CPU from the CPU set.
3617 **shared** is the default behavior, if the option isn't specified. If
3618 **split** is specified, then fio will assign one cpu per job. If not
3619 enough CPUs are given for the jobs listed, then fio will roundrobin the CPUs
3622 .. option:: cpumask=int
3624 Set the CPU affinity of this job. The parameter given is a bit mask of
3625 allowed CPUs the job may run on. So if you want the allowed CPUs to be 1
3626 and 5, you would pass the decimal value of (1 << 1 | 1 << 5), or 34. See man
3627 :manpage:`sched_setaffinity(2)`. This may not work on all supported
3628 operating systems or kernel versions. This option doesn't work well for a
3629 higher CPU count than what you can store in an integer mask, so it can only
3630 control cpus 1-32. For boxes with larger CPU counts, use
3631 :option:`cpus_allowed`.
3633 .. option:: numa_cpu_nodes=str
3635 Set this job running on specified NUMA nodes' CPUs. The arguments allow
3636 comma delimited list of cpu numbers, A-B ranges, or `all`. Note, to enable
3637 NUMA options support, fio must be built on a system with libnuma-dev(el)
3640 .. option:: numa_mem_policy=str
3642 Set this job's memory policy and corresponding NUMA nodes. Format of the
3647 ``mode`` is one of the following memory policies: ``default``, ``prefer``,
3648 ``bind``, ``interleave`` or ``local``. For ``default`` and ``local`` memory
3649 policies, no node needs to be specified. For ``prefer``, only one node is
3650 allowed. For ``bind`` and ``interleave`` the ``nodelist`` may be as
3651 follows: a comma delimited list of numbers, A-B ranges, or `all`.
3653 .. option:: cgroup=str
3655 Add job to this control group. If it doesn't exist, it will be created. The
3656 system must have a mounted cgroup blkio mount point for this to work. If
3657 your system doesn't have it mounted, you can do so with::
3659 # mount -t cgroup -o blkio none /cgroup
3661 .. option:: cgroup_weight=int
3663 Set the weight of the cgroup to this value. See the documentation that comes
3664 with the kernel, allowed values are in the range of 100..1000.
3666 .. option:: cgroup_nodelete=bool
3668 Normally fio will delete the cgroups it has created after the job
3669 completion. To override this behavior and to leave cgroups around after the
3670 job completion, set ``cgroup_nodelete=1``. This can be useful if one wants
3671 to inspect various cgroup files after job completion. Default: false.
3673 .. option:: flow_id=int
3675 The ID of the flow. If not specified, it defaults to being a global
3676 flow. See :option:`flow`.
3678 .. option:: flow=int
3680 Weight in token-based flow control. If this value is used, then fio
3681 regulates the activity between two or more jobs sharing the same
3682 flow_id. Fio attempts to keep each job activity proportional to other
3683 jobs' activities in the same flow_id group, with respect to requested
3684 weight per job. That is, if one job has `flow=3', another job has
3685 `flow=2' and another with `flow=1`, then there will be a roughly 3:2:1
3686 ratio in how much one runs vs the others.
3688 .. option:: flow_sleep=int
3690 The period of time, in microseconds, to wait after the flow counter
3691 has exceeded its proportion before retrying operations.
3693 .. option:: stonewall, wait_for_previous
3695 Wait for preceding jobs in the job file to exit, before starting this
3696 one. Can be used to insert serialization points in the job file. A stone
3697 wall also implies starting a new reporting group, see
3698 :option:`group_reporting`.
3702 By default, fio will continue running all other jobs when one job finishes.
3703 Sometimes this is not the desired action. Setting ``exitall`` will instead
3704 make fio terminate all jobs in the same group, as soon as one job of that
3707 .. option:: exit_what=str
3709 By default, fio will continue running all other jobs when one job finishes.
3710 Sometimes this is not the desired action. Setting ``exitall`` will
3711 instead make fio terminate all jobs in the same group. The option
3712 ``exit_what`` allows one to control which jobs get terminated when ``exitall``
3713 is enabled. The default is ``group`` and does not change the behaviour of
3714 ``exitall``. The setting ``all`` terminates all jobs. The setting ``stonewall``
3715 terminates all currently running jobs across all groups and continues execution
3716 with the next stonewalled group.
3718 .. option:: exec_prerun=str
3720 Before running this job, issue the command specified through
3721 :manpage:`system(3)`. Output is redirected in a file called
3722 :file:`jobname.prerun.txt`.
3724 .. option:: exec_postrun=str
3726 After the job completes, issue the command specified though
3727 :manpage:`system(3)`. Output is redirected in a file called
3728 :file:`jobname.postrun.txt`.
3732 Instead of running as the invoking user, set the user ID to this value
3733 before the thread/process does any work.
3737 Set group ID, see :option:`uid`.
3743 .. option:: verify_only
3745 Do not perform specified workload, only verify data still matches previous
3746 invocation of this workload. This option allows one to check data multiple
3747 times at a later date without overwriting it. This option makes sense only
3748 for workloads that write data, and does not support workloads with the
3749 :option:`time_based` option set.
3751 .. option:: do_verify=bool
3753 Run the verify phase after a write phase. Only valid if :option:`verify` is
3756 .. option:: verify=str
3758 If writing to a file, fio can verify the file contents after each iteration
3759 of the job. Each verification method also implies verification of special
3760 header, which is written to the beginning of each block. This header also
3761 includes meta information, like offset of the block, block number, timestamp
3762 when block was written, etc. :option:`verify` can be combined with
3763 :option:`verify_pattern` option. The allowed values are:
3766 Use an md5 sum of the data area and store it in the header of
3770 Use an experimental crc64 sum of the data area and store it in the
3771 header of each block.
3774 Use a crc32c sum of the data area and store it in the header of
3775 each block. This will automatically use hardware acceleration
3776 (e.g. SSE4.2 on an x86 or CRC crypto extensions on ARM64) but will
3777 fall back to software crc32c if none is found. Generally the
3778 fastest checksum fio supports when hardware accelerated.
3784 Use a crc32 sum of the data area and store it in the header of each
3788 Use a crc16 sum of the data area and store it in the header of each
3792 Use a crc7 sum of the data area and store it in the header of each
3796 Use xxhash as the checksum function. Generally the fastest software
3797 checksum that fio supports.
3800 Use sha512 as the checksum function.
3803 Use sha256 as the checksum function.
3806 Use optimized sha1 as the checksum function.
3809 Use optimized sha3-224 as the checksum function.
3812 Use optimized sha3-256 as the checksum function.
3815 Use optimized sha3-384 as the checksum function.
3818 Use optimized sha3-512 as the checksum function.
3821 This option is deprecated, since now meta information is included in
3822 generic verification header and meta verification happens by
3823 default. For detailed information see the description of the
3824 :option:`verify` setting. This option is kept because of
3825 compatibility's sake with old configurations. Do not use it.
3828 Verify a strict pattern. Normally fio includes a header with some
3829 basic information and checksumming, but if this option is set, only
3830 the specific pattern set with :option:`verify_pattern` is verified.
3833 Only pretend to verify. Useful for testing internals with
3834 :option:`ioengine`\=null, not for much else.
3836 This option can be used for repeated burn-in tests of a system to make sure
3837 that the written data is also correctly read back. If the data direction
3838 given is a read or random read, fio will assume that it should verify a
3839 previously written file. If the data direction includes any form of write,
3840 the verify will be of the newly written data.
3842 To avoid false verification errors, do not use the norandommap option when
3843 verifying data with async I/O engines and I/O depths > 1. Or use the
3844 norandommap and the lfsr random generator together to avoid writing to the
3845 same offset with multiple outstanding I/Os.
3847 .. option:: verify_offset=int
3849 Swap the verification header with data somewhere else in the block before
3850 writing. It is swapped back before verifying.
3852 .. option:: verify_interval=int
3854 Write the verification header at a finer granularity than the
3855 :option:`blocksize`. It will be written for chunks the size of
3856 ``verify_interval``. :option:`blocksize` should divide this evenly.
3858 .. option:: verify_pattern=str
3860 If set, fio will fill the I/O buffers with this pattern. Fio defaults to
3861 filling with totally random bytes, but sometimes it's interesting to fill
3862 with a known pattern for I/O verification purposes. Depending on the width
3863 of the pattern, fio will fill 1/2/3/4 bytes of the buffer at the time (it can
3864 be either a decimal or a hex number). The ``verify_pattern`` if larger than
3865 a 32-bit quantity has to be a hex number that starts with either "0x" or
3866 "0X". Use with :option:`verify`. Also, ``verify_pattern`` supports %o
3867 format, which means that for each block offset will be written and then
3868 verified back, e.g.::
3872 Or use combination of everything::
3874 verify_pattern=0xff%o"abcd"-12
3876 .. option:: verify_fatal=bool
3878 Normally fio will keep checking the entire contents before quitting on a
3879 block verification failure. If this option is set, fio will exit the job on
3880 the first observed failure. Default: false.
3882 .. option:: verify_dump=bool
3884 If set, dump the contents of both the original data block and the data block
3885 we read off disk to files. This allows later analysis to inspect just what
3886 kind of data corruption occurred. Off by default.
3888 .. option:: verify_async=int
3890 Fio will normally verify I/O inline from the submitting thread. This option
3891 takes an integer describing how many async offload threads to create for I/O
3892 verification instead, causing fio to offload the duty of verifying I/O
3893 contents to one or more separate threads. If using this offload option, even
3894 sync I/O engines can benefit from using an :option:`iodepth` setting higher
3895 than 1, as it allows them to have I/O in flight while verifies are running.
3896 Defaults to 0 async threads, i.e. verification is not asynchronous.
3898 .. option:: verify_async_cpus=str
3900 Tell fio to set the given CPU affinity on the async I/O verification
3901 threads. See :option:`cpus_allowed` for the format used.
3903 .. option:: verify_backlog=int
3905 Fio will normally verify the written contents of a job that utilizes verify
3906 once that job has completed. In other words, everything is written then
3907 everything is read back and verified. You may want to verify continually
3908 instead for a variety of reasons. Fio stores the meta data associated with
3909 an I/O block in memory, so for large verify workloads, quite a bit of memory
3910 would be used up holding this meta data. If this option is enabled, fio will
3911 write only N blocks before verifying these blocks.
3913 .. option:: verify_backlog_batch=int
3915 Control how many blocks fio will verify if :option:`verify_backlog` is
3916 set. If not set, will default to the value of :option:`verify_backlog`
3917 (meaning the entire queue is read back and verified). If
3918 ``verify_backlog_batch`` is less than :option:`verify_backlog` then not all
3919 blocks will be verified, if ``verify_backlog_batch`` is larger than
3920 :option:`verify_backlog`, some blocks will be verified more than once.
3922 .. option:: verify_state_save=bool
3924 When a job exits during the write phase of a verify workload, save its
3925 current state. This allows fio to replay up until that point, if the verify
3926 state is loaded for the verify read phase. The format of the filename is,
3929 <type>-<jobname>-<jobindex>-verify.state.
3931 <type> is "local" for a local run, "sock" for a client/server socket
3932 connection, and "ip" (192.168.0.1, for instance) for a networked
3933 client/server connection. Defaults to true.
3935 .. option:: verify_state_load=bool
3937 If a verify termination trigger was used, fio stores the current write state
3938 of each thread. This can be used at verification time so that fio knows how
3939 far it should verify. Without this information, fio will run a full
3940 verification pass, according to the settings in the job file used. Default
3943 .. option:: experimental_verify=bool
3945 Enable experimental verification. Standard verify records I/O metadata
3946 for later use during the verification phase. Experimental verify
3947 instead resets the file after the write phase and then replays I/Os for
3948 the verification phase.
3950 .. option:: trim_percentage=int
3952 Number of verify blocks to discard/trim.
3954 .. option:: trim_verify_zero=bool
3956 Verify that trim/discarded blocks are returned as zeros.
3958 .. option:: trim_backlog=int
3960 Trim after this number of blocks are written.
3962 .. option:: trim_backlog_batch=int
3964 Trim this number of I/O blocks.
3969 .. option:: steadystate=str:float, ss=str:float
3971 Define the criterion and limit for assessing steady state performance. The
3972 first parameter designates the criterion whereas the second parameter sets
3973 the threshold. When the criterion falls below the threshold for the
3974 specified duration, the job will stop. For example, `iops_slope:0.1%` will
3975 direct fio to terminate the job when the least squares regression slope
3976 falls below 0.1% of the mean IOPS. If :option:`group_reporting` is enabled
3977 this will apply to all jobs in the group. Below is the list of available
3978 steady state assessment criteria. All assessments are carried out using only
3979 data from the rolling collection window. Threshold limits can be expressed
3980 as a fixed value or as a percentage of the mean in the collection window.
3982 When using this feature, most jobs should include the :option:`time_based`
3983 and :option:`runtime` options or the :option:`loops` option so that fio does not
3984 stop running after it has covered the full size of the specified file(s) or device(s).
3987 Collect IOPS data. Stop the job if all individual IOPS measurements
3988 are within the specified limit of the mean IOPS (e.g., ``iops:2``
3989 means that all individual IOPS values must be within 2 of the mean,
3990 whereas ``iops:0.2%`` means that all individual IOPS values must be
3991 within 0.2% of the mean IOPS to terminate the job).
3994 Collect IOPS data and calculate the least squares regression
3995 slope. Stop the job if the slope falls below the specified limit.
3998 Collect bandwidth data. Stop the job if all individual bandwidth
3999 measurements are within the specified limit of the mean bandwidth.
4002 Collect bandwidth data and calculate the least squares regression
4003 slope. Stop the job if the slope falls below the specified limit.
4005 .. option:: steadystate_duration=time, ss_dur=time
4007 A rolling window of this duration will be used to judge whether steady
4008 state has been reached. Data will be collected every
4009 :option:`ss_interval`. The default is 0 which disables steady state
4010 detection. When the unit is omitted, the value is interpreted in
4013 .. option:: steadystate_ramp_time=time, ss_ramp=time
4015 Allow the job to run for the specified duration before beginning data
4016 collection for checking the steady state job termination criterion. The
4017 default is 0. When the unit is omitted, the value is interpreted in seconds.
4019 .. option:: steadystate_check_interval=time, ss_interval=time
4021 The values during the rolling window will be collected with a period of
4022 this value. If :option:`ss_interval` is 30s and :option:`ss_dur` is
4023 300s, 10 measurements will be taken. Default is 1s but that might not
4024 converge, especially for slower devices, so set this accordingly. When
4025 the unit is omitted, the value is interpreted in seconds.
4028 Measurements and reporting
4029 ~~~~~~~~~~~~~~~~~~~~~~~~~~
4031 .. option:: per_job_logs=bool
4033 If set to true, fio generates bw/clat/iops logs with per job unique
4034 filenames. If set to false, jobs with identical names will share a log
4035 filename. Note that when this option is set to false log files will be
4036 opened in append mode and if log files already exist the previous
4037 contents will not be overwritten. Default: true.
4039 .. option:: group_reporting
4041 It may sometimes be interesting to display statistics for groups of jobs as
4042 a whole instead of for each individual job. This is especially true if
4043 :option:`numjobs` is used; looking at individual thread/process output
4044 quickly becomes unwieldy. To see the final report per-group instead of
4045 per-job, use :option:`group_reporting`. Jobs in a file will be part of the
4046 same reporting group, unless if separated by a :option:`stonewall`, or by
4047 using :option:`new_group`.
4049 NOTE: When :option:`group_reporting` is used along with `json` output,
4050 there are certain per-job properties which can be different between jobs
4051 but do not have a natural group-level equivalent. Examples include
4052 `kb_base`, `unit_base`, `sig_figs`, `thread_number`, `pid`, and
4053 `job_start`. For these properties, the values for the first job are
4054 recorded for the group.
4056 .. option:: new_group
4058 Start a new reporting group. See: :option:`group_reporting`. If not given,
4059 all jobs in a file will be part of the same reporting group, unless
4060 separated by a :option:`stonewall`.
4062 .. option:: stats=bool
4064 By default, fio collects and shows final output results for all jobs
4065 that run. If this option is set to 0, then fio will ignore it in
4066 the final stat output.
4068 .. option:: write_bw_log=str
4070 If given, write a bandwidth log for this job. Can be used to store data of
4071 the bandwidth of the jobs in their lifetime.
4073 If no str argument is given, the default filename of
4074 :file:`jobname_type.x.log` is used. Even when the argument is given, fio
4075 will still append the type of log. So if one specifies::
4079 The actual log name will be :file:`foo_bw.x.log` where `x` is the index
4080 of the job (`1..N`, where `N` is the number of jobs). If
4081 :option:`per_job_logs` is false, then the filename will not include the
4084 The included :command:`fio_generate_plots` script uses :command:`gnuplot` to turn these
4085 text files into nice graphs. See `Log File Formats`_ for how data is
4086 structured within the file.
4088 .. option:: write_lat_log=str
4090 Same as :option:`write_bw_log`, except this option creates I/O
4091 submission (e.g., :file:`name_slat.x.log`), completion (e.g.,
4092 :file:`name_clat.x.log`), and total (e.g., :file:`name_lat.x.log`)
4093 latency files instead. See :option:`write_bw_log` for details about
4094 the filename format and `Log File Formats`_ for how data is structured
4097 .. option:: write_hist_log=str
4099 Same as :option:`write_bw_log` but writes an I/O completion latency
4100 histogram file (e.g., :file:`name_hist.x.log`) instead. Note that this
4101 file will be empty unless :option:`log_hist_msec` has also been set.
4102 See :option:`write_bw_log` for details about the filename format and
4103 `Log File Formats`_ for how data is structured within the file.
4105 .. option:: write_iops_log=str
4107 Same as :option:`write_bw_log`, but writes an IOPS file (e.g.
4108 :file:`name_iops.x.log`) instead. Because fio defaults to individual
4109 I/O logging, the value entry in the IOPS log will be 1 unless windowed
4110 logging (see :option:`log_avg_msec`) has been enabled. See
4111 :option:`write_bw_log` for details about the filename format and `Log
4112 File Formats`_ for how data is structured within the file.
4114 .. option:: log_entries=int
4116 By default, fio will log an entry in the iops, latency, or bw log for
4117 every I/O that completes. The initial number of I/O log entries is 1024.
4118 When the log entries are all used, new log entries are dynamically
4119 allocated. This dynamic log entry allocation may negatively impact
4120 time-related statistics such as I/O tail latencies (e.g. 99.9th percentile
4121 completion latency). This option allows specifying a larger initial
4122 number of log entries to avoid run-time allocations of new log entries,
4123 resulting in more precise time-related I/O statistics.
4124 Also see :option:`log_avg_msec`. Defaults to 1024.
4126 .. option:: log_avg_msec=int
4128 By default, fio will log an entry in the iops, latency, or bw log for
4129 every I/O that completes. When writing to the disk log, that can
4130 quickly grow to a very large size. Setting this option directs fio to
4131 instead record an average over the specified duration for each log
4132 entry, reducing the resolution of the log. When the job completes, fio
4133 will flush any accumulated latency log data, so the final log interval
4134 may not match the value specified by this option and there may even be
4135 duplicate timestamps. See :option:`log_window_value` as well. Defaults
4136 to 0, logging entries for each I/O. Also see `Log File Formats`_.
4138 .. option:: log_hist_msec=int
4140 Same as :option:`log_avg_msec`, but logs entries for completion latency
4141 histograms. Computing latency percentiles from averages of intervals using
4142 :option:`log_avg_msec` is inaccurate. Setting this option makes fio log
4143 histogram entries over the specified period of time, reducing log sizes for
4144 high IOPS devices while retaining percentile accuracy. See
4145 :option:`log_hist_coarseness` and :option:`write_hist_log` as well.
4146 Defaults to 0, meaning histogram logging is disabled.
4148 .. option:: log_hist_coarseness=int
4150 Integer ranging from 0 to 6, defining the coarseness of the resolution of
4151 the histogram logs enabled with :option:`log_hist_msec`. For each increment
4152 in coarseness, fio outputs half as many bins. Defaults to 0, for which
4153 histogram logs contain 1216 latency bins. See :option:`write_hist_log`
4154 and `Log File Formats`_.
4156 .. option:: log_window_value=str, log_max_value=str
4158 If :option:`log_avg_msec` is set, fio by default logs the average over that
4159 window. This option determines whether fio logs the average, maximum or
4160 both the values over the window. This only affects the latency logging,
4161 as both average and maximum values for iops or bw log will be same.
4162 Accepted values are:
4165 Log average value over the window. The default.
4168 Log maximum value in the window.
4171 Log both average and maximum value over the window.
4174 Backward-compatible alias for **avg**.
4177 Backward-compatible alias for **max**.
4179 .. option:: log_offset=bool
4181 If this is set, the iolog options will include the byte offset for the I/O
4182 entry as well as the other data values. Defaults to 0 meaning that
4183 offsets are not present in logs. Also see `Log File Formats`_.
4185 .. option:: log_compression=int
4187 If this is set, fio will compress the I/O logs as it goes, to keep the
4188 memory footprint lower. When a log reaches the specified size, that chunk is
4189 removed and compressed in the background. Given that I/O logs are fairly
4190 highly compressible, this yields a nice memory savings for longer runs. The
4191 downside is that the compression will consume some background CPU cycles, so
4192 it may impact the run. This, however, is also true if the logging ends up
4193 consuming most of the system memory. So pick your poison. The I/O logs are
4194 saved normally at the end of a run, by decompressing the chunks and storing
4195 them in the specified log file. This feature depends on the availability of
4198 .. option:: log_compression_cpus=str
4200 Define the set of CPUs that are allowed to handle online log compression for
4201 the I/O jobs. This can provide better isolation between performance
4202 sensitive jobs, and background compression work. See
4203 :option:`cpus_allowed` for the format used.
4205 .. option:: log_store_compressed=bool
4207 If set, fio will store the log files in a compressed format. They can be
4208 decompressed with fio, using the :option:`--inflate-log` command line
4209 parameter. The files will be stored with a :file:`.fz` suffix.
4211 .. option:: log_unix_epoch=bool
4213 Backwards compatible alias for log_alternate_epoch.
4215 .. option:: log_alternate_epoch=bool
4217 If set, fio will log timestamps based on the epoch used by the clock specified
4218 in the log_alternate_epoch_clock_id option, to the log files produced by
4219 enabling write_type_log for each log type, instead of the default zero-based
4222 .. option:: log_alternate_epoch_clock_id=int
4224 Specifies the clock_id to be used by clock_gettime to obtain the alternate
4225 epoch if log_alternate_epoch is true. Otherwise has no effect. Default
4226 value is 0, or CLOCK_REALTIME.
4228 .. option:: block_error_percentiles=bool
4230 If set, record errors in trim block-sized units from writes and trims and
4231 output a histogram of how many trims it took to get to errors, and what kind
4232 of error was encountered.
4234 .. option:: bwavgtime=int
4236 Average the calculated bandwidth over the given time. Value is specified in
4237 milliseconds. If the job also does bandwidth logging through
4238 :option:`write_bw_log`, then the minimum of this option and
4239 :option:`log_avg_msec` will be used. Default: 500ms.
4241 .. option:: iopsavgtime=int
4243 Average the calculated IOPS over the given time. Value is specified in
4244 milliseconds. If the job also does IOPS logging through
4245 :option:`write_iops_log`, then the minimum of this option and
4246 :option:`log_avg_msec` will be used. Default: 500ms.
4248 .. option:: disk_util=bool
4250 Generate disk utilization statistics, if the platform supports it.
4253 .. option:: disable_lat=bool
4255 Disable measurements of total latency numbers. Useful only for cutting back
4256 the number of calls to :manpage:`gettimeofday(2)`, as that does impact
4257 performance at really high IOPS rates. Note that to really get rid of a
4258 large amount of these calls, this option must be used with
4259 :option:`disable_slat` and :option:`disable_bw_measurement` as well.
4261 .. option:: disable_clat=bool
4263 Disable measurements of completion latency numbers. See
4264 :option:`disable_lat`.
4266 .. option:: disable_slat=bool
4268 Disable measurements of submission latency numbers. See
4269 :option:`disable_lat`.
4271 .. option:: disable_bw_measurement=bool, disable_bw=bool
4273 Disable measurements of throughput/bandwidth numbers. See
4274 :option:`disable_lat`.
4276 .. option:: slat_percentiles=bool
4278 Report submission latency percentiles. Submission latency is not recorded
4279 for synchronous ioengines.
4281 .. option:: clat_percentiles=bool
4283 Report completion latency percentiles.
4285 .. option:: lat_percentiles=bool
4287 Report total latency percentiles. Total latency is the sum of submission
4288 latency and completion latency.
4290 .. option:: percentile_list=float_list
4292 Overwrite the default list of percentiles for latencies and the block error
4293 histogram. Each number is a floating point number in the range (0,100], and
4294 the maximum length of the list is 20. Use ``:`` to separate the numbers. For
4295 example, ``--percentile_list=99.5:99.9`` will cause fio to report the
4296 latency durations below which 99.5% and 99.9% of the observed latencies fell,
4299 .. option:: significant_figures=int
4301 If using :option:`--output-format` of `normal`, set the significant
4302 figures to this value. Higher values will yield more precise IOPS and
4303 throughput units, while lower values will round. Requires a minimum
4304 value of 1 and a maximum value of 10. Defaults to 4.
4310 .. option:: exitall_on_error
4312 When one job finishes in error, terminate the rest. The default is to wait
4313 for each job to finish.
4315 .. option:: continue_on_error=str
4317 Normally fio will exit the job on the first observed failure. If this option
4318 is set, fio will continue the job when there is a 'non-fatal error' (EIO or
4319 EILSEQ) until the runtime is exceeded or the I/O size specified is
4320 completed. If this option is used, there are two more stats that are
4321 appended, the total error count and the first error. The error field given
4322 in the stats is the first error that was hit during the run.
4324 Note: a write error from the device may go unnoticed by fio when using
4325 buffered IO, as the write() (or similar) system call merely dirties the
4326 kernel pages, unless :option:`sync` or :option:`direct` is used. Device IO
4327 errors occur when the dirty data is actually written out to disk. If fully
4328 sync writes aren't desirable, :option:`fsync` or :option:`fdatasync` can be
4329 used as well. This is specific to writes, as reads are always synchronous.
4331 The allowed values are:
4334 Exit on any I/O or verify errors.
4337 Continue on read errors, exit on all others.
4340 Continue on write errors, exit on all others.
4343 Continue on any I/O error, exit on all others.
4346 Continue on verify errors, exit on all others.
4349 Continue on all errors.
4352 Backward-compatible alias for 'none'.
4355 Backward-compatible alias for 'all'.
4357 .. option:: ignore_error=str
4359 Sometimes you want to ignore some errors during test in that case you can
4360 specify error list for each error type, instead of only being able to
4361 ignore the default 'non-fatal error' using :option:`continue_on_error`.
4362 ``ignore_error=READ_ERR_LIST,WRITE_ERR_LIST,VERIFY_ERR_LIST`` errors for
4363 given error type is separated with ':'. Error may be symbol ('ENOSPC',
4364 'ENOMEM') or integer. Example::
4366 ignore_error=EAGAIN,ENOSPC:122
4368 This option will ignore EAGAIN from READ, and ENOSPC and 122(EDQUOT) from
4369 WRITE. This option works by overriding :option:`continue_on_error` with
4370 the list of errors for each error type if any.
4372 .. option:: error_dump=bool
4374 If set dump every error even if it is non fatal, true by default. If
4375 disabled only fatal error will be dumped.
4377 Running predefined workloads
4378 ----------------------------
4380 Fio includes predefined profiles that mimic the I/O workloads generated by
4383 .. option:: profile=str
4385 The predefined workload to run. Current profiles are:
4388 Threaded I/O bench (tiotest/tiobench) like workload.
4391 Aerospike Certification Tool (ACT) like workload.
4393 To view a profile's additional options use :option:`--cmdhelp` after specifying
4394 the profile. For example::
4396 $ fio --profile=act --cmdhelp
4401 .. option:: device-names=str
4406 .. option:: load=int
4409 ACT load multiplier. Default: 1.
4411 .. option:: test-duration=time
4414 How long the entire test takes to run. When the unit is omitted, the value
4415 is given in seconds. Default: 24h.
4417 .. option:: threads-per-queue=int
4420 Number of read I/O threads per device. Default: 8.
4422 .. option:: read-req-num-512-blocks=int
4425 Number of 512B blocks to read at the time. Default: 3.
4427 .. option:: large-block-op-kbytes=int
4430 Size of large block ops in KiB (writes). Default: 131072.
4435 Set to run ACT prep phase.
4437 Tiobench profile options
4438 ~~~~~~~~~~~~~~~~~~~~~~~~
4440 .. option:: size=str
4445 .. option:: block=int
4448 Block size in bytes. Default: 4096.
4450 .. option:: numruns=int
4460 .. option:: threads=int
4465 Interpreting the output
4466 -----------------------
4469 Example output was based on the following:
4470 TZ=UTC fio --iodepth=8 --ioengine=null --size=100M --time_based \
4471 --rate=1256k --bs=14K --name=quick --runtime=1s --name=mixed \
4472 --runtime=2m --rw=rw
4474 Fio spits out a lot of output. While running, fio will display the status of the
4475 jobs created. An example of that would be::
4477 Jobs: 1 (f=1): [_(1),M(1)][24.8%][r=20.5MiB/s,w=23.5MiB/s][r=82,w=94 IOPS][eta 01m:31s]
4479 The characters inside the first set of square brackets denote the current status of
4480 each thread. The first character is the first job defined in the job file, and so
4481 forth. The possible values (in typical life cycle order) are:
4483 +------+-----+-----------------------------------------------------------+
4485 +======+=====+===========================================================+
4486 | P | | Thread setup, but not started. |
4487 +------+-----+-----------------------------------------------------------+
4488 | C | | Thread created. |
4489 +------+-----+-----------------------------------------------------------+
4490 | I | | Thread initialized, waiting or generating necessary data. |
4491 +------+-----+-----------------------------------------------------------+
4492 | | p | Thread running pre-reading file(s). |
4493 +------+-----+-----------------------------------------------------------+
4494 | | / | Thread is in ramp period. |
4495 +------+-----+-----------------------------------------------------------+
4496 | | R | Running, doing sequential reads. |
4497 +------+-----+-----------------------------------------------------------+
4498 | | r | Running, doing random reads. |
4499 +------+-----+-----------------------------------------------------------+
4500 | | W | Running, doing sequential writes. |
4501 +------+-----+-----------------------------------------------------------+
4502 | | w | Running, doing random writes. |
4503 +------+-----+-----------------------------------------------------------+
4504 | | M | Running, doing mixed sequential reads/writes. |
4505 +------+-----+-----------------------------------------------------------+
4506 | | m | Running, doing mixed random reads/writes. |
4507 +------+-----+-----------------------------------------------------------+
4508 | | D | Running, doing sequential trims. |
4509 +------+-----+-----------------------------------------------------------+
4510 | | d | Running, doing random trims. |
4511 +------+-----+-----------------------------------------------------------+
4512 | | F | Running, currently waiting for :manpage:`fsync(2)`. |
4513 +------+-----+-----------------------------------------------------------+
4514 | | V | Running, doing verification of written data. |
4515 +------+-----+-----------------------------------------------------------+
4516 | f | | Thread finishing. |
4517 +------+-----+-----------------------------------------------------------+
4518 | E | | Thread exited, not reaped by main thread yet. |
4519 +------+-----+-----------------------------------------------------------+
4520 | _ | | Thread reaped. |
4521 +------+-----+-----------------------------------------------------------+
4522 | X | | Thread reaped, exited with an error. |
4523 +------+-----+-----------------------------------------------------------+
4524 | K | | Thread reaped, exited due to signal. |
4525 +------+-----+-----------------------------------------------------------+
4528 Example output was based on the following:
4529 TZ=UTC fio --iodepth=8 --ioengine=null --size=100M --runtime=58m \
4530 --time_based --rate=2512k --bs=256K --numjobs=10 \
4531 --name=readers --rw=read --name=writers --rw=write
4533 Fio will condense the thread string as not to take up more space on the command
4534 line than needed. For instance, if you have 10 readers and 10 writers running,
4535 the output would look like this::
4537 Jobs: 20 (f=20): [R(10),W(10)][4.0%][r=20.5MiB/s,w=23.5MiB/s][r=82,w=94 IOPS][eta 57m:36s]
4539 Note that the status string is displayed in order, so it's possible to tell which of
4540 the jobs are currently doing what. In the example above this means that jobs 1--10
4541 are readers and 11--20 are writers.
4543 The other values are fairly self explanatory -- number of threads currently
4544 running and doing I/O, the number of currently open files (f=), the estimated
4545 completion percentage, the rate of I/O since last check (read speed listed first,
4546 then write speed and optionally trim speed) in terms of bandwidth and IOPS,
4547 and time to completion for the current running group. It's impossible to estimate
4548 runtime of the following groups (if any).
4551 Example output was based on the following:
4552 TZ=UTC fio --iodepth=16 --ioengine=posixaio --filename=/tmp/fiofile \
4553 --direct=1 --size=100M --time_based --runtime=50s --rate_iops=89 \
4554 --bs=7K --name=Client1 --rw=write
4556 When fio is done (or interrupted by :kbd:`Ctrl-C`), it will show the data for
4557 each thread, group of threads, and disks in that order. For each overall thread (or
4558 group) the output looks like::
4560 Client1: (groupid=0, jobs=1): err= 0: pid=16109: Sat Jun 24 12:07:54 2017
4561 write: IOPS=88, BW=623KiB/s (638kB/s)(30.4MiB/50032msec)
4562 slat (nsec): min=500, max=145500, avg=8318.00, stdev=4781.50
4563 clat (usec): min=170, max=78367, avg=4019.02, stdev=8293.31
4564 lat (usec): min=174, max=78375, avg=4027.34, stdev=8291.79
4565 clat percentiles (usec):
4566 | 1.00th=[ 302], 5.00th=[ 326], 10.00th=[ 343], 20.00th=[ 363],
4567 | 30.00th=[ 392], 40.00th=[ 404], 50.00th=[ 416], 60.00th=[ 445],
4568 | 70.00th=[ 816], 80.00th=[ 6718], 90.00th=[12911], 95.00th=[21627],
4569 | 99.00th=[43779], 99.50th=[51643], 99.90th=[68682], 99.95th=[72877],
4571 bw ( KiB/s): min= 532, max= 686, per=0.10%, avg=622.87, stdev=24.82, samples= 100
4572 iops : min= 76, max= 98, avg=88.98, stdev= 3.54, samples= 100
4573 lat (usec) : 250=0.04%, 500=64.11%, 750=4.81%, 1000=2.79%
4574 lat (msec) : 2=4.16%, 4=1.84%, 10=4.90%, 20=11.33%, 50=5.37%
4575 lat (msec) : 100=0.65%
4576 cpu : usr=0.27%, sys=0.18%, ctx=12072, majf=0, minf=21
4577 IO depths : 1=85.0%, 2=13.1%, 4=1.8%, 8=0.1%, 16=0.0%, 32=0.0%, >=64=0.0%
4578 submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
4579 complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
4580 issued rwt: total=0,4450,0, short=0,0,0, dropped=0,0,0
4581 latency : target=0, window=0, percentile=100.00%, depth=8
4583 The job name (or first job's name when using :option:`group_reporting`) is printed,
4584 along with the group id, count of jobs being aggregated, last error id seen (which
4585 is 0 when there are no errors), pid/tid of that thread and the time the job/group
4586 completed. Below are the I/O statistics for each data direction performed (showing
4587 writes in the example above). In the order listed, they denote:
4590 The string before the colon shows the I/O direction the statistics
4591 are for. **IOPS** is the average I/Os performed per second. **BW**
4592 is the average bandwidth rate shown as: value in power of 2 format
4593 (value in power of 10 format). The last two values show: (**total
4594 I/O performed** in power of 2 format / **runtime** of that thread).
4597 Submission latency (**min** being the minimum, **max** being the
4598 maximum, **avg** being the average, **stdev** being the standard
4599 deviation). This is the time from when fio initialized the I/O
4600 to submission. For synchronous ioengines this includes the time
4601 up until just before the ioengine's queue function is called.
4602 For asynchronous ioengines this includes the time up through the
4603 completion of the ioengine's queue function (and commit function
4604 if it is defined). For sync I/O this row is not displayed as the
4605 slat is negligible. This value can be in nanoseconds,
4606 microseconds or milliseconds --- fio will choose the most
4607 appropriate base and print that (in the example above
4608 nanoseconds was the best scale). Note: in :option:`--minimal`
4609 mode latencies are always expressed in microseconds.
4612 Completion latency. Same names as slat, this denotes the time from
4613 submission to completion of the I/O pieces. For sync I/O, this
4614 represents the time from when the I/O was submitted to the
4615 operating system to when it was completed. For asynchronous
4616 ioengines this is the time from when the ioengine's queue (and
4617 commit if available) functions were completed to when the I/O's
4618 completion was reaped by fio.
4620 For file and directory operation engines, **clat** denotes the time
4621 to complete one file or directory operation.
4623 **filecreate engine**:the time cost to create a new file
4625 **filestat engine**: the time cost to look up an existing file
4627 **filedelete engine**:the time cost to delete a file
4629 **dircreate engine**: the time cost to create a new directory
4631 **dirstat engine**: the time cost to look up an existing directory
4633 **dirdelete engine**: the time cost to delete a directory
4636 Total latency. Same names as slat and clat, this denotes the time from
4637 when fio created the I/O unit to completion of the I/O operation.
4638 It is the sum of submission and completion latency.
4641 Bandwidth statistics based on measurements from discrete
4642 intervals. Fio continuously monitors bytes transferred and I/O
4643 operations completed. By default fio calculates bandwidth in
4644 each half-second interval (see :option:`bwavgtime`) and reports
4645 descriptive statistics for the measurements here. Same names as
4646 the xlat stats, but also includes the number of samples taken
4647 (**samples**) and an approximate percentage of total aggregate
4648 bandwidth this thread received in its group (**per**). This
4649 last value is only really useful if the threads in this group
4650 are on the same disk, since they are then competing for disk
4653 For file and directory operation engines, **bw** is meaningless.
4656 IOPS statistics based on measurements from discrete intervals.
4657 For details see the description for bw above. See
4658 :option:`iopsavgtime` to control the duration of the intervals.
4659 Same values reported here as for bw except for percentage.
4661 For file and directory operation engines, **iops** is the most
4662 fundamental index to denote the performance.
4663 It means how many files or directories can be operated per second.
4665 **filecreate engine**:number of files can be created per second
4667 **filestat engine**: number of files can be looked up per second
4669 **filedelete engine**:number of files can be deleted per second
4671 **dircreate engine**: number of directories can be created per second
4673 **dirstat engine**: number of directories can be looked up per second
4675 **dirdelete engine**: number of directories can be deleted per second
4677 **lat (nsec/usec/msec)**
4678 The distribution of I/O completion latencies. This is the time from when
4679 I/O leaves fio and when it gets completed. Unlike the separate
4680 read/write/trim sections above, the data here and in the remaining
4681 sections apply to all I/Os for the reporting group. 250=0.04% means that
4682 0.04% of the I/Os completed in under 250us. 500=64.11% means that 64.11%
4683 of the I/Os required 250 to 499us for completion.
4686 CPU usage. User and system time, along with the number of context
4687 switches this thread went through, usage of system and user time, and
4688 finally the number of major and minor page faults. The CPU utilization
4689 numbers are averages for the jobs in that reporting group, while the
4690 context and fault counters are summed.
4693 The distribution of I/O depths over the job lifetime. The numbers are
4694 divided into powers of 2 and each entry covers depths from that value
4695 up to those that are lower than the next entry -- e.g., 16= covers
4696 depths from 16 to 31. Note that the range covered by a depth
4697 distribution entry can be different to the range covered by the
4698 equivalent submit/complete distribution entry.
4701 How many pieces of I/O were submitting in a single submit call. Each
4702 entry denotes that amount and below, until the previous entry -- e.g.,
4703 16=100% means that we submitted anywhere between 9 to 16 I/Os per submit
4704 call. Note that the range covered by a submit distribution entry can
4705 be different to the range covered by the equivalent depth distribution
4709 Like the above submit number, but for completions instead.
4712 The number of read/write/trim requests issued, and how many of them were
4716 These values are for :option:`latency_target` and related options. When
4717 these options are engaged, this section describes the I/O depth required
4718 to meet the specified latency target.
4721 Example output was based on the following:
4722 TZ=UTC fio --ioengine=null --iodepth=2 --size=100M --numjobs=2 \
4723 --rate_process=poisson --io_limit=32M --name=read --bs=128k \
4724 --rate=11M --name=write --rw=write --bs=2k --rate=700k
4726 After each client has been listed, the group statistics are printed. They
4727 will look like this::
4729 Run status group 0 (all jobs):
4730 READ: bw=20.9MiB/s (21.9MB/s), 10.4MiB/s-10.8MiB/s (10.9MB/s-11.3MB/s), io=64.0MiB (67.1MB), run=2973-3069msec
4731 WRITE: bw=1231KiB/s (1261kB/s), 616KiB/s-621KiB/s (630kB/s-636kB/s), io=64.0MiB (67.1MB), run=52747-53223msec
4733 For each data direction it prints:
4736 Aggregate bandwidth of threads in this group followed by the
4737 minimum and maximum bandwidth of all the threads in this group.
4738 Values outside of brackets are power-of-2 format and those
4739 within are the equivalent value in a power-of-10 format.
4741 Aggregate I/O performed of all threads in this group. The
4742 format is the same as bw.
4744 The smallest and longest runtimes of the threads in this group.
4746 And finally, the disk statistics are printed. This is Linux specific. They will look like this::
4748 Disk stats (read/write):
4749 sda: ios=16398/16511, sectors=32321/65472, merge=30/162, ticks=6853/819634, in_queue=826487, util=100.00%
4751 Each value is printed for both reads and writes, with reads first. The
4755 Number of I/Os performed by all groups.
4757 Amount of data transferred in units of 512 bytes for all groups.
4759 Number of merges performed by the I/O scheduler.
4761 Number of ticks we kept the disk busy.
4763 Total time spent in the disk queue.
4765 The disk utilization. A value of 100% means we kept the disk
4766 busy constantly, 50% would be a disk idling half of the time.
4768 It is also possible to get fio to dump the current output while it is running,
4769 without terminating the job. To do that, send fio the **USR1** signal. You can
4770 also get regularly timed dumps by using the :option:`--status-interval`
4771 parameter, or by creating a file in :file:`/tmp` named
4772 :file:`fio-dump-status`. If fio sees this file, it will unlink it and dump the
4773 current output status.
4779 For scripted usage where you typically want to generate tables or graphs of the
4780 results, fio can output the results in a semicolon separated format. The format
4781 is one long line of values, such as::
4783 2;card0;0;0;7139336;121836;60004;1;10109;27.932460;116.933948;220;126861;3495.446807;1085.368601;226;126864;3523.635629;1089.012448;24063;99944;50.275485%;59818.274627;5540.657370;7155060;122104;60004;1;8338;29.086342;117.839068;388;128077;5032.488518;1234.785715;391;128085;5061.839412;1236.909129;23436;100928;50.287926%;59964.832030;5644.844189;14.595833%;19.394167%;123706;0;7313;0.1%;0.1%;0.1%;0.1%;0.1%;0.1%;100.0%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.01%;0.02%;0.05%;0.16%;6.04%;40.40%;52.68%;0.64%;0.01%;0.00%;0.01%;0.00%;0.00%;0.00%;0.00%;0.00%
4784 A description of this job goes here.
4786 The job description (if provided) follows on a second line for terse v2.
4787 It appears on the same line for other terse versions.
4789 To enable terse output, use the :option:`--minimal` or
4790 :option:`--output-format`\=terse command line options. The
4791 first value is the version of the terse output format. If the output has to be
4792 changed for some reason, this number will be incremented by 1 to signify that
4795 Split up, the format is as follows (comments in brackets denote when a
4796 field was introduced or whether it's specific to some terse version):
4800 terse version, fio version [v3], jobname, groupid, error
4804 Total IO (KiB), bandwidth (KiB/sec), IOPS, runtime (msec)
4805 Submission latency: min, max, mean, stdev (usec)
4806 Completion latency: min, max, mean, stdev (usec)
4807 Completion latency percentiles: 20 fields (see below)
4808 Total latency: min, max, mean, stdev (usec)
4809 Bw (KiB/s): min, max, aggregate percentage of total, mean, stdev, number of samples [v5]
4810 IOPS [v5]: min, max, mean, stdev, number of samples
4816 Total IO (KiB), bandwidth (KiB/sec), IOPS, runtime (msec)
4817 Submission latency: min, max, mean, stdev (usec)
4818 Completion latency: min, max, mean, stdev (usec)
4819 Completion latency percentiles: 20 fields (see below)
4820 Total latency: min, max, mean, stdev (usec)
4821 Bw (KiB/s): min, max, aggregate percentage of total, mean, stdev, number of samples [v5]
4822 IOPS [v5]: min, max, mean, stdev, number of samples
4824 TRIM status [all but version 3]:
4826 Fields are similar to READ/WRITE status.
4830 user, system, context switches, major faults, minor faults
4834 <=1, 2, 4, 8, 16, 32, >=64
4836 I/O latencies microseconds::
4838 <=2, 4, 10, 20, 50, 100, 250, 500, 750, 1000
4840 I/O latencies milliseconds::
4842 <=2, 4, 10, 20, 50, 100, 250, 500, 750, 1000, 2000, >=2000
4844 Disk utilization [v3]::
4846 disk name, read ios, write ios, read merges, write merges, read ticks, write ticks,
4847 time spent in queue, disk utilization percentage
4849 Additional Info (dependent on continue_on_error, default off)::
4851 total # errors, first error code
4853 Additional Info (dependent on description being set)::
4857 Completion latency percentiles can be a grouping of up to 20 sets, so for the
4858 terse output fio writes all of them. Each field will look like this::
4862 which is the Xth percentile, and the `usec` latency associated with it.
4864 For `Disk utilization`, all disks used by fio are shown. So for each disk there
4865 will be a disk utilization section.
4867 Below is a single line containing short names for each of the fields in the
4868 minimal output v3, separated by semicolons::
4870 terse_version_3;fio_version;jobname;groupid;error;read_kb;read_bandwidth_kb;read_iops;read_runtime_ms;read_slat_min_us;read_slat_max_us;read_slat_mean_us;read_slat_dev_us;read_clat_min_us;read_clat_max_us;read_clat_mean_us;read_clat_dev_us;read_clat_pct01;read_clat_pct02;read_clat_pct03;read_clat_pct04;read_clat_pct05;read_clat_pct06;read_clat_pct07;read_clat_pct08;read_clat_pct09;read_clat_pct10;read_clat_pct11;read_clat_pct12;read_clat_pct13;read_clat_pct14;read_clat_pct15;read_clat_pct16;read_clat_pct17;read_clat_pct18;read_clat_pct19;read_clat_pct20;read_tlat_min_us;read_lat_max_us;read_lat_mean_us;read_lat_dev_us;read_bw_min_kb;read_bw_max_kb;read_bw_agg_pct;read_bw_mean_kb;read_bw_dev_kb;write_kb;write_bandwidth_kb;write_iops;write_runtime_ms;write_slat_min_us;write_slat_max_us;write_slat_mean_us;write_slat_dev_us;write_clat_min_us;write_clat_max_us;write_clat_mean_us;write_clat_dev_us;write_clat_pct01;write_clat_pct02;write_clat_pct03;write_clat_pct04;write_clat_pct05;write_clat_pct06;write_clat_pct07;write_clat_pct08;write_clat_pct09;write_clat_pct10;write_clat_pct11;write_clat_pct12;write_clat_pct13;write_clat_pct14;write_clat_pct15;write_clat_pct16;write_clat_pct17;write_clat_pct18;write_clat_pct19;write_clat_pct20;write_tlat_min_us;write_lat_max_us;write_lat_mean_us;write_lat_dev_us;write_bw_min_kb;write_bw_max_kb;write_bw_agg_pct;write_bw_mean_kb;write_bw_dev_kb;cpu_user;cpu_sys;cpu_csw;cpu_mjf;cpu_minf;iodepth_1;iodepth_2;iodepth_4;iodepth_8;iodepth_16;iodepth_32;iodepth_64;lat_2us;lat_4us;lat_10us;lat_20us;lat_50us;lat_100us;lat_250us;lat_500us;lat_750us;lat_1000us;lat_2ms;lat_4ms;lat_10ms;lat_20ms;lat_50ms;lat_100ms;lat_250ms;lat_500ms;lat_750ms;lat_1000ms;lat_2000ms;lat_over_2000ms;disk_name;disk_read_iops;disk_write_iops;disk_read_merges;disk_write_merges;disk_read_ticks;write_ticks;disk_queue_time;disk_util
4872 In client/server mode terse output differs from what appears when jobs are run
4873 locally. Disk utilization data is omitted from the standard terse output and
4874 for v3 and later appears on its own separate line at the end of each terse
4881 The `json` output format is intended to be both human readable and convenient
4882 for automated parsing. For the most part its sections mirror those of the
4883 `normal` output. The `runtime` value is reported in msec and the `bw` value is
4884 reported in 1024 bytes per second units.
4890 The `json+` output format is identical to the `json` output format except that it
4891 adds a full dump of the completion latency bins. Each `bins` object contains a
4892 set of (key, value) pairs where keys are latency durations and values count how
4893 many I/Os had completion latencies of the corresponding duration. For example,
4896 "bins" : { "87552" : 1, "89600" : 1, "94720" : 1, "96768" : 1, "97792" : 1, "99840" : 1, "100864" : 2, "103936" : 6, "104960" : 534, "105984" : 5995, "107008" : 7529, ... }
4898 This data indicates that one I/O required 87,552ns to complete, two I/Os required
4899 100,864ns to complete, and 7529 I/Os required 107,008ns to complete.
4901 Also included with fio is a Python script `fio_jsonplus_clat2csv` that takes
4902 json+ output and generates CSV-formatted latency data suitable for plotting.
4904 The latency durations actually represent the midpoints of latency intervals.
4905 For details refer to :file:`stat.h`.
4911 There are two trace file format that you can encounter. The older (v1) format is
4912 unsupported since version 1.20-rc3 (March 2008). It will still be described
4913 below in case that you get an old trace and want to understand it.
4915 In any case the trace is a simple text file with a single action per line.
4918 Trace file format v1
4919 ~~~~~~~~~~~~~~~~~~~~
4921 Each line represents a single I/O action in the following format::
4925 where `rw=0/1` for read/write, and the `offset` and `length` entries being in bytes.
4927 This format is not supported in fio versions >= 1.20-rc3.
4930 Trace file format v2
4931 ~~~~~~~~~~~~~~~~~~~~
4933 The second version of the trace file format was added in fio version 1.17. It
4934 allows one to access more than one file per trace and has a bigger set of possible
4937 The first line of the trace file has to be::
4941 Following this can be lines in two different formats, which are described below.
4943 The file management format::
4947 The `filename` is given as an absolute path. The `action` can be one of these:
4950 Add the given `filename` to the trace.
4952 Open the file with the given `filename`. The `filename` has to have
4953 been added with the **add** action before.
4955 Close the file with the given `filename`. The file has to have been
4959 The file I/O action format::
4961 filename action offset length
4963 The `filename` is given as an absolute path, and has to have been added and
4964 opened before it can be used with this format. The `offset` and `length` are
4965 given in bytes. The `action` can be one of these:
4968 Wait for `offset` microseconds. Everything below 100 is discarded.
4969 The time is relative to the previous `wait` statement. Note that
4970 action `wait` is not allowed as of version 3, as the same behavior
4971 can be achieved using timestamps.
4973 Read `length` bytes beginning from `offset`.
4975 Write `length` bytes beginning from `offset`.
4977 :manpage:`fsync(2)` the file.
4979 :manpage:`fdatasync(2)` the file.
4981 Trim the given file from the given `offset` for `length` bytes.
4984 Trace file format v3
4985 ~~~~~~~~~~~~~~~~~~~~
4987 The third version of the trace file format was added in fio version 3.31. It
4988 forces each action to have a timestamp associated with it.
4990 The first line of the trace file has to be::
4994 Following this can be lines in two different formats, which are described below.
4996 The file management format::
4998 timestamp filename action
5000 The file I/O action format::
5002 timestamp filename action offset length
5004 The `timestamp` is relative to the beginning of the run (ie starts at 0). The
5005 `filename`, `action`, `offset` and `length` are identical to version 2, except
5006 that version 3 does not allow the `wait` action.
5009 I/O Replay - Merging Traces
5010 ---------------------------
5012 Colocation is a common practice used to get the most out of a machine.
5013 Knowing which workloads play nicely with each other and which ones don't is
5014 a much harder task. While fio can replay workloads concurrently via multiple
5015 jobs, it leaves some variability up to the scheduler making results harder to
5016 reproduce. Merging is a way to make the order of events consistent.
5018 Merging is integrated into I/O replay and done when a
5019 :option:`merge_blktrace_file` is specified. The list of files passed to
5020 :option:`read_iolog` go through the merge process and output a single file
5021 stored to the specified file. The output file is passed on as if it were the
5022 only file passed to :option:`read_iolog`. An example would look like::
5024 $ fio --read_iolog="<file1>:<file2>" --merge_blktrace_file="<output_file>"
5026 Creating only the merged file can be done by passing the command line argument
5027 :option:`--merge-blktrace-only`.
5029 Scaling traces can be done to see the relative impact of any particular trace
5030 being slowed down or sped up. :option:`merge_blktrace_scalars` takes in a colon
5031 separated list of percentage scalars. It is index paired with the files passed
5032 to :option:`read_iolog`.
5034 With scaling, it may be desirable to match the running time of all traces.
5035 This can be done with :option:`merge_blktrace_iters`. It is index paired with
5036 :option:`read_iolog` just like :option:`merge_blktrace_scalars`.
5038 In an example, given two traces, A and B, each 60s long. If we want to see
5039 the impact of trace A issuing IOs twice as fast and repeat trace A over the
5040 runtime of trace B, the following can be done::
5042 $ fio --read_iolog="<trace_a>:"<trace_b>" --merge_blktrace_file"<output_file>" --merge_blktrace_scalars="50:100" --merge_blktrace_iters="2:1"
5044 This runs trace A at 2x the speed twice for approximately the same runtime as
5045 a single run of trace B.
5048 CPU idleness profiling
5049 ----------------------
5051 In some cases, we want to understand CPU overhead in a test. For example, we
5052 test patches for the specific goodness of whether they reduce CPU usage.
5053 Fio implements a balloon approach to create a thread per CPU that runs at idle
5054 priority, meaning that it only runs when nobody else needs the cpu.
5055 By measuring the amount of work completed by the thread, idleness of each CPU
5056 can be derived accordingly.
5058 An unit work is defined as touching a full page of unsigned characters. Mean and
5059 standard deviation of time to complete an unit work is reported in "unit work"
5060 section. Options can be chosen to report detailed percpu idleness or overall
5061 system idleness by aggregating percpu stats.
5064 Verification and triggers
5065 -------------------------
5067 Fio is usually run in one of two ways, when data verification is done. The first
5068 is a normal write job of some sort with verify enabled. When the write phase has
5069 completed, fio switches to reads and verifies everything it wrote. The second
5070 model is running just the write phase, and then later on running the same job
5071 (but with reads instead of writes) to repeat the same I/O patterns and verify
5072 the contents. Both of these methods depend on the write phase being completed,
5073 as fio otherwise has no idea how much data was written.
5075 With verification triggers, fio supports dumping the current write state to
5076 local files. Then a subsequent read verify workload can load this state and know
5077 exactly where to stop. This is useful for testing cases where power is cut to a
5078 server in a managed fashion, for instance.
5080 A verification trigger consists of two things:
5082 1) Storing the write state of each job.
5083 2) Executing a trigger command.
5085 The write state is relatively small, on the order of hundreds of bytes to single
5086 kilobytes. It contains information on the number of completions done, the last X
5089 A trigger is invoked either through creation ('touch') of a specified file in
5090 the system, or through a timeout setting. If fio is run with
5091 :option:`--trigger-file`\= :file:`/tmp/trigger-file`, then it will continually
5092 check for the existence of :file:`/tmp/trigger-file`. When it sees this file, it
5093 will fire off the trigger (thus saving state, and executing the trigger
5096 For client/server runs, there's both a local and remote trigger. If fio is
5097 running as a server backend, it will send the job states back to the client for
5098 safe storage, then execute the remote trigger, if specified. If a local trigger
5099 is specified, the server will still send back the write state, but the client
5100 will then execute the trigger.
5102 Verification trigger example
5103 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5105 Let's say we want to run a powercut test on the remote Linux machine 'server'.
5106 Our write workload is in :file:`write-test.fio`. We want to cut power to 'server' at
5107 some point during the run, and we'll run this test from the safety or our local
5108 machine, 'localbox'. On the server, we'll start the fio backend normally::
5110 server# fio --server
5112 and on the client, we'll fire off the workload::
5114 localbox$ fio --client=server --trigger-file=/tmp/my-trigger --trigger-remote="bash -c \"echo b > /proc/sysrq-triger\""
5116 We set :file:`/tmp/my-trigger` as the trigger file, and we tell fio to execute::
5118 echo b > /proc/sysrq-trigger
5120 on the server once it has received the trigger and sent us the write state. This
5121 will work, but it's not **really** cutting power to the server, it's merely
5122 abruptly rebooting it. If we have a remote way of cutting power to the server
5123 through IPMI or similar, we could do that through a local trigger command
5124 instead. Let's assume we have a script that does IPMI reboot of a given hostname,
5125 ipmi-reboot. On localbox, we could then have run fio with a local trigger
5128 localbox$ fio --client=server --trigger-file=/tmp/my-trigger --trigger="ipmi-reboot server"
5130 For this case, fio would wait for the server to send us the write state, then
5131 execute ``ipmi-reboot server`` when that happened.
5133 Loading verify state
5134 ~~~~~~~~~~~~~~~~~~~~
5136 To load stored write state, a read verification job file must contain the
5137 :option:`verify_state_load` option. If that is set, fio will load the previously
5138 stored state. For a local fio run this is done by loading the files directly,
5139 and on a client/server run, the server backend will ask the client to send the
5140 files over and load them from there.
5146 Fio supports a variety of log file formats, for logging latencies, bandwidth,
5147 and IOPS. The logs share a common format, which looks like this:
5149 *time* (`msec`), *value*, *data direction*, *block size* (`bytes`),
5150 *offset* (`bytes`), *command priority*
5152 *Time* for the log entry is always in milliseconds. The *value* logged depends
5153 on the type of log, it will be one of the following:
5156 Value is latency in nsecs
5162 *Data direction* is one of the following:
5171 The entry's *block size* is always in bytes. The *offset* is the position in bytes
5172 from the start of the file for that particular I/O. The logging of the offset can be
5173 toggled with :option:`log_offset`.
5175 *Command priority* is 0 for normal priority and 1 for high priority. This is controlled
5176 by the ioengine specific :option:`cmdprio_percentage`.
5178 Fio defaults to logging every individual I/O but when windowed logging is set
5179 through :option:`log_avg_msec`, either the average (by default), the maximum
5180 (:option:`log_window_value` is set to max) *value* seen over the specified period
5181 of time, or both the average *value* and maximum *value1* (:option:`log_window_value`
5182 is set to both) is recorded. The log file format when both the values are reported
5185 *time* (`msec`), *value*, *value1*, *data direction*, *block size* (`bytes`),
5186 *offset* (`bytes`), *command priority*
5189 Each *data direction* seen within the window period will aggregate its values in a
5190 separate row. Further, when using windowed logging the *block size* and *offset*
5191 entries will always contain 0.
5197 Normally fio is invoked as a stand-alone application on the machine where the
5198 I/O workload should be generated. However, the backend and frontend of fio can
5199 be run separately i.e., the fio server can generate an I/O workload on the "Device
5200 Under Test" while being controlled by a client on another machine.
5202 Start the server on the machine which has access to the storage DUT::
5206 where `args` defines what fio listens to. The arguments are of the form
5207 ``type,hostname`` or ``IP,port``. *type* is either ``ip`` (or ip4) for TCP/IP
5208 v4, ``ip6`` for TCP/IP v6, or ``sock`` for a local unix domain socket.
5209 *hostname* is either a hostname or IP address, and *port* is the port to listen
5210 to (only valid for TCP/IP, not a local socket). Some examples:
5214 Start a fio server, listening on all interfaces on the default port (8765).
5216 2) ``fio --server=ip:hostname,4444``
5218 Start a fio server, listening on IP belonging to hostname and on port 4444.
5220 3) ``fio --server=ip6:::1,4444``
5222 Start a fio server, listening on IPv6 localhost ::1 and on port 4444.
5224 4) ``fio --server=,4444``
5226 Start a fio server, listening on all interfaces on port 4444.
5228 5) ``fio --server=1.2.3.4``
5230 Start a fio server, listening on IP 1.2.3.4 on the default port.
5232 6) ``fio --server=sock:/tmp/fio.sock``
5234 Start a fio server, listening on the local socket :file:`/tmp/fio.sock`.
5236 Once a server is running, a "client" can connect to the fio server with::
5238 fio <local-args> --client=<server> <remote-args> <job file(s)>
5240 where `local-args` are arguments for the client where it is running, `server`
5241 is the connect string, and `remote-args` and `job file(s)` are sent to the
5242 server. The `server` string follows the same format as it does on the server
5243 side, to allow IP/hostname/socket and port strings.
5245 Note that all job options must be defined in job files when running fio as a
5246 client. Any job options specified in `remote-args` will be ignored.
5248 Fio can connect to multiple servers this way::
5250 fio --client=<server1> <job file(s)> --client=<server2> <job file(s)>
5252 If the job file is located on the fio server, then you can tell the server to
5253 load a local file as well. This is done by using :option:`--remote-config` ::
5255 fio --client=server --remote-config /path/to/file.fio
5257 Then fio will open this local (to the server) job file instead of being passed
5258 one from the client.
5260 If you have many servers (example: 100 VMs/containers), you can input a pathname
5261 of a file containing host IPs/names as the parameter value for the
5262 :option:`--client` option. For example, here is an example :file:`host.list`
5263 file containing 2 hostnames::
5265 host1.your.dns.domain
5266 host2.your.dns.domain
5268 The fio command would then be::
5270 fio --client=host.list <job file(s)>
5272 In this mode, you cannot input server-specific parameters or job files -- all
5273 servers receive the same job file.
5275 In order to let ``fio --client`` runs use a shared filesystem from multiple
5276 hosts, ``fio --client`` now prepends the IP address of the server to the
5277 filename. For example, if fio is using the directory :file:`/mnt/nfs/fio` and is
5278 writing filename :file:`fileio.tmp`, with a :option:`--client` `hostfile`
5279 containing two hostnames ``h1`` and ``h2`` with IP addresses 192.168.10.120 and
5280 192.168.10.121, then fio will create two files::
5282 /mnt/nfs/fio/192.168.10.120.fileio.tmp
5283 /mnt/nfs/fio/192.168.10.121.fileio.tmp
5285 Terse output in client/server mode will differ slightly from what is produced
5286 when fio is run in stand-alone mode. See the terse output section for details.