Commit | Line | Data |
---|---|---|
f80dba8d MT |
1 | How fio works |
2 | ------------- | |
3 | ||
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 | |
10 | basic parameters: | |
11 | ||
12 | `I/O type`_ | |
13 | ||
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? | |
18 | ||
19 | `Block size`_ | |
20 | ||
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. | |
23 | ||
24 | `I/O size`_ | |
25 | ||
26 | How much data are we going to be reading/writing. | |
27 | ||
28 | `I/O engine`_ | |
29 | ||
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 | |
32 | SG (SCSI generic sg). | |
33 | ||
34 | `I/O depth`_ | |
35 | ||
36 | If the I/O engine is async, how large a queuing depth do we want to | |
37 | maintain? | |
38 | ||
39 | ||
40 | `Target file/device`_ | |
41 | ||
42 | How many files are we spreading the workload over. | |
43 | ||
44 | `Threads, processes and job synchronization`_ | |
45 | ||
46 | How many threads or processes should we spread this workload over. | |
47 | ||
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. | |
50 | ||
51 | ||
52 | Command line options | |
53 | -------------------- | |
54 | ||
55 | .. option:: --debug=type | |
56 | ||
f50fbdda | 57 | Enable verbose tracing `type` of various fio actions. May be ``all`` for all types |
b034c0dd TK |
58 | or individual types separated by a comma (e.g. ``--debug=file,mem`` will |
59 | enable file and memory debugging). Currently, additional logging is | |
60 | available for: | |
f80dba8d | 61 | |
b034c0dd | 62 | *process* |
f80dba8d | 63 | Dump info related to processes. |
b034c0dd | 64 | *file* |
f80dba8d | 65 | Dump info related to file actions. |
b034c0dd | 66 | *io* |
f80dba8d | 67 | Dump info related to I/O queuing. |
b034c0dd | 68 | *mem* |
f80dba8d | 69 | Dump info related to memory allocations. |
b034c0dd | 70 | *blktrace* |
f80dba8d | 71 | Dump info related to blktrace setup. |
b034c0dd | 72 | *verify* |
f80dba8d | 73 | Dump info related to I/O verification. |
b034c0dd | 74 | *all* |
f80dba8d | 75 | Enable all debug options. |
b034c0dd | 76 | *random* |
f80dba8d | 77 | Dump info related to random offset generation. |
b034c0dd | 78 | *parse* |
f80dba8d | 79 | Dump info related to option matching and parsing. |
b034c0dd | 80 | *diskutil* |
f80dba8d | 81 | Dump info related to disk utilization updates. |
b034c0dd | 82 | *job:x* |
f80dba8d | 83 | Dump info only related to job number x. |
b034c0dd | 84 | *mutex* |
f80dba8d | 85 | Dump info only related to mutex up/down ops. |
b034c0dd | 86 | *profile* |
f80dba8d | 87 | Dump info related to profile extensions. |
b034c0dd | 88 | *time* |
f80dba8d | 89 | Dump info related to internal time keeping. |
b034c0dd | 90 | *net* |
f80dba8d | 91 | Dump info related to networking connections. |
b034c0dd | 92 | *rate* |
f80dba8d | 93 | Dump info related to I/O rate switching. |
b034c0dd | 94 | *compress* |
f80dba8d | 95 | Dump info related to log compress/decompress. |
a02ec45a VF |
96 | *steadystate* |
97 | Dump info related to steadystate detection. | |
98 | *helperthread* | |
99 | Dump info related to the helper thread. | |
100 | *zbd* | |
101 | Dump info related to support for zoned block devices. | |
b034c0dd | 102 | *?* or *help* |
f80dba8d MT |
103 | Show available debug options. |
104 | ||
105 | .. option:: --parse-only | |
106 | ||
25cd4b95 | 107 | Parse options only, don't start any I/O. |
f80dba8d | 108 | |
b9921d1a DZ |
109 | .. option:: --merge-blktrace-only |
110 | ||
111 | Merge blktraces only, don't start any I/O. | |
112 | ||
f80dba8d MT |
113 | .. option:: --output=filename |
114 | ||
115 | Write output to file `filename`. | |
116 | ||
f50fbdda | 117 | .. option:: --output-format=format |
b8f7e412 | 118 | |
f50fbdda | 119 | Set the reporting `format` to `normal`, `terse`, `json`, or `json+`. Multiple |
b8f7e412 TK |
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 | |
122 | buckets. | |
123 | ||
f80dba8d MT |
124 | .. option:: --bandwidth-log |
125 | ||
126 | Generate aggregate bandwidth logs. | |
127 | ||
128 | .. option:: --minimal | |
129 | ||
130 | Print statistics in a terse, semicolon-delimited format. | |
131 | ||
132 | .. option:: --append-terse | |
133 | ||
b034c0dd TK |
134 | Print statistics in selected mode AND terse, semicolon-delimited format. |
135 | **Deprecated**, use :option:`--output-format` instead to select multiple | |
136 | formats. | |
f80dba8d | 137 | |
f50fbdda | 138 | .. option:: --terse-version=version |
f80dba8d | 139 | |
f50fbdda | 140 | Set terse `version` output format (default 3, or 2 or 4 or 5). |
f80dba8d MT |
141 | |
142 | .. option:: --version | |
143 | ||
b8f7e412 | 144 | Print version information and exit. |
f80dba8d MT |
145 | |
146 | .. option:: --help | |
147 | ||
113f0e7c | 148 | Print a summary of the command line options and exit. |
f80dba8d MT |
149 | |
150 | .. option:: --cpuclock-test | |
151 | ||
152 | Perform test and validation of internal CPU clock. | |
153 | ||
113f0e7c | 154 | .. option:: --crctest=[test] |
f80dba8d | 155 | |
b034c0dd TK |
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. | |
f80dba8d MT |
159 | |
160 | .. option:: --cmdhelp=command | |
161 | ||
162 | Print help information for `command`. May be ``all`` for all commands. | |
163 | ||
164 | .. option:: --enghelp=[ioengine[,command]] | |
165 | ||
f50fbdda TK |
166 | List all commands defined by `ioengine`, or print help for `command` |
167 | defined by `ioengine`. If no `ioengine` is given, list all | |
b034c0dd | 168 | available ioengines. |
f80dba8d MT |
169 | |
170 | .. option:: --showcmd=jobfile | |
171 | ||
b8f7e412 | 172 | Convert `jobfile` to a set of command-line options. |
f80dba8d MT |
173 | |
174 | .. option:: --readonly | |
175 | ||
4027b2a1 VF |
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. | |
f80dba8d MT |
182 | |
183 | .. option:: --eta=when | |
184 | ||
b8f7e412 | 185 | Specifies when real-time ETA estimate should be printed. `when` may be |
db37d890 JA |
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. | |
189 | ||
190 | .. option:: --eta-interval=time | |
191 | ||
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 | |
195 | not supported. | |
f80dba8d MT |
196 | |
197 | .. option:: --eta-newline=time | |
198 | ||
947e0fe0 SW |
199 | Force a new line for every `time` period passed. When the unit is omitted, |
200 | the value is interpreted in seconds. | |
f80dba8d MT |
201 | |
202 | .. option:: --status-interval=time | |
203 | ||
aa6cb459 VF |
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, | |
c1f4de8a JA |
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. | |
f80dba8d MT |
211 | |
212 | .. option:: --section=name | |
213 | ||
b034c0dd TK |
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 | |
221 | parsed and used. | |
f80dba8d MT |
222 | |
223 | .. option:: --alloc-size=kb | |
224 | ||
4a419903 VF |
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. | |
b034c0dd TK |
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. | |
f80dba8d | 230 | |
b034c0dd TK |
231 | NOTE: While running :file:`.fio_smalloc.*` backing store files are visible |
232 | in :file:`/tmp`. | |
f80dba8d MT |
233 | |
234 | .. option:: --warnings-fatal | |
235 | ||
b034c0dd TK |
236 | All fio parser warnings are fatal, causing fio to exit with an |
237 | error. | |
f80dba8d MT |
238 | |
239 | .. option:: --max-jobs=nr | |
240 | ||
f50fbdda | 241 | Set the maximum number of threads/processes to support to `nr`. |
818322cc | 242 | NOTE: On Linux, it may be necessary to increase the shared-memory |
71aa48eb | 243 | limit (:file:`/proc/sys/kernel/shmmax`) if fio runs into errors while |
818322cc | 244 | creating jobs. |
f80dba8d MT |
245 | |
246 | .. option:: --server=args | |
247 | ||
b034c0dd TK |
248 | Start a backend server, with `args` specifying what to listen to. |
249 | See `Client/Server`_ section. | |
f80dba8d MT |
250 | |
251 | .. option:: --daemonize=pidfile | |
252 | ||
b034c0dd | 253 | Background a fio server, writing the pid to the given `pidfile` file. |
f80dba8d MT |
254 | |
255 | .. option:: --client=hostname | |
256 | ||
f50fbdda | 257 | Instead of running the jobs locally, send and run them on the given `hostname` |
71aa48eb | 258 | or set of `hostname`\s. See `Client/Server`_ section. |
f80dba8d MT |
259 | |
260 | .. option:: --remote-config=file | |
261 | ||
f50fbdda | 262 | Tell fio server to load this local `file`. |
f80dba8d MT |
263 | |
264 | .. option:: --idle-prof=option | |
265 | ||
b8f7e412 | 266 | Report CPU idleness. `option` is one of the following: |
113f0e7c SW |
267 | |
268 | **calibrate** | |
269 | Run unit work calibration only and exit. | |
270 | ||
271 | **system** | |
272 | Show aggregate system idleness and unit work. | |
273 | ||
274 | **percpu** | |
275 | As **system** but also show per CPU idleness. | |
f80dba8d MT |
276 | |
277 | .. option:: --inflate-log=log | |
278 | ||
f50fbdda | 279 | Inflate and output compressed `log`. |
f80dba8d MT |
280 | |
281 | .. option:: --trigger-file=file | |
282 | ||
f50fbdda | 283 | Execute trigger command when `file` exists. |
f80dba8d | 284 | |
f50fbdda | 285 | .. option:: --trigger-timeout=time |
f80dba8d | 286 | |
f50fbdda | 287 | Execute trigger at this `time`. |
f80dba8d | 288 | |
f50fbdda | 289 | .. option:: --trigger=command |
f80dba8d | 290 | |
f50fbdda | 291 | Set this `command` as local trigger. |
f80dba8d | 292 | |
f50fbdda | 293 | .. option:: --trigger-remote=command |
f80dba8d | 294 | |
f50fbdda | 295 | Set this `command` as remote trigger. |
f80dba8d MT |
296 | |
297 | .. option:: --aux-path=path | |
298 | ||
f4401bf8 SW |
299 | Use the directory specified by `path` for generated state files instead |
300 | of the current working directory. | |
f80dba8d MT |
301 | |
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. | |
306 | ||
307 | ||
308 | Job file format | |
309 | --------------- | |
310 | ||
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 | |
c60ebc45 | 313 | enclosed in [] brackets define the job name. You are free to use any ASCII name |
f80dba8d MT |
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. | |
318 | ||
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 | |
322 | residing above it. | |
323 | ||
f50fbdda TK |
324 | The :option:`--cmdhelp` option also lists all options. If used with a `command` |
325 | argument, :option:`--cmdhelp` will detail the given `command`. | |
f80dba8d MT |
326 | |
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. | |
329 | ||
330 | So let's look at a really simple job file that defines two processes, each | |
331 | randomly reading from a 128MiB file: | |
332 | ||
333 | .. code-block:: ini | |
334 | ||
335 | ; -- start job file -- | |
336 | [global] | |
337 | rw=randread | |
338 | size=128m | |
339 | ||
340 | [job1] | |
341 | ||
342 | [job2] | |
343 | ||
344 | ; -- end job file -- | |
345 | ||
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:: | |
350 | ||
351 | $ fio --name=global --rw=randread --size=128m --name=job1 --name=job2 | |
352 | ||
353 | ||
354 | Let's look at an example that has a number of processes writing randomly to | |
355 | files: | |
356 | ||
357 | .. code-block:: ini | |
358 | ||
359 | ; -- start job file -- | |
360 | [random-writers] | |
361 | ioengine=libaio | |
362 | iodepth=4 | |
363 | rw=randwrite | |
364 | bs=32k | |
365 | direct=0 | |
366 | size=64m | |
367 | numjobs=4 | |
368 | ; -- end job file -- | |
369 | ||
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:: | |
376 | ||
377 | $ fio --name=random-writers --ioengine=libaio --iodepth=4 --rw=randwrite --bs=32k --direct=0 --size=64m --numjobs=4 | |
378 | ||
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 | |
383 | example:: | |
384 | ||
385 | ; -- start job file including.fio -- | |
386 | [global] | |
387 | filename=/tmp/test | |
388 | filesize=1m | |
389 | include glob-include.fio | |
390 | ||
391 | [test] | |
392 | rw=randread | |
393 | bs=4k | |
394 | time_based=1 | |
395 | runtime=10 | |
396 | include test-include.fio | |
397 | ; -- end job file including.fio -- | |
398 | ||
399 | .. code-block:: ini | |
400 | ||
401 | ; -- start job file glob-include.fio -- | |
402 | thread=1 | |
403 | group_reporting=1 | |
404 | ; -- end job file glob-include.fio -- | |
405 | ||
406 | .. code-block:: ini | |
407 | ||
408 | ; -- start job file test-include.fio -- | |
409 | ioengine=libaio | |
410 | iodepth=4 | |
411 | ; -- end job file test-include.fio -- | |
412 | ||
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. | |
416 | ||
417 | ||
418 | Environment variables | |
419 | ~~~~~~~~~~~~~~~~~~~~~ | |
420 | ||
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. | |
426 | ||
427 | As an example, let's look at a sample fio invocation and job file:: | |
428 | ||
429 | $ SIZE=64m NUMJOBS=4 fio jobfile.fio | |
430 | ||
431 | .. code-block:: ini | |
432 | ||
433 | ; -- start job file -- | |
434 | [random-writers] | |
435 | rw=randwrite | |
436 | size=${SIZE} | |
437 | numjobs=${NUMJOBS} | |
438 | ; -- end job file -- | |
439 | ||
440 | This will expand to the following equivalent job file at runtime: | |
441 | ||
442 | .. code-block:: ini | |
443 | ||
444 | ; -- start job file -- | |
445 | [random-writers] | |
446 | rw=randwrite | |
447 | size=64m | |
448 | numjobs=4 | |
449 | ; -- end job file -- | |
450 | ||
451 | Fio ships with a few example job files, you can also look there for inspiration. | |
452 | ||
453 | Reserved keywords | |
454 | ~~~~~~~~~~~~~~~~~ | |
455 | ||
456 | Additionally, fio has a set of reserved keywords that will be replaced | |
457 | internally with the appropriate value. Those keywords are: | |
458 | ||
459 | **$pagesize** | |
460 | ||
461 | The architecture page size of the running system. | |
462 | ||
463 | **$mb_memory** | |
464 | ||
465 | Megabytes of total memory in the system. | |
466 | ||
467 | **$ncpus** | |
468 | ||
469 | Number of online available CPUs. | |
470 | ||
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 | |
474 | like:: | |
475 | ||
b034c0dd | 476 | size=8*$mb_memory |
f80dba8d MT |
477 | |
478 | and get that properly expanded to 8 times the size of memory in the machine. | |
479 | ||
480 | ||
481 | Job file parameters | |
482 | ------------------- | |
483 | ||
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: | |
488 | ||
489 | - addition (+) | |
490 | - subtraction (-) | |
491 | - multiplication (*) | |
492 | - division (/) | |
493 | - modulus (%) | |
494 | - exponentiation (^) | |
495 | ||
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: | |
499 | ||
500 | ||
501 | Parameter types | |
502 | ~~~~~~~~~~~~~~~ | |
503 | ||
504 | **str** | |
b034c0dd | 505 | String: A sequence of alphanumeric characters. |
f80dba8d MT |
506 | |
507 | **time** | |
008d0feb SW |
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. | |
f80dba8d MT |
512 | |
513 | .. _int: | |
514 | ||
515 | **int** | |
516 | Integer. A whole number value, which may contain an integer prefix | |
517 | and an integer suffix: | |
518 | ||
b034c0dd | 519 | [*integer prefix*] **number** [*integer suffix*] |
f80dba8d MT |
520 | |
521 | The optional *integer prefix* specifies the number's base. The default | |
522 | is decimal. *0x* specifies hexadecimal. | |
523 | ||
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 | |
947e0fe0 SW |
526 | default unit is bytes. For quantities of time, the default unit is seconds |
527 | unless otherwise specified. | |
f80dba8d | 528 | |
9207a0cb | 529 | With :option:`kb_base`\=1000, fio follows international standards for unit |
f80dba8d MT |
530 | prefixes. To specify power-of-10 decimal values defined in the |
531 | International System of Units (SI): | |
532 | ||
eccce61a TK |
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 | |
f80dba8d MT |
538 | |
539 | To specify power-of-2 binary values defined in IEC 80000-13: | |
540 | ||
eccce61a TK |
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 | |
f80dba8d | 546 | |
9207a0cb | 547 | With :option:`kb_base`\=1024 (the default), the unit prefixes are opposite |
f80dba8d MT |
548 | from those specified in the SI and IEC 80000-13 standards to provide |
549 | compatibility with old scripts. For example, 4k means 4096. | |
550 | ||
551 | For quantities of data, an optional unit of 'B' may be included | |
b8f7e412 | 552 | (e.g., 'kB' is the same as 'k'). |
f80dba8d MT |
553 | |
554 | The *integer suffix* is not case sensitive (e.g., m/mi mean mebi/mega, | |
555 | not milli). 'b' and 'B' both mean byte, not bit. | |
556 | ||
9207a0cb | 557 | Examples with :option:`kb_base`\=1000: |
f80dba8d MT |
558 | |
559 | * *4 KiB*: 4096, 4096b, 4096B, 4ki, 4kib, 4kiB, 4Ki, 4KiB | |
560 | * *1 MiB*: 1048576, 1mi, 1024ki | |
561 | * *1 MB*: 1000000, 1m, 1000k | |
562 | * *1 TiB*: 1099511627776, 1ti, 1024gi, 1048576mi | |
563 | * *1 TB*: 1000000000, 1t, 1000m, 1000000k | |
564 | ||
9207a0cb | 565 | Examples with :option:`kb_base`\=1024 (default): |
f80dba8d MT |
566 | |
567 | * *4 KiB*: 4096, 4096b, 4096B, 4k, 4kb, 4kB, 4K, 4KB | |
568 | * *1 MiB*: 1048576, 1m, 1024k | |
569 | * *1 MB*: 1000000, 1mi, 1000ki | |
570 | * *1 TiB*: 1099511627776, 1t, 1024g, 1048576m | |
571 | * *1 TB*: 1000000000, 1ti, 1000mi, 1000000ki | |
572 | ||
573 | To specify times (units are not case sensitive): | |
574 | ||
575 | * *D* -- means days | |
576 | * *H* -- means hours | |
4502cb42 | 577 | * *M* -- means minutes |
f80dba8d MT |
578 | * *s* -- or sec means seconds (default) |
579 | * *ms* -- or *msec* means milliseconds | |
580 | * *us* -- or *usec* means microseconds | |
581 | ||
582 | If the option accepts an upper and lower range, use a colon ':' or | |
583 | minus '-' to separate such values. See :ref:`irange <irange>`. | |
4502cb42 SW |
584 | If the lower value specified happens to be larger than the upper value |
585 | the two values are swapped. | |
f80dba8d MT |
586 | |
587 | .. _bool: | |
588 | ||
589 | **bool** | |
590 | Boolean. Usually parsed as an integer, however only defined for | |
591 | true and false (1 and 0). | |
592 | ||
593 | .. _irange: | |
594 | ||
595 | **irange** | |
596 | Integer range with suffix. Allows value range to be given, such as | |
c60ebc45 | 597 | 1024-4096. A colon may also be used as the separator, e.g. 1k:4k. If the |
f80dba8d MT |
598 | option allows two sets of ranges, they can be specified with a ',' or '/' |
599 | delimiter: 1k-4k/8k-32k. Also see :ref:`int <int>`. | |
600 | ||
601 | **float_list** | |
602 | A list of floating point numbers, separated by a ':' character. | |
603 | ||
f5c3bcf2 TK |
604 | With the above in mind, here follows the complete list of fio job parameters. |
605 | ||
f80dba8d MT |
606 | |
607 | Units | |
608 | ~~~~~ | |
609 | ||
610 | .. option:: kb_base=int | |
611 | ||
612 | Select the interpretation of unit prefixes in input parameters. | |
613 | ||
614 | **1000** | |
615 | Inputs comply with IEC 80000-13 and the International | |
616 | System of Units (SI). Use: | |
617 | ||
618 | - power-of-2 values with IEC prefixes (e.g., KiB) | |
619 | - power-of-10 values with SI prefixes (e.g., kB) | |
620 | ||
621 | **1024** | |
622 | Compatibility mode (default). To avoid breaking old scripts: | |
623 | ||
624 | - power-of-2 values with SI prefixes | |
625 | - power-of-10 values with IEC prefixes | |
626 | ||
627 | See :option:`bs` for more details on input parameters. | |
628 | ||
629 | Outputs always use correct prefixes. Most outputs include both | |
630 | side-by-side, like:: | |
631 | ||
632 | bw=2383.3kB/s (2327.4KiB/s) | |
633 | ||
634 | If only one value is reported, then kb_base selects the one to use: | |
635 | ||
636 | **1000** -- SI prefixes | |
637 | ||
638 | **1024** -- IEC prefixes | |
639 | ||
640 | .. option:: unit_base=int | |
641 | ||
642 | Base unit for reporting. Allowed values are: | |
643 | ||
644 | **0** | |
645 | Use auto-detection (default). | |
646 | **8** | |
647 | Byte based. | |
648 | **1** | |
649 | Bit based. | |
650 | ||
651 | ||
f80dba8d MT |
652 | Job description |
653 | ~~~~~~~~~~~~~~~ | |
654 | ||
655 | .. option:: name=str | |
656 | ||
657 | ASCII name of the job. This may be used to override the name printed by fio | |
658 | for this job. Otherwise the job name is used. On the command line this | |
659 | parameter has the special purpose of also signaling the start of a new job. | |
660 | ||
661 | .. option:: description=str | |
662 | ||
663 | Text description of the job. Doesn't do anything except dump this text | |
664 | description when this job is run. It's not parsed. | |
665 | ||
666 | .. option:: loops=int | |
667 | ||
668 | Run the specified number of iterations of this job. Used to repeat the same | |
669 | workload a given number of times. Defaults to 1. | |
670 | ||
671 | .. option:: numjobs=int | |
672 | ||
79591fa9 TK |
673 | Create the specified number of clones of this job. Each clone of job |
674 | is spawned as an independent thread or process. May be used to setup a | |
f80dba8d MT |
675 | larger number of threads/processes doing the same thing. Each thread is |
676 | reported separately; to see statistics for all clones as a whole, use | |
677 | :option:`group_reporting` in conjunction with :option:`new_group`. | |
a47b697c | 678 | See :option:`--max-jobs`. Default: 1. |
f80dba8d MT |
679 | |
680 | ||
681 | Time related parameters | |
682 | ~~~~~~~~~~~~~~~~~~~~~~~ | |
683 | ||
684 | .. option:: runtime=time | |
685 | ||
f75ede1d | 686 | Tell fio to terminate processing after the specified period of time. It |
f80dba8d | 687 | can be quite hard to determine for how long a specified job will run, so |
f75ede1d | 688 | this parameter is handy to cap the total runtime to a given time. When |
804c0839 | 689 | the unit is omitted, the value is interpreted in seconds. |
f80dba8d MT |
690 | |
691 | .. option:: time_based | |
692 | ||
693 | If set, fio will run for the duration of the :option:`runtime` specified | |
694 | even if the file(s) are completely read or written. It will simply loop over | |
695 | the same workload as many times as the :option:`runtime` allows. | |
696 | ||
a881438b | 697 | .. option:: startdelay=irange(time) |
f80dba8d | 698 | |
947e0fe0 SW |
699 | Delay the start of job for the specified amount of time. Can be a single |
700 | value or a range. When given as a range, each thread will choose a value | |
701 | randomly from within the range. Value is in seconds if a unit is omitted. | |
f80dba8d MT |
702 | |
703 | .. option:: ramp_time=time | |
704 | ||
705 | If set, fio will run the specified workload for this amount of time before | |
706 | logging any performance numbers. Useful for letting performance settle | |
707 | before logging results, thus minimizing the runtime required for stable | |
708 | results. Note that the ``ramp_time`` is considered lead in time for a job, | |
709 | thus it will increase the total runtime if a special timeout or | |
f75ede1d SW |
710 | :option:`runtime` is specified. When the unit is omitted, the value is |
711 | given in seconds. | |
f80dba8d MT |
712 | |
713 | .. option:: clocksource=str | |
714 | ||
715 | Use the given clocksource as the base of timing. The supported options are: | |
716 | ||
717 | **gettimeofday** | |
718 | :manpage:`gettimeofday(2)` | |
719 | ||
720 | **clock_gettime** | |
721 | :manpage:`clock_gettime(2)` | |
722 | ||
723 | **cpu** | |
724 | Internal CPU clock source | |
725 | ||
726 | cpu is the preferred clocksource if it is reliable, as it is very fast (and | |
727 | fio is heavy on time calls). Fio will automatically use this clocksource if | |
728 | it's supported and considered reliable on the system it is running on, | |
729 | unless another clocksource is specifically set. For x86/x86-64 CPUs, this | |
730 | means supporting TSC Invariant. | |
731 | ||
732 | .. option:: gtod_reduce=bool | |
733 | ||
734 | Enable all of the :manpage:`gettimeofday(2)` reducing options | |
f75ede1d | 735 | (:option:`disable_clat`, :option:`disable_slat`, :option:`disable_bw_measurement`) plus |
f80dba8d MT |
736 | reduce precision of the timeout somewhat to really shrink the |
737 | :manpage:`gettimeofday(2)` call count. With this option enabled, we only do | |
738 | about 0.4% of the :manpage:`gettimeofday(2)` calls we would have done if all | |
739 | time keeping was enabled. | |
740 | ||
741 | .. option:: gtod_cpu=int | |
742 | ||
743 | Sometimes it's cheaper to dedicate a single thread of execution to just | |
744 | getting the current time. Fio (and databases, for instance) are very | |
745 | intensive on :manpage:`gettimeofday(2)` calls. With this option, you can set | |
746 | one CPU aside for doing nothing but logging current time to a shared memory | |
747 | location. Then the other threads/processes that run I/O workloads need only | |
748 | copy that segment, instead of entering the kernel with a | |
749 | :manpage:`gettimeofday(2)` call. The CPU set aside for doing these time | |
750 | calls will be excluded from other uses. Fio will manually clear it from the | |
751 | CPU mask of other jobs. | |
752 | ||
753 | ||
754 | Target file/device | |
755 | ~~~~~~~~~~~~~~~~~~ | |
756 | ||
757 | .. option:: directory=str | |
758 | ||
759 | Prefix filenames with this directory. Used to place files in a different | |
760 | location than :file:`./`. You can specify a number of directories by | |
761 | separating the names with a ':' character. These directories will be | |
02dd2689 | 762 | assigned equally distributed to job clones created by :option:`numjobs` as |
f80dba8d MT |
763 | long as they are using generated filenames. If specific `filename(s)` are |
764 | set fio will use the first listed directory, and thereby matching the | |
f4401bf8 SW |
765 | `filename` semantic (which generates a file for each clone if not |
766 | specified, but lets all clones use the same file if set). | |
f80dba8d | 767 | |
3b803fe1 SW |
768 | See the :option:`filename` option for information on how to escape "``:``" |
769 | characters within the directory path itself. | |
f80dba8d | 770 | |
f4401bf8 SW |
771 | Note: To control the directory fio will use for internal state files |
772 | use :option:`--aux-path`. | |
773 | ||
f80dba8d MT |
774 | .. option:: filename=str |
775 | ||
776 | Fio normally makes up a `filename` based on the job name, thread number, and | |
02dd2689 SW |
777 | file number (see :option:`filename_format`). If you want to share files |
778 | between threads in a job or several | |
79591fa9 TK |
779 | jobs with fixed file paths, specify a `filename` for each of them to override |
780 | the default. If the ioengine is file based, you can specify a number of files | |
781 | by separating the names with a ':' colon. So if you wanted a job to open | |
782 | :file:`/dev/sda` and :file:`/dev/sdb` as the two working files, you would use | |
783 | ``filename=/dev/sda:/dev/sdb``. This also means that whenever this option is | |
784 | specified, :option:`nrfiles` is ignored. The size of regular files specified | |
02dd2689 | 785 | by this option will be :option:`size` divided by number of files unless an |
79591fa9 TK |
786 | explicit size is specified by :option:`filesize`. |
787 | ||
3b803fe1 | 788 | Each colon in the wanted path must be escaped with a ``\`` |
02dd2689 SW |
789 | character. For instance, if the path is :file:`/dev/dsk/foo@3,0:c` then you |
790 | would use ``filename=/dev/dsk/foo@3,0\:c`` and if the path is | |
3b803fe1 | 791 | :file:`F:\\filename` then you would use ``filename=F\:\filename``. |
02dd2689 | 792 | |
f80dba8d MT |
793 | On Windows, disk devices are accessed as :file:`\\\\.\\PhysicalDrive0` for |
794 | the first device, :file:`\\\\.\\PhysicalDrive1` for the second etc. | |
795 | Note: Windows and FreeBSD prevent write access to areas | |
02dd2689 SW |
796 | of the disk containing in-use data (e.g. filesystems). |
797 | ||
798 | The filename "`-`" is a reserved name, meaning *stdin* or *stdout*. Which | |
799 | of the two depends on the read/write direction set. | |
f80dba8d MT |
800 | |
801 | .. option:: filename_format=str | |
802 | ||
803 | If sharing multiple files between jobs, it is usually necessary to have fio | |
804 | generate the exact names that you want. By default, fio will name a file | |
805 | based on the default file format specification of | |
806 | :file:`jobname.jobnumber.filenumber`. With this option, that can be | |
807 | customized. Fio will recognize and replace the following keywords in this | |
808 | string: | |
809 | ||
810 | **$jobname** | |
811 | The name of the worker thread or process. | |
812 | **$jobnum** | |
813 | The incremental number of the worker thread or process. | |
814 | **$filenum** | |
815 | The incremental number of the file for that worker thread or | |
816 | process. | |
817 | ||
818 | To have dependent jobs share a set of files, this option can be set to have | |
819 | fio generate filenames that are shared between the two. For instance, if | |
820 | :file:`testfiles.$filenum` is specified, file number 4 for any job will be | |
821 | named :file:`testfiles.4`. The default of :file:`$jobname.$jobnum.$filenum` | |
822 | will be used if no other format specifier is given. | |
823 | ||
645943c0 JB |
824 | If you specify a path then the directories will be created up to the |
825 | main directory for the file. So for example if you specify | |
826 | ``filename_format=a/b/c/$jobnum`` then the directories a/b/c will be | |
827 | created before the file setup part of the job. If you specify | |
828 | :option:`directory` then the path will be relative that directory, | |
829 | otherwise it is treated as the absolute path. | |
830 | ||
f80dba8d MT |
831 | .. option:: unique_filename=bool |
832 | ||
833 | To avoid collisions between networked clients, fio defaults to prefixing any | |
834 | generated filenames (with a directory specified) with the source of the | |
835 | client connecting. To disable this behavior, set this option to 0. | |
836 | ||
837 | .. option:: opendir=str | |
838 | ||
839 | Recursively open any files below directory `str`. | |
840 | ||
841 | .. option:: lockfile=str | |
842 | ||
843 | Fio defaults to not locking any files before it does I/O to them. If a file | |
844 | or file descriptor is shared, fio can serialize I/O to that file to make the | |
845 | end result consistent. This is usual for emulating real workloads that share | |
846 | files. The lock modes are: | |
847 | ||
848 | **none** | |
849 | No locking. The default. | |
850 | **exclusive** | |
851 | Only one thread or process may do I/O at a time, excluding all | |
852 | others. | |
853 | **readwrite** | |
854 | Read-write locking on the file. Many readers may | |
855 | access the file at the same time, but writes get exclusive access. | |
856 | ||
857 | .. option:: nrfiles=int | |
858 | ||
79591fa9 TK |
859 | Number of files to use for this job. Defaults to 1. The size of files |
860 | will be :option:`size` divided by this unless explicit size is specified by | |
861 | :option:`filesize`. Files are created for each thread separately, and each | |
862 | file will have a file number within its name by default, as explained in | |
863 | :option:`filename` section. | |
864 | ||
f80dba8d MT |
865 | |
866 | .. option:: openfiles=int | |
867 | ||
868 | Number of files to keep open at the same time. Defaults to the same as | |
869 | :option:`nrfiles`, can be set smaller to limit the number simultaneous | |
870 | opens. | |
871 | ||
872 | .. option:: file_service_type=str | |
873 | ||
874 | Defines how fio decides which file from a job to service next. The following | |
875 | types are defined: | |
876 | ||
877 | **random** | |
878 | Choose a file at random. | |
879 | ||
880 | **roundrobin** | |
881 | Round robin over opened files. This is the default. | |
882 | ||
883 | **sequential** | |
884 | Finish one file before moving on to the next. Multiple files can | |
f50fbdda | 885 | still be open depending on :option:`openfiles`. |
f80dba8d MT |
886 | |
887 | **zipf** | |
c60ebc45 | 888 | Use a *Zipf* distribution to decide what file to access. |
f80dba8d MT |
889 | |
890 | **pareto** | |
c60ebc45 | 891 | Use a *Pareto* distribution to decide what file to access. |
f80dba8d | 892 | |
dd3503d3 | 893 | **normal** |
c60ebc45 | 894 | Use a *Gaussian* (normal) distribution to decide what file to |
f80dba8d MT |
895 | access. |
896 | ||
dd3503d3 SW |
897 | **gauss** |
898 | Alias for normal. | |
899 | ||
f80dba8d MT |
900 | For *random*, *roundrobin*, and *sequential*, a postfix can be appended to |
901 | tell fio how many I/Os to issue before switching to a new file. For example, | |
902 | specifying ``file_service_type=random:8`` would cause fio to issue | |
903 | 8 I/Os before selecting a new file at random. For the non-uniform | |
904 | distributions, a floating point postfix can be given to influence how the | |
905 | distribution is skewed. See :option:`random_distribution` for a description | |
906 | of how that would work. | |
907 | ||
908 | .. option:: ioscheduler=str | |
909 | ||
910 | Attempt to switch the device hosting the file to the specified I/O scheduler | |
911 | before running. | |
912 | ||
913 | .. option:: create_serialize=bool | |
914 | ||
915 | If true, serialize the file creation for the jobs. This may be handy to | |
916 | avoid interleaving of data files, which may greatly depend on the filesystem | |
a47b697c | 917 | used and even the number of processors in the system. Default: true. |
f80dba8d MT |
918 | |
919 | .. option:: create_fsync=bool | |
920 | ||
22413915 | 921 | :manpage:`fsync(2)` the data file after creation. This is the default. |
f80dba8d MT |
922 | |
923 | .. option:: create_on_open=bool | |
924 | ||
730bd7d9 SW |
925 | If true, don't pre-create files but allow the job's open() to create a file |
926 | when it's time to do I/O. Default: false -- pre-create all necessary files | |
927 | when the job starts. | |
f80dba8d MT |
928 | |
929 | .. option:: create_only=bool | |
930 | ||
931 | If true, fio will only run the setup phase of the job. If files need to be | |
4502cb42 | 932 | laid out or updated on disk, only that will be done -- the actual job contents |
a47b697c | 933 | are not executed. Default: false. |
f80dba8d MT |
934 | |
935 | .. option:: allow_file_create=bool | |
936 | ||
730bd7d9 SW |
937 | If true, fio is permitted to create files as part of its workload. If this |
938 | option is false, then fio will error out if | |
f80dba8d MT |
939 | the files it needs to use don't already exist. Default: true. |
940 | ||
941 | .. option:: allow_mounted_write=bool | |
942 | ||
c60ebc45 | 943 | If this isn't set, fio will abort jobs that are destructive (e.g. that write) |
f80dba8d MT |
944 | to what appears to be a mounted device or partition. This should help catch |
945 | creating inadvertently destructive tests, not realizing that the test will | |
b1db0375 TK |
946 | destroy data on the mounted file system. Note that some platforms don't allow |
947 | writing against a mounted device regardless of this option. Default: false. | |
f80dba8d MT |
948 | |
949 | .. option:: pre_read=bool | |
950 | ||
951 | If this is given, files will be pre-read into memory before starting the | |
952 | given I/O operation. This will also clear the :option:`invalidate` flag, | |
953 | since it is pointless to pre-read and then drop the cache. This will only | |
954 | work for I/O engines that are seek-able, since they allow you to read the | |
a47b697c SW |
955 | same data multiple times. Thus it will not work on non-seekable I/O engines |
956 | (e.g. network, splice). Default: false. | |
f80dba8d MT |
957 | |
958 | .. option:: unlink=bool | |
959 | ||
960 | Unlink the job files when done. Not the default, as repeated runs of that | |
a47b697c SW |
961 | job would then waste time recreating the file set again and again. Default: |
962 | false. | |
f80dba8d MT |
963 | |
964 | .. option:: unlink_each_loop=bool | |
965 | ||
a47b697c | 966 | Unlink job files after each iteration or loop. Default: false. |
f80dba8d | 967 | |
7b865a2f BVA |
968 | .. option:: zonemode=str |
969 | ||
970 | Accepted values are: | |
971 | ||
972 | **none** | |
b8dd9750 HH |
973 | The :option:`zonerange`, :option:`zonesize`, |
974 | :option `zonecapacity` and option:`zoneskip` | |
975 | parameters are ignored. | |
7b865a2f BVA |
976 | **strided** |
977 | I/O happens in a single zone until | |
978 | :option:`zonesize` bytes have been transferred. | |
979 | After that number of bytes has been | |
980 | transferred processing of the next zone | |
b8dd9750 | 981 | starts. :option `zonecapacity` is ignored. |
7b865a2f BVA |
982 | **zbd** |
983 | Zoned block device mode. I/O happens | |
984 | sequentially in each zone, even if random I/O | |
985 | has been selected. Random I/O happens across | |
986 | all zones instead of being restricted to a | |
987 | single zone. The :option:`zoneskip` parameter | |
988 | is ignored. :option:`zonerange` and | |
989 | :option:`zonesize` must be identical. | |
990 | ||
5faddc64 | 991 | .. option:: zonerange=int |
f80dba8d | 992 | |
7b865a2f BVA |
993 | Size of a single zone. See also :option:`zonesize` and |
994 | :option:`zoneskip`. | |
f80dba8d | 995 | |
5faddc64 | 996 | .. option:: zonesize=int |
f80dba8d | 997 | |
7b865a2f BVA |
998 | For :option:`zonemode` =strided, this is the number of bytes to |
999 | transfer before skipping :option:`zoneskip` bytes. If this parameter | |
1000 | is smaller than :option:`zonerange` then only a fraction of each zone | |
1001 | with :option:`zonerange` bytes will be accessed. If this parameter is | |
1002 | larger than :option:`zonerange` then each zone will be accessed | |
1003 | multiple times before skipping to the next zone. | |
1004 | ||
1005 | For :option:`zonemode` =zbd, this is the size of a single zone. The | |
1006 | :option:`zonerange` parameter is ignored in this mode. | |
f80dba8d | 1007 | |
b8dd9750 HH |
1008 | |
1009 | .. option:: zonecapacity=int | |
1010 | ||
1011 | For :option:`zonemode` =zbd, this defines the capacity of a single zone, | |
1012 | which is the accessible area starting from the zone start address. | |
1013 | This parameter only applies when using :option:`zonemode` =zbd in | |
1014 | combination with regular block devices. If not specified it defaults to | |
1015 | the zone size. If the target device is a zoned block device, the zone | |
1016 | capacity is obtained from the device information and this option is | |
1017 | ignored. | |
1018 | ||
f80dba8d MT |
1019 | .. option:: zoneskip=int |
1020 | ||
7b865a2f BVA |
1021 | For :option:`zonemode` =strided, the number of bytes to skip after |
1022 | :option:`zonesize` bytes of data have been transferred. This parameter | |
1023 | must be zero for :option:`zonemode` =zbd. | |
f80dba8d | 1024 | |
bfbdd35b BVA |
1025 | .. option:: read_beyond_wp=bool |
1026 | ||
1027 | This parameter applies to :option:`zonemode` =zbd only. | |
1028 | ||
1029 | Zoned block devices are block devices that consist of multiple zones. | |
1030 | Each zone has a type, e.g. conventional or sequential. A conventional | |
1031 | zone can be written at any offset that is a multiple of the block | |
1032 | size. Sequential zones must be written sequentially. The position at | |
1033 | which a write must occur is called the write pointer. A zoned block | |
1034 | device can be either drive managed, host managed or host aware. For | |
1035 | host managed devices the host must ensure that writes happen | |
1036 | sequentially. Fio recognizes host managed devices and serializes | |
1037 | writes to sequential zones for these devices. | |
1038 | ||
1039 | If a read occurs in a sequential zone beyond the write pointer then | |
1040 | the zoned block device will complete the read without reading any data | |
1041 | from the storage medium. Since such reads lead to unrealistically high | |
1042 | bandwidth and IOPS numbers fio only reads beyond the write pointer if | |
1043 | explicitly told to do so. Default: false. | |
1044 | ||
59b07544 BVA |
1045 | .. option:: max_open_zones=int |
1046 | ||
1047 | When running a random write test across an entire drive many more | |
1048 | zones will be open than in a typical application workload. Hence this | |
1049 | command line option that allows to limit the number of open zones. The | |
1050 | number of open zones is defined as the number of zones to which write | |
1051 | commands are issued. | |
1052 | ||
a7c2b6fc BVA |
1053 | .. option:: zone_reset_threshold=float |
1054 | ||
1055 | A number between zero and one that indicates the ratio of logical | |
1056 | blocks with data to the total number of logical blocks in the test | |
1057 | above which zones should be reset periodically. | |
1058 | ||
1059 | .. option:: zone_reset_frequency=float | |
1060 | ||
1061 | A number between zero and one that indicates how often a zone reset | |
1062 | should be issued if the zone reset threshold has been exceeded. A zone | |
1063 | reset is submitted after each (1 / zone_reset_frequency) write | |
1064 | requests. This and the previous parameter can be used to simulate | |
1065 | garbage collection activity. | |
1066 | ||
f80dba8d MT |
1067 | |
1068 | I/O type | |
1069 | ~~~~~~~~ | |
1070 | ||
1071 | .. option:: direct=bool | |
1072 | ||
1073 | If value is true, use non-buffered I/O. This is usually O_DIRECT. Note that | |
8e889110 | 1074 | OpenBSD and ZFS on Solaris don't support direct I/O. On Windows the synchronous |
f80dba8d MT |
1075 | ioengines don't support direct I/O. Default: false. |
1076 | ||
1077 | .. option:: atomic=bool | |
1078 | ||
1079 | If value is true, attempt to use atomic direct I/O. Atomic writes are | |
1080 | guaranteed to be stable once acknowledged by the operating system. Only | |
1081 | Linux supports O_ATOMIC right now. | |
1082 | ||
1083 | .. option:: buffered=bool | |
1084 | ||
1085 | If value is true, use buffered I/O. This is the opposite of the | |
1086 | :option:`direct` option. Defaults to true. | |
1087 | ||
1088 | .. option:: readwrite=str, rw=str | |
1089 | ||
1090 | Type of I/O pattern. Accepted values are: | |
1091 | ||
1092 | **read** | |
1093 | Sequential reads. | |
1094 | **write** | |
1095 | Sequential writes. | |
1096 | **trim** | |
3740cfc8 VF |
1097 | Sequential trims (Linux block devices and SCSI |
1098 | character devices only). | |
f80dba8d MT |
1099 | **randread** |
1100 | Random reads. | |
2831be97 SW |
1101 | **randwrite** |
1102 | Random writes. | |
f80dba8d | 1103 | **randtrim** |
3740cfc8 VF |
1104 | Random trims (Linux block devices and SCSI |
1105 | character devices only). | |
f80dba8d MT |
1106 | **rw,readwrite** |
1107 | Sequential mixed reads and writes. | |
1108 | **randrw** | |
1109 | Random mixed reads and writes. | |
1110 | **trimwrite** | |
1111 | Sequential trim+write sequences. Blocks will be trimmed first, | |
1112 | then the same blocks will be written to. | |
1113 | ||
1114 | Fio defaults to read if the option is not specified. For the mixed I/O | |
1115 | types, the default is to split them 50/50. For certain types of I/O the | |
730bd7d9 SW |
1116 | result may still be skewed a bit, since the speed may be different. |
1117 | ||
1118 | It is possible to specify the number of I/Os to do before getting a new | |
1119 | offset by appending ``:<nr>`` to the end of the string given. For a | |
f80dba8d MT |
1120 | random read, it would look like ``rw=randread:8`` for passing in an offset |
1121 | modifier with a value of 8. If the suffix is used with a sequential I/O | |
730bd7d9 SW |
1122 | pattern, then the *<nr>* value specified will be **added** to the generated |
1123 | offset for each I/O turning sequential I/O into sequential I/O with holes. | |
1124 | For instance, using ``rw=write:4k`` will skip 4k for every write. Also see | |
1125 | the :option:`rw_sequencer` option. | |
f80dba8d MT |
1126 | |
1127 | .. option:: rw_sequencer=str | |
1128 | ||
1129 | If an offset modifier is given by appending a number to the ``rw=<str>`` | |
1130 | line, then this option controls how that number modifies the I/O offset | |
1131 | being generated. Accepted values are: | |
1132 | ||
1133 | **sequential** | |
1134 | Generate sequential offset. | |
1135 | **identical** | |
1136 | Generate the same offset. | |
1137 | ||
1138 | ``sequential`` is only useful for random I/O, where fio would normally | |
c60ebc45 | 1139 | generate a new random offset for every I/O. If you append e.g. 8 to randread, |
007c7be9 SW |
1140 | you would get a new random offset for every 8 I/Os. The result would be a |
1141 | seek for only every 8 I/Os, instead of for every I/O. Use ``rw=randread:8`` | |
f80dba8d MT |
1142 | to specify that. As sequential I/O is already sequential, setting |
1143 | ``sequential`` for that would not result in any differences. ``identical`` | |
1144 | behaves in a similar fashion, except it sends the same offset 8 number of | |
1145 | times before generating a new offset. | |
1146 | ||
1147 | .. option:: unified_rw_reporting=bool | |
1148 | ||
1149 | Fio normally reports statistics on a per data direction basis, meaning that | |
1150 | reads, writes, and trims are accounted and reported separately. If this | |
1151 | option is set fio sums the results and report them as "mixed" instead. | |
1152 | ||
1153 | .. option:: randrepeat=bool | |
1154 | ||
1155 | Seed the random number generator used for random I/O patterns in a | |
1156 | predictable way so the pattern is repeatable across runs. Default: true. | |
1157 | ||
1158 | .. option:: allrandrepeat=bool | |
1159 | ||
1160 | Seed all random number generators in a predictable way so results are | |
1161 | repeatable across runs. Default: false. | |
1162 | ||
1163 | .. option:: randseed=int | |
1164 | ||
1165 | Seed the random number generators based on this seed value, to be able to | |
1166 | control what sequence of output is being generated. If not set, the random | |
1167 | sequence depends on the :option:`randrepeat` setting. | |
1168 | ||
1169 | .. option:: fallocate=str | |
1170 | ||
1171 | Whether pre-allocation is performed when laying down files. | |
1172 | Accepted values are: | |
1173 | ||
1174 | **none** | |
1175 | Do not pre-allocate space. | |
1176 | ||
2c3e17be SW |
1177 | **native** |
1178 | Use a platform's native pre-allocation call but fall back to | |
1179 | **none** behavior if it fails/is not implemented. | |
1180 | ||
f80dba8d MT |
1181 | **posix** |
1182 | Pre-allocate via :manpage:`posix_fallocate(3)`. | |
1183 | ||
1184 | **keep** | |
1185 | Pre-allocate via :manpage:`fallocate(2)` with | |
1186 | FALLOC_FL_KEEP_SIZE set. | |
1187 | ||
38ca5f03 TV |
1188 | **truncate** |
1189 | Extend file to final size via :manpage:`ftruncate(2)` | |
1190 | instead of allocating. | |
1191 | ||
f80dba8d MT |
1192 | **0** |
1193 | Backward-compatible alias for **none**. | |
1194 | ||
1195 | **1** | |
1196 | Backward-compatible alias for **posix**. | |
1197 | ||
1198 | May not be available on all supported platforms. **keep** is only available | |
2c3e17be SW |
1199 | on Linux. If using ZFS on Solaris this cannot be set to **posix** |
1200 | because ZFS doesn't support pre-allocation. Default: **native** if any | |
38ca5f03 TV |
1201 | pre-allocation methods except **truncate** are available, **none** if not. |
1202 | ||
1203 | Note that using **truncate** on Windows will interact surprisingly | |
1204 | with non-sequential write patterns. When writing to a file that has | |
1205 | been extended by setting the end-of-file information, Windows will | |
1206 | backfill the unwritten portion of the file up to that offset with | |
1207 | zeroes before issuing the new write. This means that a single small | |
1208 | write to the end of an extended file will stall until the entire | |
1209 | file has been filled with zeroes. | |
f80dba8d MT |
1210 | |
1211 | .. option:: fadvise_hint=str | |
1212 | ||
c712c97a JA |
1213 | Use :manpage:`posix_fadvise(2)` or :manpage:`posix_fadvise(2)` to |
1214 | advise the kernel on what I/O patterns are likely to be issued. | |
1215 | Accepted values are: | |
f80dba8d MT |
1216 | |
1217 | **0** | |
1218 | Backwards-compatible hint for "no hint". | |
1219 | ||
1220 | **1** | |
1221 | Backwards compatible hint for "advise with fio workload type". This | |
1222 | uses **FADV_RANDOM** for a random workload, and **FADV_SEQUENTIAL** | |
1223 | for a sequential workload. | |
1224 | ||
1225 | **sequential** | |
1226 | Advise using **FADV_SEQUENTIAL**. | |
1227 | ||
1228 | **random** | |
1229 | Advise using **FADV_RANDOM**. | |
1230 | ||
8f4b9f24 | 1231 | .. option:: write_hint=str |
f80dba8d | 1232 | |
8f4b9f24 JA |
1233 | Use :manpage:`fcntl(2)` to advise the kernel what life time to expect |
1234 | from a write. Only supported on Linux, as of version 4.13. Accepted | |
1235 | values are: | |
1236 | ||
1237 | **none** | |
1238 | No particular life time associated with this file. | |
1239 | ||
1240 | **short** | |
1241 | Data written to this file has a short life time. | |
1242 | ||
1243 | **medium** | |
1244 | Data written to this file has a medium life time. | |
1245 | ||
1246 | **long** | |
1247 | Data written to this file has a long life time. | |
1248 | ||
1249 | **extreme** | |
1250 | Data written to this file has a very long life time. | |
1251 | ||
1252 | The values are all relative to each other, and no absolute meaning | |
1253 | should be associated with them. | |
f80dba8d MT |
1254 | |
1255 | .. option:: offset=int | |
1256 | ||
82dbb8cb | 1257 | Start I/O at the provided offset in the file, given as either a fixed size in |
83c8b093 JF |
1258 | bytes or a percentage. If a percentage is given, the generated offset will be |
1259 | aligned to the minimum ``blocksize`` or to the value of ``offset_align`` if | |
1260 | provided. Data before the given offset will not be touched. This | |
89978a6b BW |
1261 | effectively caps the file size at `real_size - offset`. Can be combined with |
1262 | :option:`size` to constrain the start and end range of the I/O workload. | |
44bb1142 TK |
1263 | A percentage can be specified by a number between 1 and 100 followed by '%', |
1264 | for example, ``offset=20%`` to specify 20%. | |
f80dba8d | 1265 | |
83c8b093 JF |
1266 | .. option:: offset_align=int |
1267 | ||
1268 | If set to non-zero value, the byte offset generated by a percentage ``offset`` | |
1269 | is aligned upwards to this value. Defaults to 0 meaning that a percentage | |
1270 | offset is aligned to the minimum block size. | |
1271 | ||
f80dba8d MT |
1272 | .. option:: offset_increment=int |
1273 | ||
1274 | If this is provided, then the real offset becomes `offset + offset_increment | |
1275 | * thread_number`, where the thread number is a counter that starts at 0 and | |
1276 | is incremented for each sub-job (i.e. when :option:`numjobs` option is | |
1277 | specified). This option is useful if there are several jobs which are | |
1278 | intended to operate on a file in parallel disjoint segments, with even | |
0b288ba1 VF |
1279 | spacing between the starting points. Percentages can be used for this option. |
1280 | If a percentage is given, the generated offset will be aligned to the minimum | |
1281 | ``blocksize`` or to the value of ``offset_align`` if provided. | |
f80dba8d MT |
1282 | |
1283 | .. option:: number_ios=int | |
1284 | ||
c60ebc45 | 1285 | Fio will normally perform I/Os until it has exhausted the size of the region |
f80dba8d MT |
1286 | set by :option:`size`, or if it exhaust the allocated time (or hits an error |
1287 | condition). With this setting, the range/size can be set independently of | |
c60ebc45 | 1288 | the number of I/Os to perform. When fio reaches this number, it will exit |
f80dba8d MT |
1289 | normally and report status. Note that this does not extend the amount of I/O |
1290 | that will be done, it will only stop fio if this condition is met before | |
1291 | other end-of-job criteria. | |
1292 | ||
1293 | .. option:: fsync=int | |
1294 | ||
730bd7d9 SW |
1295 | If writing to a file, issue an :manpage:`fsync(2)` (or its equivalent) of |
1296 | the dirty data for every number of blocks given. For example, if you give 32 | |
1297 | as a parameter, fio will sync the file after every 32 writes issued. If fio is | |
1298 | using non-buffered I/O, we may not sync the file. The exception is the sg | |
1299 | I/O engine, which synchronizes the disk cache anyway. Defaults to 0, which | |
1300 | means fio does not periodically issue and wait for a sync to complete. Also | |
1301 | see :option:`end_fsync` and :option:`fsync_on_close`. | |
f80dba8d MT |
1302 | |
1303 | .. option:: fdatasync=int | |
1304 | ||
1305 | Like :option:`fsync` but uses :manpage:`fdatasync(2)` to only sync data and | |
44f668d7 | 1306 | not metadata blocks. In Windows, FreeBSD, DragonFlyBSD or OSX there is no |
730bd7d9 SW |
1307 | :manpage:`fdatasync(2)` so this falls back to using :manpage:`fsync(2)`. |
1308 | Defaults to 0, which means fio does not periodically issue and wait for a | |
1309 | data-only sync to complete. | |
f80dba8d MT |
1310 | |
1311 | .. option:: write_barrier=int | |
1312 | ||
2831be97 | 1313 | Make every `N-th` write a barrier write. |
f80dba8d | 1314 | |
f50fbdda | 1315 | .. option:: sync_file_range=str:int |
f80dba8d | 1316 | |
f50fbdda | 1317 | Use :manpage:`sync_file_range(2)` for every `int` number of write |
f80dba8d MT |
1318 | operations. Fio will track range of writes that have happened since the last |
1319 | :manpage:`sync_file_range(2)` call. `str` can currently be one or more of: | |
1320 | ||
1321 | **wait_before** | |
1322 | SYNC_FILE_RANGE_WAIT_BEFORE | |
1323 | **write** | |
1324 | SYNC_FILE_RANGE_WRITE | |
1325 | **wait_after** | |
1326 | SYNC_FILE_RANGE_WAIT_AFTER | |
1327 | ||
1328 | So if you do ``sync_file_range=wait_before,write:8``, fio would use | |
1329 | ``SYNC_FILE_RANGE_WAIT_BEFORE | SYNC_FILE_RANGE_WRITE`` for every 8 | |
1330 | writes. Also see the :manpage:`sync_file_range(2)` man page. This option is | |
1331 | Linux specific. | |
1332 | ||
1333 | .. option:: overwrite=bool | |
1334 | ||
1335 | If true, writes to a file will always overwrite existing data. If the file | |
1336 | doesn't already exist, it will be created before the write phase begins. If | |
1337 | the file exists and is large enough for the specified write phase, nothing | |
a47b697c | 1338 | will be done. Default: false. |
f80dba8d MT |
1339 | |
1340 | .. option:: end_fsync=bool | |
1341 | ||
a47b697c SW |
1342 | If true, :manpage:`fsync(2)` file contents when a write stage has completed. |
1343 | Default: false. | |
f80dba8d MT |
1344 | |
1345 | .. option:: fsync_on_close=bool | |
1346 | ||
1347 | If true, fio will :manpage:`fsync(2)` a dirty file on close. This differs | |
a47b697c SW |
1348 | from :option:`end_fsync` in that it will happen on every file close, not |
1349 | just at the end of the job. Default: false. | |
f80dba8d MT |
1350 | |
1351 | .. option:: rwmixread=int | |
1352 | ||
1353 | Percentage of a mixed workload that should be reads. Default: 50. | |
1354 | ||
1355 | .. option:: rwmixwrite=int | |
1356 | ||
1357 | Percentage of a mixed workload that should be writes. If both | |
1358 | :option:`rwmixread` and :option:`rwmixwrite` is given and the values do not | |
1359 | add up to 100%, the latter of the two will be used to override the | |
1360 | first. This may interfere with a given rate setting, if fio is asked to | |
1361 | limit reads or writes to a certain rate. If that is the case, then the | |
1362 | distribution may be skewed. Default: 50. | |
1363 | ||
1364 | .. option:: random_distribution=str:float[,str:float][,str:float] | |
1365 | ||
1366 | By default, fio will use a completely uniform random distribution when asked | |
1367 | to perform random I/O. Sometimes it is useful to skew the distribution in | |
1368 | specific ways, ensuring that some parts of the data is more hot than others. | |
1369 | fio includes the following distribution models: | |
1370 | ||
1371 | **random** | |
1372 | Uniform random distribution | |
1373 | ||
1374 | **zipf** | |
1375 | Zipf distribution | |
1376 | ||
1377 | **pareto** | |
1378 | Pareto distribution | |
1379 | ||
b2f4b559 | 1380 | **normal** |
c60ebc45 | 1381 | Normal (Gaussian) distribution |
f80dba8d MT |
1382 | |
1383 | **zoned** | |
1384 | Zoned random distribution | |
1385 | ||
59466396 JA |
1386 | **zoned_abs** |
1387 | Zone absolute random distribution | |
1388 | ||
f80dba8d | 1389 | When using a **zipf** or **pareto** distribution, an input value is also |
f50fbdda | 1390 | needed to define the access pattern. For **zipf**, this is the `Zipf |
c60ebc45 | 1391 | theta`. For **pareto**, it's the `Pareto power`. Fio includes a test |
f50fbdda | 1392 | program, :command:`fio-genzipf`, that can be used visualize what the given input |
f80dba8d MT |
1393 | values will yield in terms of hit rates. If you wanted to use **zipf** with |
1394 | a `theta` of 1.2, you would use ``random_distribution=zipf:1.2`` as the | |
1395 | option. If a non-uniform model is used, fio will disable use of the random | |
b2f4b559 SW |
1396 | map. For the **normal** distribution, a normal (Gaussian) deviation is |
1397 | supplied as a value between 0 and 100. | |
f80dba8d MT |
1398 | |
1399 | For a **zoned** distribution, fio supports specifying percentages of I/O | |
1400 | access that should fall within what range of the file or device. For | |
1401 | example, given a criteria of: | |
1402 | ||
f50fbdda TK |
1403 | * 60% of accesses should be to the first 10% |
1404 | * 30% of accesses should be to the next 20% | |
1405 | * 8% of accesses should be to the next 30% | |
1406 | * 2% of accesses should be to the next 40% | |
f80dba8d MT |
1407 | |
1408 | we can define that through zoning of the random accesses. For the above | |
1409 | example, the user would do:: | |
1410 | ||
1411 | random_distribution=zoned:60/10:30/20:8/30:2/40 | |
1412 | ||
59466396 JA |
1413 | A **zoned_abs** distribution works exactly like the **zoned**, except |
1414 | that it takes absolute sizes. For example, let's say you wanted to | |
1415 | define access according to the following criteria: | |
1416 | ||
1417 | * 60% of accesses should be to the first 20G | |
1418 | * 30% of accesses should be to the next 100G | |
1419 | * 10% of accesses should be to the next 500G | |
1420 | ||
1421 | we can define an absolute zoning distribution with: | |
1422 | ||
1423 | random_distribution=zoned_abs=60/20G:30/100G:10/500g | |
1424 | ||
6a16ece8 JA |
1425 | For both **zoned** and **zoned_abs**, fio supports defining up to |
1426 | 256 separate zones. | |
1427 | ||
59466396 JA |
1428 | Similarly to how :option:`bssplit` works for setting ranges and |
1429 | percentages of block sizes. Like :option:`bssplit`, it's possible to | |
1430 | specify separate zones for reads, writes, and trims. If just one set | |
1431 | is given, it'll apply to all of them. This goes for both **zoned** | |
1432 | **zoned_abs** distributions. | |
f80dba8d MT |
1433 | |
1434 | .. option:: percentage_random=int[,int][,int] | |
1435 | ||
1436 | For a random workload, set how big a percentage should be random. This | |
1437 | defaults to 100%, in which case the workload is fully random. It can be set | |
1438 | from anywhere from 0 to 100. Setting it to 0 would make the workload fully | |
1439 | sequential. Any setting in between will result in a random mix of sequential | |
1440 | and random I/O, at the given percentages. Comma-separated values may be | |
1441 | specified for reads, writes, and trims as described in :option:`blocksize`. | |
1442 | ||
1443 | .. option:: norandommap | |
1444 | ||
1445 | Normally fio will cover every block of the file when doing random I/O. If | |
1446 | this option is given, fio will just get a new random offset without looking | |
1447 | at past I/O history. This means that some blocks may not be read or written, | |
1448 | and that some blocks may be read/written more than once. If this option is | |
1449 | used with :option:`verify` and multiple blocksizes (via :option:`bsrange`), | |
1450 | only intact blocks are verified, i.e., partially-overwritten blocks are | |
47e6a6e5 SW |
1451 | ignored. With an async I/O engine and an I/O depth > 1, it is possible for |
1452 | the same block to be overwritten, which can cause verification errors. Either | |
1453 | do not use norandommap in this case, or also use the lfsr random generator. | |
f80dba8d MT |
1454 | |
1455 | .. option:: softrandommap=bool | |
1456 | ||
1457 | See :option:`norandommap`. If fio runs with the random block map enabled and | |
1458 | it fails to allocate the map, if this option is set it will continue without | |
1459 | a random block map. As coverage will not be as complete as with random maps, | |
1460 | this option is disabled by default. | |
1461 | ||
1462 | .. option:: random_generator=str | |
1463 | ||
f50fbdda | 1464 | Fio supports the following engines for generating I/O offsets for random I/O: |
f80dba8d MT |
1465 | |
1466 | **tausworthe** | |
f50fbdda | 1467 | Strong 2^88 cycle random number generator. |
f80dba8d | 1468 | **lfsr** |
f50fbdda | 1469 | Linear feedback shift register generator. |
f80dba8d | 1470 | **tausworthe64** |
f50fbdda | 1471 | Strong 64-bit 2^258 cycle random number generator. |
f80dba8d MT |
1472 | |
1473 | **tausworthe** is a strong random number generator, but it requires tracking | |
1474 | on the side if we want to ensure that blocks are only read or written | |
f50fbdda | 1475 | once. **lfsr** guarantees that we never generate the same offset twice, and |
f80dba8d | 1476 | it's also less computationally expensive. It's not a true random generator, |
f50fbdda | 1477 | however, though for I/O purposes it's typically good enough. **lfsr** only |
f80dba8d MT |
1478 | works with single block sizes, not with workloads that use multiple block |
1479 | sizes. If used with such a workload, fio may read or write some blocks | |
1480 | multiple times. The default value is **tausworthe**, unless the required | |
1481 | space exceeds 2^32 blocks. If it does, then **tausworthe64** is | |
1482 | selected automatically. | |
1483 | ||
1484 | ||
1485 | Block size | |
1486 | ~~~~~~~~~~ | |
1487 | ||
1488 | .. option:: blocksize=int[,int][,int], bs=int[,int][,int] | |
1489 | ||
1490 | The block size in bytes used for I/O units. Default: 4096. A single value | |
1491 | applies to reads, writes, and trims. Comma-separated values may be | |
1492 | specified for reads, writes, and trims. A value not terminated in a comma | |
1493 | applies to subsequent types. | |
1494 | ||
1495 | Examples: | |
1496 | ||
1497 | **bs=256k** | |
1498 | means 256k for reads, writes and trims. | |
1499 | ||
1500 | **bs=8k,32k** | |
1501 | means 8k for reads, 32k for writes and trims. | |
1502 | ||
1503 | **bs=8k,32k,** | |
1504 | means 8k for reads, 32k for writes, and default for trims. | |
1505 | ||
1506 | **bs=,8k** | |
1507 | means default for reads, 8k for writes and trims. | |
1508 | ||
1509 | **bs=,8k,** | |
b443ae44 | 1510 | means default for reads, 8k for writes, and default for trims. |
f80dba8d MT |
1511 | |
1512 | .. option:: blocksize_range=irange[,irange][,irange], bsrange=irange[,irange][,irange] | |
1513 | ||
1514 | A range of block sizes in bytes for I/O units. The issued I/O unit will | |
1515 | always be a multiple of the minimum size, unless | |
1516 | :option:`blocksize_unaligned` is set. | |
1517 | ||
1518 | Comma-separated ranges may be specified for reads, writes, and trims as | |
1519 | described in :option:`blocksize`. | |
1520 | ||
1521 | Example: ``bsrange=1k-4k,2k-8k``. | |
1522 | ||
1523 | .. option:: bssplit=str[,str][,str] | |
1524 | ||
6a16ece8 JA |
1525 | Sometimes you want even finer grained control of the block sizes |
1526 | issued, not just an even split between them. This option allows you to | |
1527 | weight various block sizes, so that you are able to define a specific | |
1528 | amount of block sizes issued. The format for this option is:: | |
f80dba8d MT |
1529 | |
1530 | bssplit=blocksize/percentage:blocksize/percentage | |
1531 | ||
6a16ece8 JA |
1532 | for as many block sizes as needed. So if you want to define a workload |
1533 | that has 50% 64k blocks, 10% 4k blocks, and 40% 32k blocks, you would | |
1534 | write:: | |
f80dba8d MT |
1535 | |
1536 | bssplit=4k/10:64k/50:32k/40 | |
1537 | ||
6a16ece8 JA |
1538 | Ordering does not matter. If the percentage is left blank, fio will |
1539 | fill in the remaining values evenly. So a bssplit option like this one:: | |
f80dba8d MT |
1540 | |
1541 | bssplit=4k/50:1k/:32k/ | |
1542 | ||
6a16ece8 JA |
1543 | would have 50% 4k ios, and 25% 1k and 32k ios. The percentages always |
1544 | add up to 100, if bssplit is given a range that adds up to more, it | |
1545 | will error out. | |
f80dba8d MT |
1546 | |
1547 | Comma-separated values may be specified for reads, writes, and trims as | |
1548 | described in :option:`blocksize`. | |
1549 | ||
6a16ece8 JA |
1550 | If you want a workload that has 50% 2k reads and 50% 4k reads, while |
1551 | having 90% 4k writes and 10% 8k writes, you would specify:: | |
f80dba8d | 1552 | |
cf04b906 | 1553 | bssplit=2k/50:4k/50,4k/90:8k/10 |
f80dba8d | 1554 | |
6a16ece8 JA |
1555 | Fio supports defining up to 64 different weights for each data |
1556 | direction. | |
1557 | ||
f80dba8d MT |
1558 | .. option:: blocksize_unaligned, bs_unaligned |
1559 | ||
1560 | If set, fio will issue I/O units with any size within | |
1561 | :option:`blocksize_range`, not just multiples of the minimum size. This | |
1562 | typically won't work with direct I/O, as that normally requires sector | |
1563 | alignment. | |
1564 | ||
589e88b7 | 1565 | .. option:: bs_is_seq_rand=bool |
f80dba8d MT |
1566 | |
1567 | If this option is set, fio will use the normal read,write blocksize settings | |
1568 | as sequential,random blocksize settings instead. Any random read or write | |
1569 | will use the WRITE blocksize settings, and any sequential read or write will | |
1570 | use the READ blocksize settings. | |
1571 | ||
1572 | .. option:: blockalign=int[,int][,int], ba=int[,int][,int] | |
1573 | ||
1574 | Boundary to which fio will align random I/O units. Default: | |
1575 | :option:`blocksize`. Minimum alignment is typically 512b for using direct | |
1576 | I/O, though it usually depends on the hardware block size. This option is | |
1577 | mutually exclusive with using a random map for files, so it will turn off | |
1578 | that option. Comma-separated values may be specified for reads, writes, and | |
1579 | trims as described in :option:`blocksize`. | |
1580 | ||
1581 | ||
1582 | Buffers and memory | |
1583 | ~~~~~~~~~~~~~~~~~~ | |
1584 | ||
1585 | .. option:: zero_buffers | |
1586 | ||
1587 | Initialize buffers with all zeros. Default: fill buffers with random data. | |
1588 | ||
1589 | .. option:: refill_buffers | |
1590 | ||
1591 | If this option is given, fio will refill the I/O buffers on every | |
72592780 SW |
1592 | submit. Only makes sense if :option:`zero_buffers` isn't specified, |
1593 | naturally. Defaults to being unset i.e., the buffer is only filled at | |
1594 | init time and the data in it is reused when possible but if any of | |
1595 | :option:`verify`, :option:`buffer_compress_percentage` or | |
1596 | :option:`dedupe_percentage` are enabled then `refill_buffers` is also | |
1597 | automatically enabled. | |
f80dba8d MT |
1598 | |
1599 | .. option:: scramble_buffers=bool | |
1600 | ||
1601 | If :option:`refill_buffers` is too costly and the target is using data | |
1602 | deduplication, then setting this option will slightly modify the I/O buffer | |
1603 | contents to defeat normal de-dupe attempts. This is not enough to defeat | |
1604 | more clever block compression attempts, but it will stop naive dedupe of | |
1605 | blocks. Default: true. | |
1606 | ||
1607 | .. option:: buffer_compress_percentage=int | |
1608 | ||
72592780 SW |
1609 | If this is set, then fio will attempt to provide I/O buffer content |
1610 | (on WRITEs) that compresses to the specified level. Fio does this by | |
1611 | providing a mix of random data followed by fixed pattern data. The | |
1612 | fixed pattern is either zeros, or the pattern specified by | |
1613 | :option:`buffer_pattern`. If the `buffer_pattern` option is used, it | |
1614 | might skew the compression ratio slightly. Setting | |
1615 | `buffer_compress_percentage` to a value other than 100 will also | |
1616 | enable :option:`refill_buffers` in order to reduce the likelihood that | |
1617 | adjacent blocks are so similar that they over compress when seen | |
1618 | together. See :option:`buffer_compress_chunk` for how to set a finer or | |
1619 | coarser granularity for the random/fixed data region. Defaults to unset | |
1620 | i.e., buffer data will not adhere to any compression level. | |
f80dba8d MT |
1621 | |
1622 | .. option:: buffer_compress_chunk=int | |
1623 | ||
72592780 SW |
1624 | This setting allows fio to manage how big the random/fixed data region |
1625 | is when using :option:`buffer_compress_percentage`. When | |
1626 | `buffer_compress_chunk` is set to some non-zero value smaller than the | |
1627 | block size, fio can repeat the random/fixed region throughout the I/O | |
1628 | buffer at the specified interval (which particularly useful when | |
1629 | bigger block sizes are used for a job). When set to 0, fio will use a | |
1630 | chunk size that matches the block size resulting in a single | |
1631 | random/fixed region within the I/O buffer. Defaults to 512. When the | |
1632 | unit is omitted, the value is interpreted in bytes. | |
f80dba8d MT |
1633 | |
1634 | .. option:: buffer_pattern=str | |
1635 | ||
a1554f65 SB |
1636 | If set, fio will fill the I/O buffers with this pattern or with the contents |
1637 | of a file. If not set, the contents of I/O buffers are defined by the other | |
1638 | options related to buffer contents. The setting can be any pattern of bytes, | |
1639 | and can be prefixed with 0x for hex values. It may also be a string, where | |
1640 | the string must then be wrapped with ``""``. Or it may also be a filename, | |
1641 | where the filename must be wrapped with ``''`` in which case the file is | |
1642 | opened and read. Note that not all the file contents will be read if that | |
1643 | would cause the buffers to overflow. So, for example:: | |
1644 | ||
1645 | buffer_pattern='filename' | |
1646 | ||
1647 | or:: | |
f80dba8d MT |
1648 | |
1649 | buffer_pattern="abcd" | |
1650 | ||
1651 | or:: | |
1652 | ||
1653 | buffer_pattern=-12 | |
1654 | ||
1655 | or:: | |
1656 | ||
1657 | buffer_pattern=0xdeadface | |
1658 | ||
1659 | Also you can combine everything together in any order:: | |
1660 | ||
a1554f65 | 1661 | buffer_pattern=0xdeadface"abcd"-12'filename' |
f80dba8d MT |
1662 | |
1663 | .. option:: dedupe_percentage=int | |
1664 | ||
1665 | If set, fio will generate this percentage of identical buffers when | |
1666 | writing. These buffers will be naturally dedupable. The contents of the | |
1667 | buffers depend on what other buffer compression settings have been set. It's | |
1668 | possible to have the individual buffers either fully compressible, or not at | |
72592780 SW |
1669 | all -- this option only controls the distribution of unique buffers. Setting |
1670 | this option will also enable :option:`refill_buffers` to prevent every buffer | |
1671 | being identical. | |
f80dba8d MT |
1672 | |
1673 | .. option:: invalidate=bool | |
1674 | ||
730bd7d9 SW |
1675 | Invalidate the buffer/page cache parts of the files to be used prior to |
1676 | starting I/O if the platform and file type support it. Defaults to true. | |
21c1b29e TK |
1677 | This will be ignored if :option:`pre_read` is also specified for the |
1678 | same job. | |
f80dba8d MT |
1679 | |
1680 | .. option:: sync=bool | |
1681 | ||
1682 | Use synchronous I/O for buffered writes. For the majority of I/O engines, | |
1683 | this means using O_SYNC. Default: false. | |
1684 | ||
1685 | .. option:: iomem=str, mem=str | |
1686 | ||
1687 | Fio can use various types of memory as the I/O unit buffer. The allowed | |
1688 | values are: | |
1689 | ||
1690 | **malloc** | |
1691 | Use memory from :manpage:`malloc(3)` as the buffers. Default memory | |
1692 | type. | |
1693 | ||
1694 | **shm** | |
1695 | Use shared memory as the buffers. Allocated through | |
1696 | :manpage:`shmget(2)`. | |
1697 | ||
1698 | **shmhuge** | |
1699 | Same as shm, but use huge pages as backing. | |
1700 | ||
1701 | **mmap** | |
22413915 | 1702 | Use :manpage:`mmap(2)` to allocate buffers. May either be anonymous memory, or can |
f80dba8d MT |
1703 | be file backed if a filename is given after the option. The format |
1704 | is `mem=mmap:/path/to/file`. | |
1705 | ||
1706 | **mmaphuge** | |
1707 | Use a memory mapped huge file as the buffer backing. Append filename | |
1708 | after mmaphuge, ala `mem=mmaphuge:/hugetlbfs/file`. | |
1709 | ||
1710 | **mmapshared** | |
1711 | Same as mmap, but use a MMAP_SHARED mapping. | |
1712 | ||
03553853 YR |
1713 | **cudamalloc** |
1714 | Use GPU memory as the buffers for GPUDirect RDMA benchmark. | |
f50fbdda | 1715 | The :option:`ioengine` must be `rdma`. |
03553853 | 1716 | |
f80dba8d MT |
1717 | The area allocated is a function of the maximum allowed bs size for the job, |
1718 | multiplied by the I/O depth given. Note that for **shmhuge** and | |
1719 | **mmaphuge** to work, the system must have free huge pages allocated. This | |
1720 | can normally be checked and set by reading/writing | |
1721 | :file:`/proc/sys/vm/nr_hugepages` on a Linux system. Fio assumes a huge page | |
1722 | is 4MiB in size. So to calculate the number of huge pages you need for a | |
1723 | given job file, add up the I/O depth of all jobs (normally one unless | |
1724 | :option:`iodepth` is used) and multiply by the maximum bs set. Then divide | |
1725 | that number by the huge page size. You can see the size of the huge pages in | |
1726 | :file:`/proc/meminfo`. If no huge pages are allocated by having a non-zero | |
1727 | number in `nr_hugepages`, using **mmaphuge** or **shmhuge** will fail. Also | |
1728 | see :option:`hugepage-size`. | |
1729 | ||
1730 | **mmaphuge** also needs to have hugetlbfs mounted and the file location | |
1731 | should point there. So if it's mounted in :file:`/huge`, you would use | |
1732 | `mem=mmaphuge:/huge/somefile`. | |
1733 | ||
f50fbdda | 1734 | .. option:: iomem_align=int, mem_align=int |
f80dba8d MT |
1735 | |
1736 | This indicates the memory alignment of the I/O memory buffers. Note that | |
1737 | the given alignment is applied to the first I/O unit buffer, if using | |
1738 | :option:`iodepth` the alignment of the following buffers are given by the | |
1739 | :option:`bs` used. In other words, if using a :option:`bs` that is a | |
1740 | multiple of the page sized in the system, all buffers will be aligned to | |
1741 | this value. If using a :option:`bs` that is not page aligned, the alignment | |
1742 | of subsequent I/O memory buffers is the sum of the :option:`iomem_align` and | |
1743 | :option:`bs` used. | |
1744 | ||
1745 | .. option:: hugepage-size=int | |
1746 | ||
1747 | Defines the size of a huge page. Must at least be equal to the system | |
1748 | setting, see :file:`/proc/meminfo`. Defaults to 4MiB. Should probably | |
1749 | always be a multiple of megabytes, so using ``hugepage-size=Xm`` is the | |
1750 | preferred way to set this to avoid setting a non-pow-2 bad value. | |
1751 | ||
1752 | .. option:: lockmem=int | |
1753 | ||
1754 | Pin the specified amount of memory with :manpage:`mlock(2)`. Can be used to | |
1755 | simulate a smaller amount of memory. The amount specified is per worker. | |
1756 | ||
1757 | ||
1758 | I/O size | |
1759 | ~~~~~~~~ | |
1760 | ||
1761 | .. option:: size=int | |
1762 | ||
79591fa9 TK |
1763 | The total size of file I/O for each thread of this job. Fio will run until |
1764 | this many bytes has been transferred, unless runtime is limited by other options | |
1765 | (such as :option:`runtime`, for instance, or increased/decreased by :option:`io_size`). | |
1766 | Fio will divide this size between the available files determined by options | |
1767 | such as :option:`nrfiles`, :option:`filename`, unless :option:`filesize` is | |
1768 | specified by the job. If the result of division happens to be 0, the size is | |
c4aa2d08 | 1769 | set to the physical size of the given files or devices if they exist. |
79591fa9 | 1770 | If this option is not specified, fio will use the full size of the given |
f80dba8d MT |
1771 | files or devices. If the files do not exist, size must be given. It is also |
1772 | possible to give size as a percentage between 1 and 100. If ``size=20%`` is | |
1773 | given, fio will use 20% of the full size of the given files or devices. | |
9d25d068 SW |
1774 | Can be combined with :option:`offset` to constrain the start and end range |
1775 | that I/O will be done within. | |
f80dba8d MT |
1776 | |
1777 | .. option:: io_size=int, io_limit=int | |
1778 | ||
1779 | Normally fio operates within the region set by :option:`size`, which means | |
1780 | that the :option:`size` option sets both the region and size of I/O to be | |
1781 | performed. Sometimes that is not what you want. With this option, it is | |
1782 | possible to define just the amount of I/O that fio should do. For instance, | |
1783 | if :option:`size` is set to 20GiB and :option:`io_size` is set to 5GiB, fio | |
1784 | will perform I/O within the first 20GiB but exit when 5GiB have been | |
1785 | done. The opposite is also possible -- if :option:`size` is set to 20GiB, | |
1786 | and :option:`io_size` is set to 40GiB, then fio will do 40GiB of I/O within | |
1787 | the 0..20GiB region. | |
1788 | ||
7fdd97ca | 1789 | .. option:: filesize=irange(int) |
f80dba8d MT |
1790 | |
1791 | Individual file sizes. May be a range, in which case fio will select sizes | |
1792 | for files at random within the given range and limited to :option:`size` in | |
1793 | total (if that is given). If not given, each created file is the same size. | |
79591fa9 TK |
1794 | This option overrides :option:`size` in terms of file size, which means |
1795 | this value is used as a fixed size or possible range of each file. | |
f80dba8d MT |
1796 | |
1797 | .. option:: file_append=bool | |
1798 | ||
1799 | Perform I/O after the end of the file. Normally fio will operate within the | |
1800 | size of a file. If this option is set, then fio will append to the file | |
1801 | instead. This has identical behavior to setting :option:`offset` to the size | |
1802 | of a file. This option is ignored on non-regular files. | |
1803 | ||
1804 | .. option:: fill_device=bool, fill_fs=bool | |
1805 | ||
1806 | Sets size to something really large and waits for ENOSPC (no space left on | |
1807 | device) as the terminating condition. Only makes sense with sequential | |
1808 | write. For a read workload, the mount point will be filled first then I/O | |
1809 | started on the result. This option doesn't make sense if operating on a raw | |
1810 | device node, since the size of that is already known by the file system. | |
1811 | Additionally, writing beyond end-of-device will not return ENOSPC there. | |
1812 | ||
1813 | ||
1814 | I/O engine | |
1815 | ~~~~~~~~~~ | |
1816 | ||
1817 | .. option:: ioengine=str | |
1818 | ||
1819 | Defines how the job issues I/O to the file. The following types are defined: | |
1820 | ||
1821 | **sync** | |
1822 | Basic :manpage:`read(2)` or :manpage:`write(2)` | |
1823 | I/O. :manpage:`lseek(2)` is used to position the I/O location. | |
54227e6b | 1824 | See :option:`fsync` and :option:`fdatasync` for syncing write I/Os. |
f80dba8d MT |
1825 | |
1826 | **psync** | |
1827 | Basic :manpage:`pread(2)` or :manpage:`pwrite(2)` I/O. Default on | |
1828 | all supported operating systems except for Windows. | |
1829 | ||
1830 | **vsync** | |
1831 | Basic :manpage:`readv(2)` or :manpage:`writev(2)` I/O. Will emulate | |
c60ebc45 | 1832 | queuing by coalescing adjacent I/Os into a single submission. |
f80dba8d MT |
1833 | |
1834 | **pvsync** | |
1835 | Basic :manpage:`preadv(2)` or :manpage:`pwritev(2)` I/O. | |
1836 | ||
1837 | **pvsync2** | |
1838 | Basic :manpage:`preadv2(2)` or :manpage:`pwritev2(2)` I/O. | |
1839 | ||
029b42ac JA |
1840 | **io_uring** |
1841 | Fast Linux native asynchronous I/O. Supports async IO | |
1842 | for both direct and buffered IO. | |
1843 | This engine defines engine specific options. | |
1844 | ||
f80dba8d MT |
1845 | **libaio** |
1846 | Linux native asynchronous I/O. Note that Linux may only support | |
22413915 | 1847 | queued behavior with non-buffered I/O (set ``direct=1`` or |
f80dba8d MT |
1848 | ``buffered=0``). |
1849 | This engine defines engine specific options. | |
1850 | ||
1851 | **posixaio** | |
1852 | POSIX asynchronous I/O using :manpage:`aio_read(3)` and | |
1853 | :manpage:`aio_write(3)`. | |
1854 | ||
1855 | **solarisaio** | |
1856 | Solaris native asynchronous I/O. | |
1857 | ||
1858 | **windowsaio** | |
1859 | Windows native asynchronous I/O. Default on Windows. | |
1860 | ||
1861 | **mmap** | |
1862 | File is memory mapped with :manpage:`mmap(2)` and data copied | |
1863 | to/from using :manpage:`memcpy(3)`. | |
1864 | ||
1865 | **splice** | |
1866 | :manpage:`splice(2)` is used to transfer the data and | |
1867 | :manpage:`vmsplice(2)` to transfer data from user space to the | |
1868 | kernel. | |
1869 | ||
1870 | **sg** | |
1871 | SCSI generic sg v3 I/O. May either be synchronous using the SG_IO | |
1872 | ioctl, or if the target is an sg character device we use | |
1873 | :manpage:`read(2)` and :manpage:`write(2)` for asynchronous | |
f50fbdda | 1874 | I/O. Requires :option:`filename` option to specify either block or |
3740cfc8 | 1875 | character devices. This engine supports trim operations. |
52b81b7c | 1876 | The sg engine includes engine specific options. |
f80dba8d MT |
1877 | |
1878 | **null** | |
1879 | Doesn't transfer any data, just pretends to. This is mainly used to | |
1880 | exercise fio itself and for debugging/testing purposes. | |
1881 | ||
1882 | **net** | |
1883 | Transfer over the network to given ``host:port``. Depending on the | |
1884 | :option:`protocol` used, the :option:`hostname`, :option:`port`, | |
1885 | :option:`listen` and :option:`filename` options are used to specify | |
1886 | what sort of connection to make, while the :option:`protocol` option | |
1887 | determines which protocol will be used. This engine defines engine | |
1888 | specific options. | |
1889 | ||
1890 | **netsplice** | |
1891 | Like **net**, but uses :manpage:`splice(2)` and | |
1892 | :manpage:`vmsplice(2)` to map data and send/receive. | |
1893 | This engine defines engine specific options. | |
1894 | ||
1895 | **cpuio** | |
1896 | Doesn't transfer any data, but burns CPU cycles according to the | |
1897 | :option:`cpuload` and :option:`cpuchunks` options. Setting | |
9207a0cb | 1898 | :option:`cpuload`\=85 will cause that job to do nothing but burn 85% |
71aa48eb | 1899 | of the CPU. In case of SMP machines, use :option:`numjobs`\=<nr_of_cpu> |
f50fbdda | 1900 | to get desired CPU usage, as the cpuload only loads a |
f80dba8d MT |
1901 | single CPU at the desired rate. A job never finishes unless there is |
1902 | at least one non-cpuio job. | |
1903 | ||
f80dba8d MT |
1904 | **rdma** |
1905 | The RDMA I/O engine supports both RDMA memory semantics | |
1906 | (RDMA_WRITE/RDMA_READ) and channel semantics (Send/Recv) for the | |
609ac152 SB |
1907 | InfiniBand, RoCE and iWARP protocols. This engine defines engine |
1908 | specific options. | |
f80dba8d MT |
1909 | |
1910 | **falloc** | |
1911 | I/O engine that does regular fallocate to simulate data transfer as | |
1912 | fio ioengine. | |
1913 | ||
1914 | DDIR_READ | |
1915 | does fallocate(,mode = FALLOC_FL_KEEP_SIZE,). | |
1916 | ||
1917 | DDIR_WRITE | |
1918 | does fallocate(,mode = 0). | |
1919 | ||
1920 | DDIR_TRIM | |
1921 | does fallocate(,mode = FALLOC_FL_KEEP_SIZE|FALLOC_FL_PUNCH_HOLE). | |
1922 | ||
761cd093 SW |
1923 | **ftruncate** |
1924 | I/O engine that sends :manpage:`ftruncate(2)` operations in response | |
1925 | to write (DDIR_WRITE) events. Each ftruncate issued sets the file's | |
f50fbdda | 1926 | size to the current block offset. :option:`blocksize` is ignored. |
761cd093 | 1927 | |
f80dba8d MT |
1928 | **e4defrag** |
1929 | I/O engine that does regular EXT4_IOC_MOVE_EXT ioctls to simulate | |
1930 | defragment activity in request to DDIR_WRITE event. | |
1931 | ||
f3f96717 IF |
1932 | **rados** |
1933 | I/O engine supporting direct access to Ceph Reliable Autonomic | |
1934 | Distributed Object Store (RADOS) via librados. This ioengine | |
1935 | defines engine specific options. | |
1936 | ||
f80dba8d MT |
1937 | **rbd** |
1938 | I/O engine supporting direct access to Ceph Rados Block Devices | |
1939 | (RBD) via librbd without the need to use the kernel rbd driver. This | |
1940 | ioengine defines engine specific options. | |
1941 | ||
c2f6a13d LMB |
1942 | **http** |
1943 | I/O engine supporting GET/PUT requests over HTTP(S) with libcurl to | |
1944 | a WebDAV or S3 endpoint. This ioengine defines engine specific options. | |
1945 | ||
1946 | This engine only supports direct IO of iodepth=1; you need to scale this | |
1947 | via numjobs. blocksize defines the size of the objects to be created. | |
1948 | ||
1949 | TRIM is translated to object deletion. | |
1950 | ||
f80dba8d | 1951 | **gfapi** |
ac8ca2af SW |
1952 | Using GlusterFS libgfapi sync interface to direct access to |
1953 | GlusterFS volumes without having to go through FUSE. This ioengine | |
f80dba8d MT |
1954 | defines engine specific options. |
1955 | ||
1956 | **gfapi_async** | |
ac8ca2af SW |
1957 | Using GlusterFS libgfapi async interface to direct access to |
1958 | GlusterFS volumes without having to go through FUSE. This ioengine | |
f80dba8d MT |
1959 | defines engine specific options. |
1960 | ||
1961 | **libhdfs** | |
f50fbdda | 1962 | Read and write through Hadoop (HDFS). The :option:`filename` option |
f80dba8d MT |
1963 | is used to specify host,port of the hdfs name-node to connect. This |
1964 | engine interprets offsets a little differently. In HDFS, files once | |
e25c0c91 SW |
1965 | created cannot be modified so random writes are not possible. To |
1966 | imitate this the libhdfs engine expects a bunch of small files to be | |
1967 | created over HDFS and will randomly pick a file from them | |
1968 | based on the offset generated by fio backend (see the example | |
f80dba8d | 1969 | job file to create such files, use ``rw=write`` option). Please |
e25c0c91 SW |
1970 | note, it may be necessary to set environment variables to work |
1971 | with HDFS/libhdfs properly. Each job uses its own connection to | |
f80dba8d MT |
1972 | HDFS. |
1973 | ||
1974 | **mtd** | |
1975 | Read, write and erase an MTD character device (e.g., | |
1976 | :file:`/dev/mtd0`). Discards are treated as erases. Depending on the | |
1977 | underlying device type, the I/O may have to go in a certain pattern, | |
1978 | e.g., on NAND, writing sequentially to erase blocks and discarding | |
c298ee71 | 1979 | before overwriting. The `trimwrite` mode works well for this |
f80dba8d MT |
1980 | constraint. |
1981 | ||
1982 | **pmemblk** | |
1983 | Read and write using filesystem DAX to a file on a filesystem | |
363a5f65 | 1984 | mounted with DAX on a persistent memory device through the PMDK |
f80dba8d MT |
1985 | libpmemblk library. |
1986 | ||
1987 | **dev-dax** | |
1988 | Read and write using device DAX to a persistent memory device (e.g., | |
363a5f65 | 1989 | /dev/dax0.0) through the PMDK libpmem library. |
f80dba8d MT |
1990 | |
1991 | **external** | |
1992 | Prefix to specify loading an external I/O engine object file. Append | |
c60ebc45 | 1993 | the engine filename, e.g. ``ioengine=external:/tmp/foo.o`` to load |
d243fd6d TK |
1994 | ioengine :file:`foo.o` in :file:`/tmp`. The path can be either |
1995 | absolute or relative. See :file:`engines/skeleton_external.c` for | |
1996 | details of writing an external I/O engine. | |
f80dba8d | 1997 | |
1216cc5a | 1998 | **filecreate** |
b71968b1 | 1999 | Simply create the files and do no I/O to them. You still need to |
1216cc5a | 2000 | set `filesize` so that all the accounting still occurs, but no |
b71968b1 | 2001 | actual I/O will be done other than creating the file. |
f80dba8d | 2002 | |
73ccd14e SF |
2003 | **filestat** |
2004 | Simply do stat() and do no I/O to the file. You need to set 'filesize' | |
2005 | and 'nrfiles', so that files will be created. | |
2006 | This engine is to measure file lookup and meta data access. | |
2007 | ||
ae0db592 TI |
2008 | **libpmem** |
2009 | Read and write using mmap I/O to a file on a filesystem | |
363a5f65 | 2010 | mounted with DAX on a persistent memory device through the PMDK |
ae0db592 TI |
2011 | libpmem library. |
2012 | ||
a40e7a59 GB |
2013 | **ime_psync** |
2014 | Synchronous read and write using DDN's Infinite Memory Engine (IME). | |
2015 | This engine is very basic and issues calls to IME whenever an IO is | |
2016 | queued. | |
2017 | ||
2018 | **ime_psyncv** | |
2019 | Synchronous read and write using DDN's Infinite Memory Engine (IME). | |
2020 | This engine uses iovecs and will try to stack as much IOs as possible | |
2021 | (if the IOs are "contiguous" and the IO depth is not exceeded) | |
2022 | before issuing a call to IME. | |
2023 | ||
2024 | **ime_aio** | |
2025 | Asynchronous read and write using DDN's Infinite Memory Engine (IME). | |
2026 | This engine will try to stack as much IOs as possible by creating | |
2027 | requests for IME. FIO will then decide when to commit these requests. | |
247ef2aa KZ |
2028 | **libiscsi** |
2029 | Read and write iscsi lun with libiscsi. | |
d643a1e2 | 2030 | **nbd** |
f2d6de5d | 2031 | Read and write a Network Block Device (NBD). |
a40e7a59 | 2032 | |
f80dba8d MT |
2033 | I/O engine specific parameters |
2034 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
2035 | ||
2036 | In addition, there are some parameters which are only valid when a specific | |
f50fbdda TK |
2037 | :option:`ioengine` is in use. These are used identically to normal parameters, |
2038 | with the caveat that when used on the command line, they must come after the | |
f80dba8d MT |
2039 | :option:`ioengine` that defines them is selected. |
2040 | ||
b2a432bf | 2041 | .. option:: cmdprio_percentage=int : [io_uring] [libaio] |
029b42ac | 2042 | |
b2a432bf PC |
2043 | Set the percentage of I/O that will be issued with higher priority by setting |
2044 | the priority bit. Non-read I/O is likely unaffected by ``cmdprio_percentage``. | |
2045 | This option cannot be used with the `prio` or `prioclass` options. For this | |
2046 | option to set the priority bit properly, NCQ priority must be supported and | |
7896180a VF |
2047 | enabled and :option:`direct`\=1 option must be used. fio must also be run as |
2048 | the root user. | |
029b42ac JA |
2049 | |
2050 | .. option:: fixedbufs : [io_uring] | |
2051 | ||
b2a432bf PC |
2052 | If fio is asked to do direct IO, then Linux will map pages for each |
2053 | IO call, and release them when IO is done. If this option is set, the | |
2054 | pages are pre-mapped before IO is started. This eliminates the need to | |
2055 | map and release for each IO. This is more efficient, and reduces the | |
2056 | IO latency as well. | |
2057 | ||
2058 | .. option:: hipri : [io_uring] | |
2059 | ||
2060 | If this option is set, fio will attempt to use polled IO completions. | |
2061 | Normal IO completions generate interrupts to signal the completion of | |
2062 | IO, polled completions do not. Hence they are require active reaping | |
2063 | by the application. The benefits are more efficient IO for high IOPS | |
2064 | scenarios, and lower latencies for low queue depth IO. | |
029b42ac | 2065 | |
5ffd5626 | 2066 | .. option:: registerfiles : [io_uring] |
2c870598 | 2067 | |
5ffd5626 JA |
2068 | With this option, fio registers the set of files being used with the |
2069 | kernel. This avoids the overhead of managing file counts in the kernel, | |
2070 | making the submission and completion part more lightweight. Required | |
2071 | for the below :option:`sqthread_poll` option. | |
2072 | ||
029b42ac JA |
2073 | .. option:: sqthread_poll : [io_uring] |
2074 | ||
2075 | Normally fio will submit IO by issuing a system call to notify the | |
2076 | kernel of available items in the SQ ring. If this option is set, the | |
2077 | act of submitting IO will be done by a polling thread in the kernel. | |
2078 | This frees up cycles for fio, at the cost of using more CPU in the | |
2079 | system. | |
2080 | ||
2081 | .. option:: sqthread_poll_cpu : [io_uring] | |
2082 | ||
2083 | When :option:`sqthread_poll` is set, this option provides a way to | |
2084 | define which CPU should be used for the polling thread. | |
2085 | ||
f80dba8d MT |
2086 | .. option:: userspace_reap : [libaio] |
2087 | ||
2088 | Normally, with the libaio engine in use, fio will use the | |
2089 | :manpage:`io_getevents(2)` system call to reap newly returned events. With | |
2090 | this flag turned on, the AIO ring will be read directly from user-space to | |
2091 | reap events. The reaping mode is only enabled when polling for a minimum of | |
c60ebc45 | 2092 | 0 events (e.g. when :option:`iodepth_batch_complete` `=0`). |
f80dba8d | 2093 | |
9d25d068 | 2094 | .. option:: hipri : [pvsync2] |
f80dba8d MT |
2095 | |
2096 | Set RWF_HIPRI on I/O, indicating to the kernel that it's of higher priority | |
2097 | than normal. | |
2098 | ||
a0679ce5 SB |
2099 | .. option:: hipri_percentage : [pvsync2] |
2100 | ||
f50fbdda | 2101 | When hipri is set this determines the probability of a pvsync2 I/O being high |
a0679ce5 SB |
2102 | priority. The default is 100%. |
2103 | ||
7d42e66e KK |
2104 | .. option:: nowait : [pvsync2] [libaio] [io_uring] |
2105 | ||
2106 | By default if a request cannot be executed immediately (e.g. resource starvation, | |
2107 | waiting on locks) it is queued and the initiating process will be blocked until | |
2108 | the required resource becomes free. | |
2109 | ||
2110 | This option sets the RWF_NOWAIT flag (supported from the 4.14 Linux kernel) and | |
2111 | the call will return instantly with EAGAIN or a partial result rather than waiting. | |
2112 | ||
2113 | It is useful to also use ignore_error=EAGAIN when using this option. | |
2114 | ||
2115 | Note: glibc 2.27, 2.28 have a bug in syscall wrappers preadv2, pwritev2. | |
2116 | They return EOPNOTSUP instead of EAGAIN. | |
2117 | ||
2118 | For cached I/O, using this option usually means a request operates only with | |
2119 | cached data. Currently the RWF_NOWAIT flag does not supported for cached write. | |
2120 | ||
2121 | For direct I/O, requests will only succeed if cache invalidation isn't required, | |
2122 | file blocks are fully allocated and the disk request could be issued immediately. | |
2123 | ||
f80dba8d MT |
2124 | .. option:: cpuload=int : [cpuio] |
2125 | ||
da19cdb4 TK |
2126 | Attempt to use the specified percentage of CPU cycles. This is a mandatory |
2127 | option when using cpuio I/O engine. | |
f80dba8d MT |
2128 | |
2129 | .. option:: cpuchunks=int : [cpuio] | |
2130 | ||
2131 | Split the load into cycles of the given time. In microseconds. | |
2132 | ||
2133 | .. option:: exit_on_io_done=bool : [cpuio] | |
2134 | ||
2135 | Detect when I/O threads are done, then exit. | |
2136 | ||
f80dba8d MT |
2137 | .. option:: namenode=str : [libhdfs] |
2138 | ||
22413915 | 2139 | The hostname or IP address of a HDFS cluster namenode to contact. |
f80dba8d MT |
2140 | |
2141 | .. option:: port=int | |
2142 | ||
f50fbdda TK |
2143 | [libhdfs] |
2144 | ||
2145 | The listening port of the HFDS cluster namenode. | |
2146 | ||
f80dba8d MT |
2147 | [netsplice], [net] |
2148 | ||
2149 | The TCP or UDP port to bind to or connect to. If this is used with | |
2150 | :option:`numjobs` to spawn multiple instances of the same job type, then | |
2151 | this will be the starting port number since fio will use a range of | |
2152 | ports. | |
2153 | ||
609ac152 SB |
2154 | [rdma] |
2155 | ||
2156 | The port to use for RDMA-CM communication. This should be the same value | |
2157 | on the client and the server side. | |
2158 | ||
2159 | .. option:: hostname=str : [netsplice] [net] [rdma] | |
f80dba8d | 2160 | |
609ac152 SB |
2161 | The hostname or IP address to use for TCP, UDP or RDMA-CM based I/O. If the job |
2162 | is a TCP listener or UDP reader, the hostname is not used and must be omitted | |
f50fbdda | 2163 | unless it is a valid UDP multicast address. |
f80dba8d MT |
2164 | |
2165 | .. option:: interface=str : [netsplice] [net] | |
2166 | ||
2167 | The IP address of the network interface used to send or receive UDP | |
2168 | multicast. | |
2169 | ||
2170 | .. option:: ttl=int : [netsplice] [net] | |
2171 | ||
2172 | Time-to-live value for outgoing UDP multicast packets. Default: 1. | |
2173 | ||
2174 | .. option:: nodelay=bool : [netsplice] [net] | |
2175 | ||
2176 | Set TCP_NODELAY on TCP connections. | |
2177 | ||
f50fbdda | 2178 | .. option:: protocol=str, proto=str : [netsplice] [net] |
f80dba8d MT |
2179 | |
2180 | The network protocol to use. Accepted values are: | |
2181 | ||
2182 | **tcp** | |
2183 | Transmission control protocol. | |
2184 | **tcpv6** | |
2185 | Transmission control protocol V6. | |
2186 | **udp** | |
2187 | User datagram protocol. | |
2188 | **udpv6** | |
2189 | User datagram protocol V6. | |
2190 | **unix** | |
2191 | UNIX domain socket. | |
2192 | ||
2193 | When the protocol is TCP or UDP, the port must also be given, as well as the | |
2194 | hostname if the job is a TCP listener or UDP reader. For unix sockets, the | |
f50fbdda | 2195 | normal :option:`filename` option should be used and the port is invalid. |
f80dba8d | 2196 | |
e9184ec1 | 2197 | .. option:: listen : [netsplice] [net] |
f80dba8d MT |
2198 | |
2199 | For TCP network connections, tell fio to listen for incoming connections | |
2200 | rather than initiating an outgoing connection. The :option:`hostname` must | |
2201 | be omitted if this option is used. | |
2202 | ||
e9184ec1 | 2203 | .. option:: pingpong : [netsplice] [net] |
f80dba8d MT |
2204 | |
2205 | Normally a network writer will just continue writing data, and a network | |
2206 | reader will just consume packages. If ``pingpong=1`` is set, a writer will | |
2207 | send its normal payload to the reader, then wait for the reader to send the | |
2208 | same payload back. This allows fio to measure network latencies. The | |
2209 | submission and completion latencies then measure local time spent sending or | |
2210 | receiving, and the completion latency measures how long it took for the | |
2211 | other end to receive and send back. For UDP multicast traffic | |
2212 | ``pingpong=1`` should only be set for a single reader when multiple readers | |
2213 | are listening to the same address. | |
2214 | ||
e9184ec1 | 2215 | .. option:: window_size : [netsplice] [net] |
f80dba8d MT |
2216 | |
2217 | Set the desired socket buffer size for the connection. | |
2218 | ||
e9184ec1 | 2219 | .. option:: mss : [netsplice] [net] |
f80dba8d MT |
2220 | |
2221 | Set the TCP maximum segment size (TCP_MAXSEG). | |
2222 | ||
2223 | .. option:: donorname=str : [e4defrag] | |
2224 | ||
730bd7d9 | 2225 | File will be used as a block donor (swap extents between files). |
f80dba8d MT |
2226 | |
2227 | .. option:: inplace=int : [e4defrag] | |
2228 | ||
2229 | Configure donor file blocks allocation strategy: | |
2230 | ||
2231 | **0** | |
2232 | Default. Preallocate donor's file on init. | |
2233 | **1** | |
2b455dbf | 2234 | Allocate space immediately inside defragment event, and free right |
f80dba8d MT |
2235 | after event. |
2236 | ||
f3f96717 | 2237 | .. option:: clustername=str : [rbd,rados] |
f80dba8d MT |
2238 | |
2239 | Specifies the name of the Ceph cluster. | |
2240 | ||
2241 | .. option:: rbdname=str : [rbd] | |
2242 | ||
2243 | Specifies the name of the RBD. | |
2244 | ||
f3f96717 | 2245 | .. option:: pool=str : [rbd,rados] |
f80dba8d | 2246 | |
f3f96717 | 2247 | Specifies the name of the Ceph pool containing RBD or RADOS data. |
f80dba8d | 2248 | |
f3f96717 | 2249 | .. option:: clientname=str : [rbd,rados] |
f80dba8d MT |
2250 | |
2251 | Specifies the username (without the 'client.' prefix) used to access the | |
2252 | Ceph cluster. If the *clustername* is specified, the *clientname* shall be | |
2253 | the full *type.id* string. If no type. prefix is given, fio will add | |
2254 | 'client.' by default. | |
2255 | ||
f3f96717 IF |
2256 | .. option:: busy_poll=bool : [rbd,rados] |
2257 | ||
2258 | Poll store instead of waiting for completion. Usually this provides better | |
2259 | throughput at cost of higher(up to 100%) CPU utilization. | |
2260 | ||
f80dba8d MT |
2261 | .. option:: skip_bad=bool : [mtd] |
2262 | ||
2263 | Skip operations against known bad blocks. | |
2264 | ||
2265 | .. option:: hdfsdirectory : [libhdfs] | |
2266 | ||
2267 | libhdfs will create chunk in this HDFS directory. | |
2268 | ||
2269 | .. option:: chunk_size : [libhdfs] | |
2270 | ||
2b455dbf | 2271 | The size of the chunk to use for each file. |
f80dba8d | 2272 | |
609ac152 SB |
2273 | .. option:: verb=str : [rdma] |
2274 | ||
2275 | The RDMA verb to use on this side of the RDMA ioengine connection. Valid | |
2276 | values are write, read, send and recv. These correspond to the equivalent | |
2277 | RDMA verbs (e.g. write = rdma_write etc.). Note that this only needs to be | |
2278 | specified on the client side of the connection. See the examples folder. | |
2279 | ||
2280 | .. option:: bindname=str : [rdma] | |
2281 | ||
2282 | The name to use to bind the local RDMA-CM connection to a local RDMA device. | |
2283 | This could be a hostname or an IPv4 or IPv6 address. On the server side this | |
2284 | will be passed into the rdma_bind_addr() function and on the client site it | |
2285 | will be used in the rdma_resolve_add() function. This can be useful when | |
2286 | multiple paths exist between the client and the server or in certain loopback | |
2287 | configurations. | |
f80dba8d | 2288 | |
93a13ba5 | 2289 | .. option:: stat_type=str : [filestat] |
c446eff0 | 2290 | |
93a13ba5 TK |
2291 | Specify stat system call type to measure lookup/getattr performance. |
2292 | Default is **stat** for :manpage:`stat(2)`. | |
c446eff0 | 2293 | |
52b81b7c KD |
2294 | .. option:: readfua=bool : [sg] |
2295 | ||
2296 | With readfua option set to 1, read operations include | |
2297 | the force unit access (fua) flag. Default is 0. | |
2298 | ||
2299 | .. option:: writefua=bool : [sg] | |
2300 | ||
2301 | With writefua option set to 1, write operations include | |
2302 | the force unit access (fua) flag. Default is 0. | |
2303 | ||
2c3a9150 | 2304 | .. option:: sg_write_mode=str : [sg] |
3740cfc8 | 2305 | |
2c3a9150 VF |
2306 | Specify the type of write commands to issue. This option can take three values: |
2307 | ||
2308 | **write** | |
2309 | This is the default where write opcodes are issued as usual. | |
2310 | **verify** | |
2311 | Issue WRITE AND VERIFY commands. The BYTCHK bit is set to 0. This | |
2312 | directs the device to carry out a medium verification with no data | |
2313 | comparison. The writefua option is ignored with this selection. | |
2314 | **same** | |
2315 | Issue WRITE SAME commands. This transfers a single block to the device | |
2316 | and writes this same block of data to a contiguous sequence of LBAs | |
2317 | beginning at the specified offset. fio's block size parameter specifies | |
2318 | the amount of data written with each command. However, the amount of data | |
2319 | actually transferred to the device is equal to the device's block | |
2320 | (sector) size. For a device with 512 byte sectors, blocksize=8k will | |
2321 | write 16 sectors with each command. fio will still generate 8k of data | |
2322 | for each command but only the first 512 bytes will be used and | |
2323 | transferred to the device. The writefua option is ignored with this | |
2324 | selection. | |
52b81b7c | 2325 | |
c2f6a13d LMB |
2326 | .. option:: http_host=str : [http] |
2327 | ||
2328 | Hostname to connect to. For S3, this could be the bucket hostname. | |
2329 | Default is **localhost** | |
2330 | ||
2331 | .. option:: http_user=str : [http] | |
2332 | ||
2333 | Username for HTTP authentication. | |
2334 | ||
2335 | .. option:: http_pass=str : [http] | |
2336 | ||
2337 | Password for HTTP authentication. | |
2338 | ||
09fd2966 | 2339 | .. option:: https=str : [http] |
c2f6a13d | 2340 | |
09fd2966 LMB |
2341 | Enable HTTPS instead of http. *on* enables HTTPS; *insecure* |
2342 | will enable HTTPS, but disable SSL peer verification (use with | |
2343 | caution!). Default is **off** | |
c2f6a13d | 2344 | |
09fd2966 | 2345 | .. option:: http_mode=str : [http] |
c2f6a13d | 2346 | |
09fd2966 LMB |
2347 | Which HTTP access mode to use: *webdav*, *swift*, or *s3*. |
2348 | Default is **webdav** | |
c2f6a13d LMB |
2349 | |
2350 | .. option:: http_s3_region=str : [http] | |
2351 | ||
2352 | The S3 region/zone string. | |
2353 | Default is **us-east-1** | |
2354 | ||
2355 | .. option:: http_s3_key=str : [http] | |
2356 | ||
2357 | The S3 secret key. | |
2358 | ||
2359 | .. option:: http_s3_keyid=str : [http] | |
2360 | ||
2361 | The S3 key/access id. | |
2362 | ||
09fd2966 LMB |
2363 | .. option:: http_swift_auth_token=str : [http] |
2364 | ||
2365 | The Swift auth token. See the example configuration file on how | |
2366 | to retrieve this. | |
2367 | ||
c2f6a13d LMB |
2368 | .. option:: http_verbose=int : [http] |
2369 | ||
2370 | Enable verbose requests from libcurl. Useful for debugging. 1 | |
2371 | turns on verbose logging from libcurl, 2 additionally enables | |
2372 | HTTP IO tracing. Default is **0** | |
2373 | ||
f2d6de5d RJ |
2374 | .. option:: uri=str : [nbd] |
2375 | ||
2376 | Specify the NBD URI of the server to test. The string | |
2377 | is a standard NBD URI | |
2378 | (see https://github.com/NetworkBlockDevice/nbd/tree/master/doc). | |
2379 | Example URIs: nbd://localhost:10809 | |
2380 | nbd+unix:///?socket=/tmp/socket | |
2381 | nbds://tlshost/exportname | |
2382 | ||
f80dba8d MT |
2383 | I/O depth |
2384 | ~~~~~~~~~ | |
2385 | ||
2386 | .. option:: iodepth=int | |
2387 | ||
2388 | Number of I/O units to keep in flight against the file. Note that | |
2389 | increasing *iodepth* beyond 1 will not affect synchronous ioengines (except | |
c60ebc45 | 2390 | for small degrees when :option:`verify_async` is in use). Even async |
f80dba8d MT |
2391 | engines may impose OS restrictions causing the desired depth not to be |
2392 | achieved. This may happen on Linux when using libaio and not setting | |
9207a0cb | 2393 | :option:`direct`\=1, since buffered I/O is not async on that OS. Keep an |
f80dba8d MT |
2394 | eye on the I/O depth distribution in the fio output to verify that the |
2395 | achieved depth is as expected. Default: 1. | |
2396 | ||
2397 | .. option:: iodepth_batch_submit=int, iodepth_batch=int | |
2398 | ||
2399 | This defines how many pieces of I/O to submit at once. It defaults to 1 | |
2400 | which means that we submit each I/O as soon as it is available, but can be | |
2401 | raised to submit bigger batches of I/O at the time. If it is set to 0 the | |
2402 | :option:`iodepth` value will be used. | |
2403 | ||
2404 | .. option:: iodepth_batch_complete_min=int, iodepth_batch_complete=int | |
2405 | ||
2406 | This defines how many pieces of I/O to retrieve at once. It defaults to 1 | |
2407 | which means that we'll ask for a minimum of 1 I/O in the retrieval process | |
2408 | from the kernel. The I/O retrieval will go on until we hit the limit set by | |
2409 | :option:`iodepth_low`. If this variable is set to 0, then fio will always | |
2410 | check for completed events before queuing more I/O. This helps reduce I/O | |
2411 | latency, at the cost of more retrieval system calls. | |
2412 | ||
2413 | .. option:: iodepth_batch_complete_max=int | |
2414 | ||
2415 | This defines maximum pieces of I/O to retrieve at once. This variable should | |
9207a0cb | 2416 | be used along with :option:`iodepth_batch_complete_min`\=int variable, |
f80dba8d | 2417 | specifying the range of min and max amount of I/O which should be |
730bd7d9 | 2418 | retrieved. By default it is equal to the :option:`iodepth_batch_complete_min` |
f80dba8d MT |
2419 | value. |
2420 | ||
2421 | Example #1:: | |
2422 | ||
2423 | iodepth_batch_complete_min=1 | |
2424 | iodepth_batch_complete_max=<iodepth> | |
2425 | ||
2426 | which means that we will retrieve at least 1 I/O and up to the whole | |
2427 | submitted queue depth. If none of I/O has been completed yet, we will wait. | |
2428 | ||
2429 | Example #2:: | |
2430 | ||
2431 | iodepth_batch_complete_min=0 | |
2432 | iodepth_batch_complete_max=<iodepth> | |
2433 | ||
2434 | which means that we can retrieve up to the whole submitted queue depth, but | |
2435 | if none of I/O has been completed yet, we will NOT wait and immediately exit | |
2436 | the system call. In this example we simply do polling. | |
2437 | ||
2438 | .. option:: iodepth_low=int | |
2439 | ||
2440 | The low water mark indicating when to start filling the queue | |
2441 | again. Defaults to the same as :option:`iodepth`, meaning that fio will | |
2442 | attempt to keep the queue full at all times. If :option:`iodepth` is set to | |
c60ebc45 | 2443 | e.g. 16 and *iodepth_low* is set to 4, then after fio has filled the queue of |
f80dba8d MT |
2444 | 16 requests, it will let the depth drain down to 4 before starting to fill |
2445 | it again. | |
2446 | ||
997b5680 SW |
2447 | .. option:: serialize_overlap=bool |
2448 | ||
2449 | Serialize in-flight I/Os that might otherwise cause or suffer from data races. | |
2450 | When two or more I/Os are submitted simultaneously, there is no guarantee that | |
2451 | the I/Os will be processed or completed in the submitted order. Further, if | |
2452 | two or more of those I/Os are writes, any overlapping region between them can | |
2453 | become indeterminate/undefined on certain storage. These issues can cause | |
2454 | verification to fail erratically when at least one of the racing I/Os is | |
2455 | changing data and the overlapping region has a non-zero size. Setting | |
2456 | ``serialize_overlap`` tells fio to avoid provoking this behavior by explicitly | |
2457 | serializing in-flight I/Os that have a non-zero overlap. Note that setting | |
ee21ebee | 2458 | this option can reduce both performance and the :option:`iodepth` achieved. |
3d6a6f04 VF |
2459 | |
2460 | This option only applies to I/Os issued for a single job except when it is | |
a02ec45a | 2461 | enabled along with :option:`io_submit_mode`\=offload. In offload mode, fio |
3d6a6f04 | 2462 | will check for overlap among all I/Os submitted by offload jobs with :option:`serialize_overlap` |
307f2246 | 2463 | enabled. |
3d6a6f04 VF |
2464 | |
2465 | Default: false. | |
997b5680 | 2466 | |
f80dba8d MT |
2467 | .. option:: io_submit_mode=str |
2468 | ||
2469 | This option controls how fio submits the I/O to the I/O engine. The default | |
2470 | is `inline`, which means that the fio job threads submit and reap I/O | |
2471 | directly. If set to `offload`, the job threads will offload I/O submission | |
2472 | to a dedicated pool of I/O threads. This requires some coordination and thus | |
2473 | has a bit of extra overhead, especially for lower queue depth I/O where it | |
2474 | can increase latencies. The benefit is that fio can manage submission rates | |
2475 | independently of the device completion rates. This avoids skewed latency | |
730bd7d9 | 2476 | reporting if I/O gets backed up on the device side (the coordinated omission |
abfd235a JA |
2477 | problem). Note that this option cannot reliably be used with async IO |
2478 | engines. | |
f80dba8d MT |
2479 | |
2480 | ||
2481 | I/O rate | |
2482 | ~~~~~~~~ | |
2483 | ||
a881438b | 2484 | .. option:: thinktime=time |
f80dba8d | 2485 | |
f75ede1d SW |
2486 | Stall the job for the specified period of time after an I/O has completed before issuing the |
2487 | next. May be used to simulate processing being done by an application. | |
947e0fe0 | 2488 | When the unit is omitted, the value is interpreted in microseconds. See |
f80dba8d MT |
2489 | :option:`thinktime_blocks` and :option:`thinktime_spin`. |
2490 | ||
a881438b | 2491 | .. option:: thinktime_spin=time |
f80dba8d MT |
2492 | |
2493 | Only valid if :option:`thinktime` is set - pretend to spend CPU time doing | |
2494 | something with the data received, before falling back to sleeping for the | |
f75ede1d | 2495 | rest of the period specified by :option:`thinktime`. When the unit is |
947e0fe0 | 2496 | omitted, the value is interpreted in microseconds. |
f80dba8d MT |
2497 | |
2498 | .. option:: thinktime_blocks=int | |
2499 | ||
2500 | Only valid if :option:`thinktime` is set - control how many blocks to issue, | |
f50fbdda TK |
2501 | before waiting :option:`thinktime` usecs. If not set, defaults to 1 which will make |
2502 | fio wait :option:`thinktime` usecs after every block. This effectively makes any | |
f80dba8d | 2503 | queue depth setting redundant, since no more than 1 I/O will be queued |
f50fbdda | 2504 | before we have to complete it and do our :option:`thinktime`. In other words, this |
f80dba8d | 2505 | setting effectively caps the queue depth if the latter is larger. |
71bfa161 | 2506 | |
f80dba8d | 2507 | .. option:: rate=int[,int][,int] |
71bfa161 | 2508 | |
f80dba8d MT |
2509 | Cap the bandwidth used by this job. The number is in bytes/sec, the normal |
2510 | suffix rules apply. Comma-separated values may be specified for reads, | |
2511 | writes, and trims as described in :option:`blocksize`. | |
71bfa161 | 2512 | |
b25b3464 SW |
2513 | For example, using `rate=1m,500k` would limit reads to 1MiB/sec and writes to |
2514 | 500KiB/sec. Capping only reads or writes can be done with `rate=,500k` or | |
2515 | `rate=500k,` where the former will only limit writes (to 500KiB/sec) and the | |
2516 | latter will only limit reads. | |
2517 | ||
f80dba8d | 2518 | .. option:: rate_min=int[,int][,int] |
71bfa161 | 2519 | |
f80dba8d MT |
2520 | Tell fio to do whatever it can to maintain at least this bandwidth. Failing |
2521 | to meet this requirement will cause the job to exit. Comma-separated values | |
2522 | may be specified for reads, writes, and trims as described in | |
2523 | :option:`blocksize`. | |
71bfa161 | 2524 | |
f80dba8d | 2525 | .. option:: rate_iops=int[,int][,int] |
71bfa161 | 2526 | |
f80dba8d MT |
2527 | Cap the bandwidth to this number of IOPS. Basically the same as |
2528 | :option:`rate`, just specified independently of bandwidth. If the job is | |
2529 | given a block size range instead of a fixed value, the smallest block size | |
2530 | is used as the metric. Comma-separated values may be specified for reads, | |
2531 | writes, and trims as described in :option:`blocksize`. | |
71bfa161 | 2532 | |
f80dba8d | 2533 | .. option:: rate_iops_min=int[,int][,int] |
71bfa161 | 2534 | |
f80dba8d MT |
2535 | If fio doesn't meet this rate of I/O, it will cause the job to exit. |
2536 | Comma-separated values may be specified for reads, writes, and trims as | |
2537 | described in :option:`blocksize`. | |
71bfa161 | 2538 | |
f80dba8d | 2539 | .. option:: rate_process=str |
66c098b8 | 2540 | |
f80dba8d MT |
2541 | This option controls how fio manages rated I/O submissions. The default is |
2542 | `linear`, which submits I/O in a linear fashion with fixed delays between | |
c60ebc45 | 2543 | I/Os that gets adjusted based on I/O completion rates. If this is set to |
f80dba8d MT |
2544 | `poisson`, fio will submit I/O based on a more real world random request |
2545 | flow, known as the Poisson process | |
2546 | (https://en.wikipedia.org/wiki/Poisson_point_process). The lambda will be | |
2547 | 10^6 / IOPS for the given workload. | |
71bfa161 | 2548 | |
1a9bf814 JA |
2549 | .. option:: rate_ignore_thinktime=bool |
2550 | ||
2551 | By default, fio will attempt to catch up to the specified rate setting, | |
2552 | if any kind of thinktime setting was used. If this option is set, then | |
2553 | fio will ignore the thinktime and continue doing IO at the specified | |
2554 | rate, instead of entering a catch-up mode after thinktime is done. | |
2555 | ||
71bfa161 | 2556 | |
f80dba8d MT |
2557 | I/O latency |
2558 | ~~~~~~~~~~~ | |
71bfa161 | 2559 | |
a881438b | 2560 | .. option:: latency_target=time |
71bfa161 | 2561 | |
f80dba8d | 2562 | If set, fio will attempt to find the max performance point that the given |
f75ede1d | 2563 | workload will run at while maintaining a latency below this target. When |
947e0fe0 | 2564 | the unit is omitted, the value is interpreted in microseconds. See |
f75ede1d | 2565 | :option:`latency_window` and :option:`latency_percentile`. |
71bfa161 | 2566 | |
a881438b | 2567 | .. option:: latency_window=time |
71bfa161 | 2568 | |
f80dba8d | 2569 | Used with :option:`latency_target` to specify the sample window that the job |
f75ede1d | 2570 | is run at varying queue depths to test the performance. When the unit is |
947e0fe0 | 2571 | omitted, the value is interpreted in microseconds. |
b4692828 | 2572 | |
f80dba8d | 2573 | .. option:: latency_percentile=float |
71bfa161 | 2574 | |
c60ebc45 | 2575 | The percentage of I/Os that must fall within the criteria specified by |
f80dba8d | 2576 | :option:`latency_target` and :option:`latency_window`. If not set, this |
c60ebc45 | 2577 | defaults to 100.0, meaning that all I/Os must be equal or below to the value |
f80dba8d | 2578 | set by :option:`latency_target`. |
71bfa161 | 2579 | |
e1bcd541 SL |
2580 | .. option:: latency_run=bool |
2581 | ||
2582 | Used with :option:`latency_target`. If false (default), fio will find | |
2583 | the highest queue depth that meets :option:`latency_target` and exit. If | |
2584 | true, fio will continue running and try to meet :option:`latency_target` | |
2585 | by adjusting queue depth. | |
2586 | ||
a881438b | 2587 | .. option:: max_latency=time |
71bfa161 | 2588 | |
f75ede1d | 2589 | If set, fio will exit the job with an ETIMEDOUT error if it exceeds this |
947e0fe0 | 2590 | maximum latency. When the unit is omitted, the value is interpreted in |
f75ede1d | 2591 | microseconds. |
71bfa161 | 2592 | |
f80dba8d | 2593 | .. option:: rate_cycle=int |
71bfa161 | 2594 | |
f80dba8d | 2595 | Average bandwidth for :option:`rate` and :option:`rate_min` over this number |
a47b697c | 2596 | of milliseconds. Defaults to 1000. |
71bfa161 | 2597 | |
71bfa161 | 2598 | |
f80dba8d MT |
2599 | I/O replay |
2600 | ~~~~~~~~~~ | |
71bfa161 | 2601 | |
f80dba8d | 2602 | .. option:: write_iolog=str |
c2b1e753 | 2603 | |
f80dba8d MT |
2604 | Write the issued I/O patterns to the specified file. See |
2605 | :option:`read_iolog`. Specify a separate file for each job, otherwise the | |
2606 | iologs will be interspersed and the file may be corrupt. | |
c2b1e753 | 2607 | |
f80dba8d | 2608 | .. option:: read_iolog=str |
71bfa161 | 2609 | |
22413915 | 2610 | Open an iolog with the specified filename and replay the I/O patterns it |
f80dba8d MT |
2611 | contains. This can be used to store a workload and replay it sometime |
2612 | later. The iolog given may also be a blktrace binary file, which allows fio | |
2613 | to replay a workload captured by :command:`blktrace`. See | |
2614 | :manpage:`blktrace(8)` for how to capture such logging data. For blktrace | |
2615 | replay, the file needs to be turned into a blkparse binary data file first | |
2616 | (``blkparse <device> -o /dev/null -d file_for_fio.bin``). | |
78439a18 JA |
2617 | You can specify a number of files by separating the names with a ':' |
2618 | character. See the :option:`filename` option for information on how to | |
3b803fe1 | 2619 | escape ':' characters within the file names. These files will |
78439a18 | 2620 | be sequentially assigned to job clones created by :option:`numjobs`. |
d19c04d1 | 2621 | '-' is a reserved name, meaning read from stdin, notably if |
2622 | :option:`filename` is set to '-' which means stdin as well, then | |
2623 | this flag can't be set to '-'. | |
71bfa161 | 2624 | |
77be374d AK |
2625 | .. option:: read_iolog_chunked=bool |
2626 | ||
2627 | Determines how iolog is read. If false(default) entire :option:`read_iolog` | |
2628 | will be read at once. If selected true, input from iolog will be read | |
2629 | gradually. Useful when iolog is very large, or it is generated. | |
2630 | ||
b9921d1a DZ |
2631 | .. option:: merge_blktrace_file=str |
2632 | ||
2633 | When specified, rather than replaying the logs passed to :option:`read_iolog`, | |
2634 | the logs go through a merge phase which aggregates them into a single | |
2635 | blktrace. The resulting file is then passed on as the :option:`read_iolog` | |
2636 | parameter. The intention here is to make the order of events consistent. | |
2637 | This limits the influence of the scheduler compared to replaying multiple | |
2638 | blktraces via concurrent jobs. | |
2639 | ||
87a48ada DZ |
2640 | .. option:: merge_blktrace_scalars=float_list |
2641 | ||
2642 | This is a percentage based option that is index paired with the list of | |
2643 | files passed to :option:`read_iolog`. When merging is performed, scale | |
2644 | the time of each event by the corresponding amount. For example, | |
2645 | ``--merge_blktrace_scalars="50:100"`` runs the first trace in halftime | |
2646 | and the second trace in realtime. This knob is separately tunable from | |
2647 | :option:`replay_time_scale` which scales the trace during runtime and | |
2648 | does not change the output of the merge unlike this option. | |
2649 | ||
55bfd8c8 DZ |
2650 | .. option:: merge_blktrace_iters=float_list |
2651 | ||
2652 | This is a whole number option that is index paired with the list of files | |
2653 | passed to :option:`read_iolog`. When merging is performed, run each trace | |
2654 | for the specified number of iterations. For example, | |
2655 | ``--merge_blktrace_iters="2:1"`` runs the first trace for two iterations | |
2656 | and the second trace for one iteration. | |
2657 | ||
589e88b7 | 2658 | .. option:: replay_no_stall=bool |
71bfa161 | 2659 | |
f80dba8d | 2660 | When replaying I/O with :option:`read_iolog` the default behavior is to |
22413915 | 2661 | attempt to respect the timestamps within the log and replay them with the |
f80dba8d MT |
2662 | appropriate delay between IOPS. By setting this variable fio will not |
2663 | respect the timestamps and attempt to replay them as fast as possible while | |
2664 | still respecting ordering. The result is the same I/O pattern to a given | |
2665 | device, but different timings. | |
71bfa161 | 2666 | |
6dd7fa77 JA |
2667 | .. option:: replay_time_scale=int |
2668 | ||
2669 | When replaying I/O with :option:`read_iolog`, fio will honor the | |
2670 | original timing in the trace. With this option, it's possible to scale | |
2671 | the time. It's a percentage option, if set to 50 it means run at 50% | |
2672 | the original IO rate in the trace. If set to 200, run at twice the | |
2673 | original IO rate. Defaults to 100. | |
2674 | ||
f80dba8d | 2675 | .. option:: replay_redirect=str |
b4692828 | 2676 | |
f80dba8d MT |
2677 | While replaying I/O patterns using :option:`read_iolog` the default behavior |
2678 | is to replay the IOPS onto the major/minor device that each IOP was recorded | |
2679 | from. This is sometimes undesirable because on a different machine those | |
2680 | major/minor numbers can map to a different device. Changing hardware on the | |
2681 | same system can also result in a different major/minor mapping. | |
730bd7d9 | 2682 | ``replay_redirect`` causes all I/Os to be replayed onto the single specified |
f80dba8d | 2683 | device regardless of the device it was recorded |
9207a0cb | 2684 | from. i.e. :option:`replay_redirect`\= :file:`/dev/sdc` would cause all I/O |
f80dba8d MT |
2685 | in the blktrace or iolog to be replayed onto :file:`/dev/sdc`. This means |
2686 | multiple devices will be replayed onto a single device, if the trace | |
2687 | contains multiple devices. If you want multiple devices to be replayed | |
2688 | concurrently to multiple redirected devices you must blkparse your trace | |
2689 | into separate traces and replay them with independent fio invocations. | |
2690 | Unfortunately this also breaks the strict time ordering between multiple | |
2691 | device accesses. | |
71bfa161 | 2692 | |
f80dba8d | 2693 | .. option:: replay_align=int |
74929ac2 | 2694 | |
350a535d DZ |
2695 | Force alignment of the byte offsets in a trace to this value. The value |
2696 | must be a power of 2. | |
3c54bc46 | 2697 | |
f80dba8d | 2698 | .. option:: replay_scale=int |
3c54bc46 | 2699 | |
350a535d DZ |
2700 | Scale byte offsets down by this factor when replaying traces. Should most |
2701 | likely use :option:`replay_align` as well. | |
3c54bc46 | 2702 | |
38f68906 JA |
2703 | .. option:: replay_skip=str |
2704 | ||
2705 | Sometimes it's useful to skip certain IO types in a replay trace. | |
2706 | This could be, for instance, eliminating the writes in the trace. | |
2707 | Or not replaying the trims/discards, if you are redirecting to | |
2708 | a device that doesn't support them. This option takes a comma | |
2709 | separated list of read, write, trim, sync. | |
2710 | ||
3c54bc46 | 2711 | |
f80dba8d MT |
2712 | Threads, processes and job synchronization |
2713 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
3c54bc46 | 2714 | |
f80dba8d | 2715 | .. option:: thread |
3c54bc46 | 2716 | |
730bd7d9 SW |
2717 | Fio defaults to creating jobs by using fork, however if this option is |
2718 | given, fio will create jobs by using POSIX Threads' function | |
2719 | :manpage:`pthread_create(3)` to create threads instead. | |
71bfa161 | 2720 | |
f80dba8d | 2721 | .. option:: wait_for=str |
74929ac2 | 2722 | |
730bd7d9 SW |
2723 | If set, the current job won't be started until all workers of the specified |
2724 | waitee job are done. | |
74929ac2 | 2725 | |
f80dba8d MT |
2726 | ``wait_for`` operates on the job name basis, so there are a few |
2727 | limitations. First, the waitee must be defined prior to the waiter job | |
2728 | (meaning no forward references). Second, if a job is being referenced as a | |
2729 | waitee, it must have a unique name (no duplicate waitees). | |
74929ac2 | 2730 | |
f80dba8d | 2731 | .. option:: nice=int |
892a6ffc | 2732 | |
f80dba8d | 2733 | Run the job with the given nice value. See man :manpage:`nice(2)`. |
892a6ffc | 2734 | |
f80dba8d MT |
2735 | On Windows, values less than -15 set the process class to "High"; -1 through |
2736 | -15 set "Above Normal"; 1 through 15 "Below Normal"; and above 15 "Idle" | |
2737 | priority class. | |
74929ac2 | 2738 | |
f80dba8d | 2739 | .. option:: prio=int |
71bfa161 | 2740 | |
f80dba8d MT |
2741 | Set the I/O priority value of this job. Linux limits us to a positive value |
2742 | between 0 and 7, with 0 being the highest. See man | |
2743 | :manpage:`ionice(1)`. Refer to an appropriate manpage for other operating | |
b2a432bf PC |
2744 | systems since meaning of priority may differ. For per-command priority |
2745 | setting, see I/O engine specific `cmdprio_percentage` and `hipri_percentage` | |
2746 | options. | |
71bfa161 | 2747 | |
f80dba8d | 2748 | .. option:: prioclass=int |
d59aa780 | 2749 | |
b2a432bf PC |
2750 | Set the I/O priority class. See man :manpage:`ionice(1)`. For per-command |
2751 | priority setting, see I/O engine specific `cmdprio_percentage` and | |
2752 | `hipri_percentage` options. | |
d59aa780 | 2753 | |
f80dba8d | 2754 | .. option:: cpus_allowed=str |
6d500c2e | 2755 | |
730bd7d9 | 2756 | Controls the same options as :option:`cpumask`, but accepts a textual |
b570e037 SW |
2757 | specification of the permitted CPUs instead and CPUs are indexed from 0. So |
2758 | to use CPUs 0 and 5 you would specify ``cpus_allowed=0,5``. This option also | |
2759 | allows a range of CPUs to be specified -- say you wanted a binding to CPUs | |
2760 | 0, 5, and 8 to 15, you would set ``cpus_allowed=0,5,8-15``. | |
2761 | ||
2762 | On Windows, when ``cpus_allowed`` is unset only CPUs from fio's current | |
2763 | processor group will be used and affinity settings are inherited from the | |
2764 | system. An fio build configured to target Windows 7 makes options that set | |
2765 | CPUs processor group aware and values will set both the processor group | |
2766 | and a CPU from within that group. For example, on a system where processor | |
2767 | group 0 has 40 CPUs and processor group 1 has 32 CPUs, ``cpus_allowed`` | |
2768 | values between 0 and 39 will bind CPUs from processor group 0 and | |
2769 | ``cpus_allowed`` values between 40 and 71 will bind CPUs from processor | |
2770 | group 1. When using ``cpus_allowed_policy=shared`` all CPUs specified by a | |
2771 | single ``cpus_allowed`` option must be from the same processor group. For | |
2772 | Windows fio builds not built for Windows 7, CPUs will only be selected from | |
2773 | (and be relative to) whatever processor group fio happens to be running in | |
2774 | and CPUs from other processor groups cannot be used. | |
6d500c2e | 2775 | |
f80dba8d | 2776 | .. option:: cpus_allowed_policy=str |
6d500c2e | 2777 | |
f80dba8d | 2778 | Set the policy of how fio distributes the CPUs specified by |
730bd7d9 | 2779 | :option:`cpus_allowed` or :option:`cpumask`. Two policies are supported: |
6d500c2e | 2780 | |
f80dba8d MT |
2781 | **shared** |
2782 | All jobs will share the CPU set specified. | |
2783 | **split** | |
2784 | Each job will get a unique CPU from the CPU set. | |
6d500c2e | 2785 | |
22413915 | 2786 | **shared** is the default behavior, if the option isn't specified. If |
b21fc93f | 2787 | **split** is specified, then fio will assign one cpu per job. If not |
f80dba8d MT |
2788 | enough CPUs are given for the jobs listed, then fio will roundrobin the CPUs |
2789 | in the set. | |
6d500c2e | 2790 | |
b570e037 SW |
2791 | .. option:: cpumask=int |
2792 | ||
2793 | Set the CPU affinity of this job. The parameter given is a bit mask of | |
2794 | allowed CPUs the job may run on. So if you want the allowed CPUs to be 1 | |
2795 | and 5, you would pass the decimal value of (1 << 1 | 1 << 5), or 34. See man | |
2796 | :manpage:`sched_setaffinity(2)`. This may not work on all supported | |
2797 | operating systems or kernel versions. This option doesn't work well for a | |
2798 | higher CPU count than what you can store in an integer mask, so it can only | |
2799 | control cpus 1-32. For boxes with larger CPU counts, use | |
2800 | :option:`cpus_allowed`. | |
2801 | ||
f80dba8d | 2802 | .. option:: numa_cpu_nodes=str |
6d500c2e | 2803 | |
f80dba8d MT |
2804 | Set this job running on specified NUMA nodes' CPUs. The arguments allow |
2805 | comma delimited list of cpu numbers, A-B ranges, or `all`. Note, to enable | |
ac8ca2af | 2806 | NUMA options support, fio must be built on a system with libnuma-dev(el) |
f80dba8d | 2807 | installed. |
61b9861d | 2808 | |
f80dba8d | 2809 | .. option:: numa_mem_policy=str |
61b9861d | 2810 | |
f80dba8d MT |
2811 | Set this job's memory policy and corresponding NUMA nodes. Format of the |
2812 | arguments:: | |
5c94b008 | 2813 | |
f80dba8d | 2814 | <mode>[:<nodelist>] |
ce35b1ec | 2815 | |
804c0839 | 2816 | ``mode`` is one of the following memory policies: ``default``, ``prefer``, |
730bd7d9 SW |
2817 | ``bind``, ``interleave`` or ``local``. For ``default`` and ``local`` memory |
2818 | policies, no node needs to be specified. For ``prefer``, only one node is | |
2819 | allowed. For ``bind`` and ``interleave`` the ``nodelist`` may be as | |
2820 | follows: a comma delimited list of numbers, A-B ranges, or `all`. | |
71bfa161 | 2821 | |
f80dba8d | 2822 | .. option:: cgroup=str |
390b1537 | 2823 | |
f80dba8d MT |
2824 | Add job to this control group. If it doesn't exist, it will be created. The |
2825 | system must have a mounted cgroup blkio mount point for this to work. If | |
2826 | your system doesn't have it mounted, you can do so with:: | |
5af1c6f3 | 2827 | |
f80dba8d | 2828 | # mount -t cgroup -o blkio none /cgroup |
5af1c6f3 | 2829 | |
f80dba8d | 2830 | .. option:: cgroup_weight=int |
5af1c6f3 | 2831 | |
f80dba8d MT |
2832 | Set the weight of the cgroup to this value. See the documentation that comes |
2833 | with the kernel, allowed values are in the range of 100..1000. | |
a086c257 | 2834 | |
f80dba8d | 2835 | .. option:: cgroup_nodelete=bool |
8c07860d | 2836 | |
f80dba8d MT |
2837 | Normally fio will delete the cgroups it has created after the job |
2838 | completion. To override this behavior and to leave cgroups around after the | |
2839 | job completion, set ``cgroup_nodelete=1``. This can be useful if one wants | |
2840 | to inspect various cgroup files after job completion. Default: false. | |
8c07860d | 2841 | |
f80dba8d | 2842 | .. option:: flow_id=int |
8c07860d | 2843 | |
f80dba8d MT |
2844 | The ID of the flow. If not specified, it defaults to being a global |
2845 | flow. See :option:`flow`. | |
1907dbc6 | 2846 | |
f80dba8d | 2847 | .. option:: flow=int |
71bfa161 | 2848 | |
f80dba8d MT |
2849 | Weight in token-based flow control. If this value is used, then there is a |
2850 | 'flow counter' which is used to regulate the proportion of activity between | |
2851 | two or more jobs. Fio attempts to keep this flow counter near zero. The | |
2852 | ``flow`` parameter stands for how much should be added or subtracted to the | |
2853 | flow counter on each iteration of the main I/O loop. That is, if one job has | |
2854 | ``flow=8`` and another job has ``flow=-1``, then there will be a roughly 1:8 | |
2855 | ratio in how much one runs vs the other. | |
71bfa161 | 2856 | |
f80dba8d | 2857 | .. option:: flow_sleep=int |
82407585 | 2858 | |
d4e74fda DB |
2859 | The period of time, in microseconds, to wait after the flow counter |
2860 | has exceeded its proportion before retrying operations. | |
82407585 | 2861 | |
f80dba8d | 2862 | .. option:: stonewall, wait_for_previous |
82407585 | 2863 | |
f80dba8d MT |
2864 | Wait for preceding jobs in the job file to exit, before starting this |
2865 | one. Can be used to insert serialization points in the job file. A stone | |
2866 | wall also implies starting a new reporting group, see | |
2867 | :option:`group_reporting`. | |
2868 | ||
2869 | .. option:: exitall | |
2870 | ||
64402a8a HW |
2871 | By default, fio will continue running all other jobs when one job finishes. |
2872 | Sometimes this is not the desired action. Setting ``exitall`` will instead | |
2873 | make fio terminate all jobs in the same group, as soon as one job of that | |
2874 | group finishes. | |
2875 | ||
2876 | .. option:: exit_what | |
2877 | ||
2878 | By default, fio will continue running all other jobs when one job finishes. | |
2879 | Sometimes this is not the desired action. Setting ``exit_all`` will | |
2880 | instead make fio terminate all jobs in the same group. The option | |
2881 | ``exit_what`` allows to control which jobs get terminated when ``exitall`` is | |
2882 | enabled. The default is ``group`` and does not change the behaviour of | |
2883 | ``exitall``. The setting ``all`` terminates all jobs. The setting ``stonewall`` | |
2884 | terminates all currently running jobs across all groups and continues execution | |
2885 | with the next stonewalled group. | |
f80dba8d MT |
2886 | |
2887 | .. option:: exec_prerun=str | |
2888 | ||
2889 | Before running this job, issue the command specified through | |
2890 | :manpage:`system(3)`. Output is redirected in a file called | |
2891 | :file:`jobname.prerun.txt`. | |
2892 | ||
2893 | .. option:: exec_postrun=str | |
2894 | ||
2895 | After the job completes, issue the command specified though | |
2896 | :manpage:`system(3)`. Output is redirected in a file called | |
2897 | :file:`jobname.postrun.txt`. | |
2898 | ||
2899 | .. option:: uid=int | |
2900 | ||
2901 | Instead of running as the invoking user, set the user ID to this value | |
2902 | before the thread/process does any work. | |
2903 | ||
2904 | .. option:: gid=int | |
2905 | ||
2906 | Set group ID, see :option:`uid`. | |
2907 | ||
2908 | ||
2909 | Verification | |
2910 | ~~~~~~~~~~~~ | |
2911 | ||
2912 | .. option:: verify_only | |
2913 | ||
2914 | Do not perform specified workload, only verify data still matches previous | |
2915 | invocation of this workload. This option allows one to check data multiple | |
2916 | times at a later date without overwriting it. This option makes sense only | |
2917 | for workloads that write data, and does not support workloads with the | |
2918 | :option:`time_based` option set. | |
2919 | ||
2920 | .. option:: do_verify=bool | |
2921 | ||
2922 | Run the verify phase after a write phase. Only valid if :option:`verify` is | |
2923 | set. Default: true. | |
2924 | ||
2925 | .. option:: verify=str | |
2926 | ||
2927 | If writing to a file, fio can verify the file contents after each iteration | |
2928 | of the job. Each verification method also implies verification of special | |
2929 | header, which is written to the beginning of each block. This header also | |
2930 | includes meta information, like offset of the block, block number, timestamp | |
2931 | when block was written, etc. :option:`verify` can be combined with | |
2932 | :option:`verify_pattern` option. The allowed values are: | |
2933 | ||
2934 | **md5** | |
2935 | Use an md5 sum of the data area and store it in the header of | |
2936 | each block. | |
2937 | ||
2938 | **crc64** | |
2939 | Use an experimental crc64 sum of the data area and store it in the | |
2940 | header of each block. | |
2941 | ||
2942 | **crc32c** | |
a5896300 SW |
2943 | Use a crc32c sum of the data area and store it in the header of |
2944 | each block. This will automatically use hardware acceleration | |
2945 | (e.g. SSE4.2 on an x86 or CRC crypto extensions on ARM64) but will | |
2946 | fall back to software crc32c if none is found. Generally the | |
804c0839 | 2947 | fastest checksum fio supports when hardware accelerated. |
f80dba8d MT |
2948 | |
2949 | **crc32c-intel** | |
a5896300 | 2950 | Synonym for crc32c. |
f80dba8d MT |
2951 | |
2952 | **crc32** | |
2953 | Use a crc32 sum of the data area and store it in the header of each | |
2954 | block. | |
2955 | ||
2956 | **crc16** | |
2957 | Use a crc16 sum of the data area and store it in the header of each | |
2958 | block. | |
2959 | ||
2960 | **crc7** | |
2961 | Use a crc7 sum of the data area and store it in the header of each | |
2962 | block. | |
2963 | ||
2964 | **xxhash** | |
2965 | Use xxhash as the checksum function. Generally the fastest software | |
2966 | checksum that fio supports. | |
2967 | ||
2968 | **sha512** | |
2969 | Use sha512 as the checksum function. | |
2970 | ||
2971 | **sha256** | |
2972 | Use sha256 as the checksum function. | |
2973 | ||
2974 | **sha1** | |
2975 | Use optimized sha1 as the checksum function. | |
82407585 | 2976 | |
ae3a5acc JA |
2977 | **sha3-224** |
2978 | Use optimized sha3-224 as the checksum function. | |
2979 | ||
2980 | **sha3-256** | |
2981 | Use optimized sha3-256 as the checksum function. | |
2982 | ||
2983 | **sha3-384** | |
2984 | Use optimized sha3-384 as the checksum function. | |
2985 | ||
2986 | **sha3-512** | |
2987 | Use optimized sha3-512 as the checksum function. | |
2988 | ||
f80dba8d MT |
2989 | **meta** |
2990 | This option is deprecated, since now meta information is included in | |
2991 | generic verification header and meta verification happens by | |
2992 | default. For detailed information see the description of the | |
2993 | :option:`verify` setting. This option is kept because of | |
2994 | compatibility's sake with old configurations. Do not use it. | |
2995 | ||
2996 | **pattern** | |
2997 | Verify a strict pattern. Normally fio includes a header with some | |
2998 | basic information and checksumming, but if this option is set, only | |
2999 | the specific pattern set with :option:`verify_pattern` is verified. | |
3000 | ||
3001 | **null** | |
3002 | Only pretend to verify. Useful for testing internals with | |
9207a0cb | 3003 | :option:`ioengine`\=null, not for much else. |
f80dba8d MT |
3004 | |
3005 | This option can be used for repeated burn-in tests of a system to make sure | |
3006 | that the written data is also correctly read back. If the data direction | |
3007 | given is a read or random read, fio will assume that it should verify a | |
3008 | previously written file. If the data direction includes any form of write, | |
3009 | the verify will be of the newly written data. | |
3010 | ||
47e6a6e5 SW |
3011 | To avoid false verification errors, do not use the norandommap option when |
3012 | verifying data with async I/O engines and I/O depths > 1. Or use the | |
3013 | norandommap and the lfsr random generator together to avoid writing to the | |
3014 | same offset with muliple outstanding I/Os. | |
3015 | ||
f80dba8d MT |
3016 | .. option:: verify_offset=int |
3017 | ||
3018 | Swap the verification header with data somewhere else in the block before | |
3019 | writing. It is swapped back before verifying. | |
3020 | ||
3021 | .. option:: verify_interval=int | |
3022 | ||
3023 | Write the verification header at a finer granularity than the | |
3024 | :option:`blocksize`. It will be written for chunks the size of | |
3025 | ``verify_interval``. :option:`blocksize` should divide this evenly. | |
3026 | ||
3027 | .. option:: verify_pattern=str | |
3028 | ||
3029 | If set, fio will fill the I/O buffers with this pattern. Fio defaults to | |
3030 | filling with totally random bytes, but sometimes it's interesting to fill | |
3031 | with a known pattern for I/O verification purposes. Depending on the width | |
730bd7d9 | 3032 | of the pattern, fio will fill 1/2/3/4 bytes of the buffer at the time (it can |
f80dba8d MT |
3033 | be either a decimal or a hex number). The ``verify_pattern`` if larger than |
3034 | a 32-bit quantity has to be a hex number that starts with either "0x" or | |
3035 | "0X". Use with :option:`verify`. Also, ``verify_pattern`` supports %o | |
3036 | format, which means that for each block offset will be written and then | |
3037 | verified back, e.g.:: | |
61b9861d RP |
3038 | |
3039 | verify_pattern=%o | |
3040 | ||
f80dba8d MT |
3041 | Or use combination of everything:: |
3042 | ||
61b9861d | 3043 | verify_pattern=0xff%o"abcd"-12 |
e28218f3 | 3044 | |
f80dba8d MT |
3045 | .. option:: verify_fatal=bool |
3046 | ||
3047 | Normally fio will keep checking the entire contents before quitting on a | |
3048 | block verification failure. If this option is set, fio will exit the job on | |
3049 | the first observed failure. Default: false. | |
3050 | ||
3051 | .. option:: verify_dump=bool | |
3052 | ||
3053 | If set, dump the contents of both the original data block and the data block | |
3054 | we read off disk to files. This allows later analysis to inspect just what | |
3055 | kind of data corruption occurred. Off by default. | |
3056 | ||
3057 | .. option:: verify_async=int | |
3058 | ||
3059 | Fio will normally verify I/O inline from the submitting thread. This option | |
3060 | takes an integer describing how many async offload threads to create for I/O | |
3061 | verification instead, causing fio to offload the duty of verifying I/O | |
3062 | contents to one or more separate threads. If using this offload option, even | |
3063 | sync I/O engines can benefit from using an :option:`iodepth` setting higher | |
3064 | than 1, as it allows them to have I/O in flight while verifies are running. | |
d7e6ea1c | 3065 | Defaults to 0 async threads, i.e. verification is not asynchronous. |
f80dba8d MT |
3066 | |
3067 | .. option:: verify_async_cpus=str | |
3068 | ||
3069 | Tell fio to set the given CPU affinity on the async I/O verification | |
3070 | threads. See :option:`cpus_allowed` for the format used. | |
3071 | ||
3072 | .. option:: verify_backlog=int | |
3073 | ||
3074 | Fio will normally verify the written contents of a job that utilizes verify | |
3075 | once that job has completed. In other words, everything is written then | |
3076 | everything is read back and verified. You may want to verify continually | |
3077 | instead for a variety of reasons. Fio stores the meta data associated with | |
3078 | an I/O block in memory, so for large verify workloads, quite a bit of memory | |
3079 | would be used up holding this meta data. If this option is enabled, fio will | |
3080 | write only N blocks before verifying these blocks. | |
3081 | ||
3082 | .. option:: verify_backlog_batch=int | |
3083 | ||
3084 | Control how many blocks fio will verify if :option:`verify_backlog` is | |
3085 | set. If not set, will default to the value of :option:`verify_backlog` | |
3086 | (meaning the entire queue is read back and verified). If | |
3087 | ``verify_backlog_batch`` is less than :option:`verify_backlog` then not all | |
3088 | blocks will be verified, if ``verify_backlog_batch`` is larger than | |
3089 | :option:`verify_backlog`, some blocks will be verified more than once. | |
3090 | ||
3091 | .. option:: verify_state_save=bool | |
3092 | ||
3093 | When a job exits during the write phase of a verify workload, save its | |
3094 | current state. This allows fio to replay up until that point, if the verify | |
3095 | state is loaded for the verify read phase. The format of the filename is, | |
3096 | roughly:: | |
3097 | ||
f50fbdda | 3098 | <type>-<jobname>-<jobindex>-verify.state. |
f80dba8d MT |
3099 | |
3100 | <type> is "local" for a local run, "sock" for a client/server socket | |
3101 | connection, and "ip" (192.168.0.1, for instance) for a networked | |
d7e6ea1c | 3102 | client/server connection. Defaults to true. |
f80dba8d MT |
3103 | |
3104 | .. option:: verify_state_load=bool | |
3105 | ||
3106 | If a verify termination trigger was used, fio stores the current write state | |
3107 | of each thread. This can be used at verification time so that fio knows how | |
3108 | far it should verify. Without this information, fio will run a full | |
a47b697c SW |
3109 | verification pass, according to the settings in the job file used. Default |
3110 | false. | |
f80dba8d MT |
3111 | |
3112 | .. option:: trim_percentage=int | |
3113 | ||
3114 | Number of verify blocks to discard/trim. | |
3115 | ||
3116 | .. option:: trim_verify_zero=bool | |
3117 | ||
22413915 | 3118 | Verify that trim/discarded blocks are returned as zeros. |
f80dba8d MT |
3119 | |
3120 | .. option:: trim_backlog=int | |
3121 | ||
5cfd1e9a | 3122 | Trim after this number of blocks are written. |
f80dba8d MT |
3123 | |
3124 | .. option:: trim_backlog_batch=int | |
3125 | ||
3126 | Trim this number of I/O blocks. | |
3127 | ||
3128 | .. option:: experimental_verify=bool | |
3129 | ||
3130 | Enable experimental verification. | |
3131 | ||
f80dba8d MT |
3132 | Steady state |
3133 | ~~~~~~~~~~~~ | |
3134 | ||
3135 | .. option:: steadystate=str:float, ss=str:float | |
3136 | ||
3137 | Define the criterion and limit for assessing steady state performance. The | |
3138 | first parameter designates the criterion whereas the second parameter sets | |
3139 | the threshold. When the criterion falls below the threshold for the | |
3140 | specified duration, the job will stop. For example, `iops_slope:0.1%` will | |
3141 | direct fio to terminate the job when the least squares regression slope | |
3142 | falls below 0.1% of the mean IOPS. If :option:`group_reporting` is enabled | |
3143 | this will apply to all jobs in the group. Below is the list of available | |
3144 | steady state assessment criteria. All assessments are carried out using only | |
3145 | data from the rolling collection window. Threshold limits can be expressed | |
3146 | as a fixed value or as a percentage of the mean in the collection window. | |
3147 | ||
1cb049d9 VF |
3148 | When using this feature, most jobs should include the :option:`time_based` |
3149 | and :option:`runtime` options or the :option:`loops` option so that fio does not | |
3150 | stop running after it has covered the full size of the specified file(s) or device(s). | |
3151 | ||
f80dba8d MT |
3152 | **iops** |
3153 | Collect IOPS data. Stop the job if all individual IOPS measurements | |
3154 | are within the specified limit of the mean IOPS (e.g., ``iops:2`` | |
3155 | means that all individual IOPS values must be within 2 of the mean, | |
3156 | whereas ``iops:0.2%`` means that all individual IOPS values must be | |
3157 | within 0.2% of the mean IOPS to terminate the job). | |
3158 | ||
3159 | **iops_slope** | |
3160 | Collect IOPS data and calculate the least squares regression | |
3161 | slope. Stop the job if the slope falls below the specified limit. | |
3162 | ||
3163 | **bw** | |
3164 | Collect bandwidth data. Stop the job if all individual bandwidth | |
3165 | measurements are within the specified limit of the mean bandwidth. | |
3166 | ||
3167 | **bw_slope** | |
3168 | Collect bandwidth data and calculate the least squares regression | |
3169 | slope. Stop the job if the slope falls below the specified limit. | |
3170 | ||
3171 | .. option:: steadystate_duration=time, ss_dur=time | |
3172 | ||
3173 | A rolling window of this duration will be used to judge whether steady state | |
3174 | has been reached. Data will be collected once per second. The default is 0 | |
f75ede1d | 3175 | which disables steady state detection. When the unit is omitted, the |
947e0fe0 | 3176 | value is interpreted in seconds. |
f80dba8d MT |
3177 | |
3178 | .. option:: steadystate_ramp_time=time, ss_ramp=time | |
3179 | ||
3180 | Allow the job to run for the specified duration before beginning data | |
3181 | collection for checking the steady state job termination criterion. The | |
947e0fe0 | 3182 | default is 0. When the unit is omitted, the value is interpreted in seconds. |
f80dba8d MT |
3183 | |
3184 | ||
3185 | Measurements and reporting | |
3186 | ~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
3187 | ||
3188 | .. option:: per_job_logs=bool | |
3189 | ||
3190 | If set, this generates bw/clat/iops log with per file private filenames. If | |
3191 | not set, jobs with identical names will share the log filename. Default: | |
3192 | true. | |
3193 | ||
3194 | .. option:: group_reporting | |
3195 | ||
3196 | It may sometimes be interesting to display statistics for groups of jobs as | |
3197 | a whole instead of for each individual job. This is especially true if | |
3198 | :option:`numjobs` is used; looking at individual thread/process output | |
3199 | quickly becomes unwieldy. To see the final report per-group instead of | |
3200 | per-job, use :option:`group_reporting`. Jobs in a file will be part of the | |
3201 | same reporting group, unless if separated by a :option:`stonewall`, or by | |
3202 | using :option:`new_group`. | |
3203 | ||
3204 | .. option:: new_group | |
3205 | ||
3206 | Start a new reporting group. See: :option:`group_reporting`. If not given, | |
3207 | all jobs in a file will be part of the same reporting group, unless | |
3208 | separated by a :option:`stonewall`. | |
3209 | ||
589e88b7 | 3210 | .. option:: stats=bool |
8243be59 JA |
3211 | |
3212 | By default, fio collects and shows final output results for all jobs | |
3213 | that run. If this option is set to 0, then fio will ignore it in | |
3214 | the final stat output. | |
3215 | ||
f80dba8d MT |
3216 | .. option:: write_bw_log=str |
3217 | ||
3218 | If given, write a bandwidth log for this job. Can be used to store data of | |
074f0817 | 3219 | the bandwidth of the jobs in their lifetime. |
f80dba8d | 3220 | |
074f0817 SW |
3221 | If no str argument is given, the default filename of |
3222 | :file:`jobname_type.x.log` is used. Even when the argument is given, fio | |
3223 | will still append the type of log. So if one specifies:: | |
3224 | ||
3225 | write_bw_log=foo | |
f80dba8d | 3226 | |
074f0817 SW |
3227 | The actual log name will be :file:`foo_bw.x.log` where `x` is the index |
3228 | of the job (`1..N`, where `N` is the number of jobs). If | |
3229 | :option:`per_job_logs` is false, then the filename will not include the | |
3230 | `.x` job index. | |
e3cedca7 | 3231 | |
074f0817 SW |
3232 | The included :command:`fio_generate_plots` script uses :command:`gnuplot` to turn these |
3233 | text files into nice graphs. See `Log File Formats`_ for how data is | |
3234 | structured within the file. | |
3235 | ||
3236 | .. option:: write_lat_log=str | |
e3cedca7 | 3237 | |
074f0817 | 3238 | Same as :option:`write_bw_log`, except this option creates I/O |
77b7e675 SW |
3239 | submission (e.g., :file:`name_slat.x.log`), completion (e.g., |
3240 | :file:`name_clat.x.log`), and total (e.g., :file:`name_lat.x.log`) | |
074f0817 SW |
3241 | latency files instead. See :option:`write_bw_log` for details about |
3242 | the filename format and `Log File Formats`_ for how data is structured | |
3243 | within the files. | |
be4ecfdf | 3244 | |
f80dba8d | 3245 | .. option:: write_hist_log=str |
06842027 | 3246 | |
074f0817 | 3247 | Same as :option:`write_bw_log` but writes an I/O completion latency |
77b7e675 | 3248 | histogram file (e.g., :file:`name_hist.x.log`) instead. Note that this |
074f0817 SW |
3249 | file will be empty unless :option:`log_hist_msec` has also been set. |
3250 | See :option:`write_bw_log` for details about the filename format and | |
3251 | `Log File Formats`_ for how data is structured within the file. | |
06842027 | 3252 | |
f80dba8d | 3253 | .. option:: write_iops_log=str |
06842027 | 3254 | |
074f0817 | 3255 | Same as :option:`write_bw_log`, but writes an IOPS file (e.g. |
15417073 SW |
3256 | :file:`name_iops.x.log`) instead. Because fio defaults to individual |
3257 | I/O logging, the value entry in the IOPS log will be 1 unless windowed | |
3258 | logging (see :option:`log_avg_msec`) has been enabled. See | |
3259 | :option:`write_bw_log` for details about the filename format and `Log | |
3260 | File Formats`_ for how data is structured within the file. | |
06842027 | 3261 | |
f80dba8d | 3262 | .. option:: log_avg_msec=int |
06842027 | 3263 | |
f80dba8d MT |
3264 | By default, fio will log an entry in the iops, latency, or bw log for every |
3265 | I/O that completes. When writing to the disk log, that can quickly grow to a | |
3266 | very large size. Setting this option makes fio average the each log entry | |
3267 | over the specified period of time, reducing the resolution of the log. See | |
3268 | :option:`log_max_value` as well. Defaults to 0, logging all entries. | |
6fc82095 | 3269 | Also see `Log File Formats`_. |
06842027 | 3270 | |
f80dba8d | 3271 | .. option:: log_hist_msec=int |
06842027 | 3272 | |
f80dba8d MT |
3273 | Same as :option:`log_avg_msec`, but logs entries for completion latency |
3274 | histograms. Computing latency percentiles from averages of intervals using | |
c60ebc45 | 3275 | :option:`log_avg_msec` is inaccurate. Setting this option makes fio log |
f80dba8d MT |
3276 | histogram entries over the specified period of time, reducing log sizes for |
3277 | high IOPS devices while retaining percentile accuracy. See | |
074f0817 SW |
3278 | :option:`log_hist_coarseness` and :option:`write_hist_log` as well. |
3279 | Defaults to 0, meaning histogram logging is disabled. | |
06842027 | 3280 | |
f80dba8d | 3281 | .. option:: log_hist_coarseness=int |
06842027 | 3282 | |
f80dba8d MT |
3283 | Integer ranging from 0 to 6, defining the coarseness of the resolution of |
3284 | the histogram logs enabled with :option:`log_hist_msec`. For each increment | |
3285 | in coarseness, fio outputs half as many bins. Defaults to 0, for which | |
074f0817 SW |
3286 | histogram logs contain 1216 latency bins. See :option:`write_hist_log` |
3287 | and `Log File Formats`_. | |
8b28bd41 | 3288 | |
f80dba8d | 3289 | .. option:: log_max_value=bool |
66c098b8 | 3290 | |
f80dba8d MT |
3291 | If :option:`log_avg_msec` is set, fio logs the average over that window. If |
3292 | you instead want to log the maximum value, set this option to 1. Defaults to | |
3293 | 0, meaning that averaged values are logged. | |
a696fa2a | 3294 | |
589e88b7 | 3295 | .. option:: log_offset=bool |
a696fa2a | 3296 | |
f80dba8d | 3297 | If this is set, the iolog options will include the byte offset for the I/O |
5a83478f SW |
3298 | entry as well as the other data values. Defaults to 0 meaning that |
3299 | offsets are not present in logs. Also see `Log File Formats`_. | |
71bfa161 | 3300 | |
f80dba8d | 3301 | .. option:: log_compression=int |
7de87099 | 3302 | |
f80dba8d MT |
3303 | If this is set, fio will compress the I/O logs as it goes, to keep the |
3304 | memory footprint lower. When a log reaches the specified size, that chunk is | |
3305 | removed and compressed in the background. Given that I/O logs are fairly | |
3306 | highly compressible, this yields a nice memory savings for longer runs. The | |
3307 | downside is that the compression will consume some background CPU cycles, so | |
3308 | it may impact the run. This, however, is also true if the logging ends up | |
3309 | consuming most of the system memory. So pick your poison. The I/O logs are | |
3310 | saved normally at the end of a run, by decompressing the chunks and storing | |
3311 | them in the specified log file. This feature depends on the availability of | |
3312 | zlib. | |
e0b0d892 | 3313 | |
f80dba8d | 3314 | .. option:: log_compression_cpus=str |
e0b0d892 | 3315 | |
f80dba8d MT |
3316 | Define the set of CPUs that are allowed to handle online log compression for |
3317 | the I/O jobs. This can provide better isolation between performance | |
0cf90a62 SW |
3318 | sensitive jobs, and background compression work. See |
3319 | :option:`cpus_allowed` for the format used. | |
9e684a49 | 3320 | |
f80dba8d | 3321 | .. option:: log_store_compressed=bool |
9e684a49 | 3322 | |
f80dba8d MT |
3323 | If set, fio will store the log files in a compressed format. They can be |
3324 | decompressed with fio, using the :option:`--inflate-log` command line | |
3325 | parameter. The files will be stored with a :file:`.fz` suffix. | |
9e684a49 | 3326 | |
f80dba8d | 3327 | .. option:: log_unix_epoch=bool |
9e684a49 | 3328 | |
f80dba8d MT |
3329 | If set, fio will log Unix timestamps to the log files produced by enabling |
3330 | write_type_log for each log type, instead of the default zero-based | |
3331 | timestamps. | |
3332 | ||
3333 | .. option:: block_error_percentiles=bool | |
3334 | ||
3335 | If set, record errors in trim block-sized units from writes and trims and | |
3336 | output a histogram of how many trims it took to get to errors, and what kind | |
3337 | of error was encountered. | |
3338 | ||
3339 | .. option:: bwavgtime=int | |
3340 | ||
3341 | Average the calculated bandwidth over the given time. Value is specified in | |
3342 | milliseconds. If the job also does bandwidth logging through | |
3343 | :option:`write_bw_log`, then the minimum of this option and | |
3344 | :option:`log_avg_msec` will be used. Default: 500ms. | |
3345 | ||
3346 | .. option:: iopsavgtime=int | |
3347 | ||
3348 | Average the calculated IOPS over the given time. Value is specified in | |
3349 | milliseconds. If the job also does IOPS logging through | |
3350 | :option:`write_iops_log`, then the minimum of this option and | |
3351 | :option:`log_avg_msec` will be used. Default: 500ms. | |
3352 | ||
3353 | .. option:: disk_util=bool | |
3354 | ||
3355 | Generate disk utilization statistics, if the platform supports it. | |
3356 | Default: true. | |
3357 | ||
3358 | .. option:: disable_lat=bool | |
3359 | ||
3360 | Disable measurements of total latency numbers. Useful only for cutting back | |
3361 | the number of calls to :manpage:`gettimeofday(2)`, as that does impact | |
3362 | performance at really high IOPS rates. Note that to really get rid of a | |
3363 | large amount of these calls, this option must be used with | |
f75ede1d | 3364 | :option:`disable_slat` and :option:`disable_bw_measurement` as well. |
f80dba8d MT |
3365 | |
3366 | .. option:: disable_clat=bool | |
3367 | ||
3368 | Disable measurements of completion latency numbers. See | |
3369 | :option:`disable_lat`. | |
3370 | ||
3371 | .. option:: disable_slat=bool | |
3372 | ||
3373 | Disable measurements of submission latency numbers. See | |
f50fbdda | 3374 | :option:`disable_lat`. |
f80dba8d | 3375 | |
f75ede1d | 3376 | .. option:: disable_bw_measurement=bool, disable_bw=bool |
f80dba8d MT |
3377 | |
3378 | Disable measurements of throughput/bandwidth numbers. See | |
3379 | :option:`disable_lat`. | |
3380 | ||
dd39b9ce VF |
3381 | .. option:: slat_percentiles=bool |
3382 | ||
3383 | Report submission latency percentiles. Submission latency is not recorded | |
3384 | for synchronous ioengines. | |
3385 | ||
f80dba8d MT |
3386 | .. option:: clat_percentiles=bool |
3387 | ||
dd39b9ce | 3388 | Report completion latency percentiles. |
b599759b JA |
3389 | |
3390 | .. option:: lat_percentiles=bool | |
3391 | ||
dd39b9ce VF |
3392 | Report total latency percentiles. Total latency is the sum of submission |
3393 | latency and completion latency. | |
f80dba8d MT |
3394 | |
3395 | .. option:: percentile_list=float_list | |
3396 | ||
dd39b9ce VF |
3397 | Overwrite the default list of percentiles for latencies and the block error |
3398 | histogram. Each number is a floating point number in the range (0,100], and | |
3399 | the maximum length of the list is 20. Use ``:`` to separate the numbers. For | |
c32ba107 | 3400 | example, ``--percentile_list=99.5:99.9`` will cause fio to report the |
dd39b9ce VF |
3401 | latency durations below which 99.5% and 99.9% of the observed latencies fell, |
3402 | respectively. | |
f80dba8d | 3403 | |
e883cb35 JF |
3404 | .. option:: significant_figures=int |
3405 | ||
c32ba107 JA |
3406 | If using :option:`--output-format` of `normal`, set the significant |
3407 | figures to this value. Higher values will yield more precise IOPS and | |
3408 | throughput units, while lower values will round. Requires a minimum | |
3409 | value of 1 and a maximum value of 10. Defaults to 4. | |
e883cb35 | 3410 | |
f80dba8d MT |
3411 | |
3412 | Error handling | |
3413 | ~~~~~~~~~~~~~~ | |
3414 | ||
3415 | .. option:: exitall_on_error | |
3416 | ||
3417 | When one job finishes in error, terminate the rest. The default is to wait | |
3418 | for each job to finish. | |
3419 | ||
3420 | .. option:: continue_on_error=str | |
3421 | ||
3422 | Normally fio will exit the job on the first observed failure. If this option | |
3423 | is set, fio will continue the job when there is a 'non-fatal error' (EIO or | |
3424 | EILSEQ) until the runtime is exceeded or the I/O size specified is | |
3425 | completed. If this option is used, there are two more stats that are | |
3426 | appended, the total error count and the first error. The error field given | |
3427 | in the stats is the first error that was hit during the run. | |
3428 | ||
3429 | The allowed values are: | |
3430 | ||
3431 | **none** | |
3432 | Exit on any I/O or verify errors. | |
3433 | ||
3434 | **read** | |
3435 | Continue on read errors, exit on all others. | |
3436 | ||
3437 | **write** | |
3438 | Continue on write errors, exit on all others. | |
3439 | ||
3440 | **io** | |
3441 | Continue on any I/O error, exit on all others. | |
3442 | ||
3443 | **verify** | |
3444 | Continue on verify errors, exit on all others. | |
3445 | ||
3446 | **all** | |
3447 | Continue on all errors. | |
3448 | ||
3449 | **0** | |
3450 | Backward-compatible alias for 'none'. | |
3451 | ||
3452 | **1** | |
3453 | Backward-compatible alias for 'all'. | |
3454 | ||
3455 | .. option:: ignore_error=str | |
3456 | ||
3457 | Sometimes you want to ignore some errors during test in that case you can | |
a35ef7cb TK |
3458 | specify error list for each error type, instead of only being able to |
3459 | ignore the default 'non-fatal error' using :option:`continue_on_error`. | |
f80dba8d MT |
3460 | ``ignore_error=READ_ERR_LIST,WRITE_ERR_LIST,VERIFY_ERR_LIST`` errors for |
3461 | given error type is separated with ':'. Error may be symbol ('ENOSPC', | |
3462 | 'ENOMEM') or integer. Example:: | |
3463 | ||
3464 | ignore_error=EAGAIN,ENOSPC:122 | |
3465 | ||
3466 | This option will ignore EAGAIN from READ, and ENOSPC and 122(EDQUOT) from | |
a35ef7cb TK |
3467 | WRITE. This option works by overriding :option:`continue_on_error` with |
3468 | the list of errors for each error type if any. | |
f80dba8d MT |
3469 | |
3470 | .. option:: error_dump=bool | |
3471 | ||
3472 | If set dump every error even if it is non fatal, true by default. If | |
3473 | disabled only fatal error will be dumped. | |
3474 | ||
f75ede1d SW |
3475 | Running predefined workloads |
3476 | ---------------------------- | |
3477 | ||
3478 | Fio includes predefined profiles that mimic the I/O workloads generated by | |
3479 | other tools. | |
3480 | ||
3481 | .. option:: profile=str | |
3482 | ||
3483 | The predefined workload to run. Current profiles are: | |
3484 | ||
3485 | **tiobench** | |
3486 | Threaded I/O bench (tiotest/tiobench) like workload. | |
3487 | ||
3488 | **act** | |
3489 | Aerospike Certification Tool (ACT) like workload. | |
3490 | ||
3491 | To view a profile's additional options use :option:`--cmdhelp` after specifying | |
3492 | the profile. For example:: | |
3493 | ||
f50fbdda | 3494 | $ fio --profile=act --cmdhelp |
f75ede1d SW |
3495 | |
3496 | Act profile options | |
3497 | ~~~~~~~~~~~~~~~~~~~ | |
3498 | ||
3499 | .. option:: device-names=str | |
3500 | :noindex: | |
3501 | ||
3502 | Devices to use. | |
3503 | ||
3504 | .. option:: load=int | |
3505 | :noindex: | |
3506 | ||
3507 | ACT load multiplier. Default: 1. | |
3508 | ||
3509 | .. option:: test-duration=time | |
3510 | :noindex: | |
3511 | ||
947e0fe0 SW |
3512 | How long the entire test takes to run. When the unit is omitted, the value |
3513 | is given in seconds. Default: 24h. | |
f75ede1d SW |
3514 | |
3515 | .. option:: threads-per-queue=int | |
3516 | :noindex: | |
3517 | ||
f50fbdda | 3518 | Number of read I/O threads per device. Default: 8. |
f75ede1d SW |
3519 | |
3520 | .. option:: read-req-num-512-blocks=int | |
3521 | :noindex: | |
3522 | ||
3523 | Number of 512B blocks to read at the time. Default: 3. | |
3524 | ||
3525 | .. option:: large-block-op-kbytes=int | |
3526 | :noindex: | |
3527 | ||
3528 | Size of large block ops in KiB (writes). Default: 131072. | |
3529 | ||
3530 | .. option:: prep | |
3531 | :noindex: | |
3532 | ||
3533 | Set to run ACT prep phase. | |
3534 | ||
3535 | Tiobench profile options | |
3536 | ~~~~~~~~~~~~~~~~~~~~~~~~ | |
3537 | ||
3538 | .. option:: size=str | |
3539 | :noindex: | |
3540 | ||
f50fbdda | 3541 | Size in MiB. |
f75ede1d SW |
3542 | |
3543 | .. option:: block=int | |
3544 | :noindex: | |
3545 | ||
3546 | Block size in bytes. Default: 4096. | |
3547 | ||
3548 | .. option:: numruns=int | |
3549 | :noindex: | |
3550 | ||
3551 | Number of runs. | |
3552 | ||
3553 | .. option:: dir=str | |
3554 | :noindex: | |
3555 | ||
3556 | Test directory. | |
3557 | ||
3558 | .. option:: threads=int | |
3559 | :noindex: | |
3560 | ||
3561 | Number of threads. | |
f80dba8d MT |
3562 | |
3563 | Interpreting the output | |
3564 | ----------------------- | |
3565 | ||
36214730 SW |
3566 | .. |
3567 | Example output was based on the following: | |
3568 | TZ=UTC fio --iodepth=8 --ioengine=null --size=100M --time_based \ | |
3569 | --rate=1256k --bs=14K --name=quick --runtime=1s --name=mixed \ | |
3570 | --runtime=2m --rw=rw | |
3571 | ||
f80dba8d MT |
3572 | Fio spits out a lot of output. While running, fio will display the status of the |
3573 | jobs created. An example of that would be:: | |
3574 | ||
9d25d068 | 3575 | 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] |
f80dba8d | 3576 | |
36214730 SW |
3577 | The characters inside the first set of square brackets denote the current status of |
3578 | each thread. The first character is the first job defined in the job file, and so | |
3579 | forth. The possible values (in typical life cycle order) are: | |
f80dba8d MT |
3580 | |
3581 | +------+-----+-----------------------------------------------------------+ | |
3582 | | Idle | Run | | | |
3583 | +======+=====+===========================================================+ | |
3584 | | P | | Thread setup, but not started. | | |
3585 | +------+-----+-----------------------------------------------------------+ | |
3586 | | C | | Thread created. | | |
3587 | +------+-----+-----------------------------------------------------------+ | |
3588 | | I | | Thread initialized, waiting or generating necessary data. | | |
3589 | +------+-----+-----------------------------------------------------------+ | |
3590 | | | p | Thread running pre-reading file(s). | | |
3591 | +------+-----+-----------------------------------------------------------+ | |
36214730 SW |
3592 | | | / | Thread is in ramp period. | |
3593 | +------+-----+-----------------------------------------------------------+ | |
f80dba8d MT |
3594 | | | R | Running, doing sequential reads. | |
3595 | +------+-----+-----------------------------------------------------------+ | |
3596 | | | r | Running, doing random reads. | | |
3597 | +------+-----+-----------------------------------------------------------+ | |
3598 | | | W | Running, doing sequential writes. | | |
3599 | +------+-----+-----------------------------------------------------------+ | |
3600 | | | w | Running, doing random writes. | | |
3601 | +------+-----+-----------------------------------------------------------+ | |
3602 | | | M | Running, doing mixed sequential reads/writes. | | |
3603 | +------+-----+-----------------------------------------------------------+ | |
3604 | | | m | Running, doing mixed random reads/writes. | | |
3605 | +------+-----+-----------------------------------------------------------+ | |
36214730 SW |
3606 | | | D | Running, doing sequential trims. | |
3607 | +------+-----+-----------------------------------------------------------+ | |
3608 | | | d | Running, doing random trims. | | |
3609 | +------+-----+-----------------------------------------------------------+ | |
3610 | | | F | Running, currently waiting for :manpage:`fsync(2)`. | | |
f80dba8d MT |
3611 | +------+-----+-----------------------------------------------------------+ |
3612 | | | V | Running, doing verification of written data. | | |
3613 | +------+-----+-----------------------------------------------------------+ | |
36214730 SW |
3614 | | f | | Thread finishing. | |
3615 | +------+-----+-----------------------------------------------------------+ | |
f80dba8d MT |
3616 | | E | | Thread exited, not reaped by main thread yet. | |
3617 | +------+-----+-----------------------------------------------------------+ | |
36214730 | 3618 | | _ | | Thread reaped. | |
f80dba8d MT |
3619 | +------+-----+-----------------------------------------------------------+ |
3620 | | X | | Thread reaped, exited with an error. | | |
3621 | +------+-----+-----------------------------------------------------------+ | |
3622 | | K | | Thread reaped, exited due to signal. | | |
3623 | +------+-----+-----------------------------------------------------------+ | |
3624 | ||
36214730 SW |
3625 | .. |
3626 | Example output was based on the following: | |
3627 | TZ=UTC fio --iodepth=8 --ioengine=null --size=100M --runtime=58m \ | |
3628 | --time_based --rate=2512k --bs=256K --numjobs=10 \ | |
3629 | --name=readers --rw=read --name=writers --rw=write | |
3630 | ||
f80dba8d | 3631 | Fio will condense the thread string as not to take up more space on the command |
36214730 | 3632 | line than needed. For instance, if you have 10 readers and 10 writers running, |
f80dba8d MT |
3633 | the output would look like this:: |
3634 | ||
9d25d068 | 3635 | 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] |
f80dba8d | 3636 | |
36214730 SW |
3637 | Note that the status string is displayed in order, so it's possible to tell which of |
3638 | the jobs are currently doing what. In the example above this means that jobs 1--10 | |
3639 | are readers and 11--20 are writers. | |
f80dba8d MT |
3640 | |
3641 | The other values are fairly self explanatory -- number of threads currently | |
36214730 SW |
3642 | running and doing I/O, the number of currently open files (f=), the estimated |
3643 | completion percentage, the rate of I/O since last check (read speed listed first, | |
f50fbdda TK |
3644 | then write speed and optionally trim speed) in terms of bandwidth and IOPS, |
3645 | and time to completion for the current running group. It's impossible to estimate | |
3646 | runtime of the following groups (if any). | |
36214730 SW |
3647 | |
3648 | .. | |
3649 | Example output was based on the following: | |
3650 | TZ=UTC fio --iodepth=16 --ioengine=posixaio --filename=/tmp/fiofile \ | |
3651 | --direct=1 --size=100M --time_based --runtime=50s --rate_iops=89 \ | |
3652 | --bs=7K --name=Client1 --rw=write | |
3653 | ||
3654 | When fio is done (or interrupted by :kbd:`Ctrl-C`), it will show the data for | |
3655 | each thread, group of threads, and disks in that order. For each overall thread (or | |
3656 | group) the output looks like:: | |
3657 | ||
3658 | Client1: (groupid=0, jobs=1): err= 0: pid=16109: Sat Jun 24 12:07:54 2017 | |
3659 | write: IOPS=88, BW=623KiB/s (638kB/s)(30.4MiB/50032msec) | |
3660 | slat (nsec): min=500, max=145500, avg=8318.00, stdev=4781.50 | |
3661 | clat (usec): min=170, max=78367, avg=4019.02, stdev=8293.31 | |
3662 | lat (usec): min=174, max=78375, avg=4027.34, stdev=8291.79 | |
3663 | clat percentiles (usec): | |
3664 | | 1.00th=[ 302], 5.00th=[ 326], 10.00th=[ 343], 20.00th=[ 363], | |
3665 | | 30.00th=[ 392], 40.00th=[ 404], 50.00th=[ 416], 60.00th=[ 445], | |
3666 | | 70.00th=[ 816], 80.00th=[ 6718], 90.00th=[12911], 95.00th=[21627], | |
3667 | | 99.00th=[43779], 99.50th=[51643], 99.90th=[68682], 99.95th=[72877], | |
3668 | | 99.99th=[78119] | |
3669 | bw ( KiB/s): min= 532, max= 686, per=0.10%, avg=622.87, stdev=24.82, samples= 100 | |
3670 | iops : min= 76, max= 98, avg=88.98, stdev= 3.54, samples= 100 | |
29092211 VF |
3671 | lat (usec) : 250=0.04%, 500=64.11%, 750=4.81%, 1000=2.79% |
3672 | lat (msec) : 2=4.16%, 4=1.84%, 10=4.90%, 20=11.33%, 50=5.37% | |
3673 | lat (msec) : 100=0.65% | |
36214730 SW |
3674 | cpu : usr=0.27%, sys=0.18%, ctx=12072, majf=0, minf=21 |
3675 | IO depths : 1=85.0%, 2=13.1%, 4=1.8%, 8=0.1%, 16=0.0%, 32=0.0%, >=64=0.0% | |
3676 | submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% | |
3677 | complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% | |
3678 | issued rwt: total=0,4450,0, short=0,0,0, dropped=0,0,0 | |
3679 | latency : target=0, window=0, percentile=100.00%, depth=8 | |
3680 | ||
3681 | The job name (or first job's name when using :option:`group_reporting`) is printed, | |
3682 | along with the group id, count of jobs being aggregated, last error id seen (which | |
3683 | is 0 when there are no errors), pid/tid of that thread and the time the job/group | |
3684 | completed. Below are the I/O statistics for each data direction performed (showing | |
3685 | writes in the example above). In the order listed, they denote: | |
3686 | ||
3687 | **read/write/trim** | |
3688 | The string before the colon shows the I/O direction the statistics | |
3689 | are for. **IOPS** is the average I/Os performed per second. **BW** | |
3690 | is the average bandwidth rate shown as: value in power of 2 format | |
3691 | (value in power of 10 format). The last two values show: (**total | |
3692 | I/O performed** in power of 2 format / **runtime** of that thread). | |
f80dba8d MT |
3693 | |
3694 | **slat** | |
36214730 SW |
3695 | Submission latency (**min** being the minimum, **max** being the |
3696 | maximum, **avg** being the average, **stdev** being the standard | |
3697 | deviation). This is the time it took to submit the I/O. For | |
3698 | sync I/O this row is not displayed as the slat is really the | |
3699 | completion latency (since queue/complete is one operation there). | |
3700 | This value can be in nanoseconds, microseconds or milliseconds --- | |
3701 | fio will choose the most appropriate base and print that (in the | |
3702 | example above nanoseconds was the best scale). Note: in :option:`--minimal` mode | |
0d237712 | 3703 | latencies are always expressed in microseconds. |
f80dba8d MT |
3704 | |
3705 | **clat** | |
3706 | Completion latency. Same names as slat, this denotes the time from | |
3707 | submission to completion of the I/O pieces. For sync I/O, clat will | |
3708 | usually be equal (or very close) to 0, as the time from submit to | |
3709 | complete is basically just CPU time (I/O has already been done, see slat | |
3710 | explanation). | |
3711 | ||
29092211 VF |
3712 | **lat** |
3713 | Total latency. Same names as slat and clat, this denotes the time from | |
3714 | when fio created the I/O unit to completion of the I/O operation. | |
3715 | ||
f80dba8d | 3716 | **bw** |
36214730 SW |
3717 | Bandwidth statistics based on samples. Same names as the xlat stats, |
3718 | but also includes the number of samples taken (**samples**) and an | |
3719 | approximate percentage of total aggregate bandwidth this thread | |
3720 | received in its group (**per**). This last value is only really | |
3721 | useful if the threads in this group are on the same disk, since they | |
3722 | are then competing for disk access. | |
3723 | ||
3724 | **iops** | |
3725 | IOPS statistics based on samples. Same names as bw. | |
f80dba8d | 3726 | |
29092211 VF |
3727 | **lat (nsec/usec/msec)** |
3728 | The distribution of I/O completion latencies. This is the time from when | |
3729 | I/O leaves fio and when it gets completed. Unlike the separate | |
3730 | read/write/trim sections above, the data here and in the remaining | |
3731 | sections apply to all I/Os for the reporting group. 250=0.04% means that | |
3732 | 0.04% of the I/Os completed in under 250us. 500=64.11% means that 64.11% | |
3733 | of the I/Os required 250 to 499us for completion. | |
3734 | ||
f80dba8d MT |
3735 | **cpu** |
3736 | CPU usage. User and system time, along with the number of context | |
3737 | switches this thread went through, usage of system and user time, and | |
3738 | finally the number of major and minor page faults. The CPU utilization | |
3739 | numbers are averages for the jobs in that reporting group, while the | |
23a8e176 | 3740 | context and fault counters are summed. |
f80dba8d MT |
3741 | |
3742 | **IO depths** | |
a2140525 SW |
3743 | The distribution of I/O depths over the job lifetime. The numbers are |
3744 | divided into powers of 2 and each entry covers depths from that value | |
3745 | up to those that are lower than the next entry -- e.g., 16= covers | |
3746 | depths from 16 to 31. Note that the range covered by a depth | |
3747 | distribution entry can be different to the range covered by the | |
3748 | equivalent submit/complete distribution entry. | |
f80dba8d MT |
3749 | |
3750 | **IO submit** | |
3751 | How many pieces of I/O were submitting in a single submit call. Each | |
c60ebc45 | 3752 | entry denotes that amount and below, until the previous entry -- e.g., |
a2140525 SW |
3753 | 16=100% means that we submitted anywhere between 9 to 16 I/Os per submit |
3754 | call. Note that the range covered by a submit distribution entry can | |
3755 | be different to the range covered by the equivalent depth distribution | |
3756 | entry. | |
f80dba8d MT |
3757 | |
3758 | **IO complete** | |
3759 | Like the above submit number, but for completions instead. | |
3760 | ||
36214730 SW |
3761 | **IO issued rwt** |
3762 | The number of read/write/trim requests issued, and how many of them were | |
3763 | short or dropped. | |
f80dba8d | 3764 | |
29092211 | 3765 | **IO latency** |
ee21ebee | 3766 | These values are for :option:`latency_target` and related options. When |
29092211 VF |
3767 | these options are engaged, this section describes the I/O depth required |
3768 | to meet the specified latency target. | |
71bfa161 | 3769 | |
36214730 SW |
3770 | .. |
3771 | Example output was based on the following: | |
3772 | TZ=UTC fio --ioengine=null --iodepth=2 --size=100M --numjobs=2 \ | |
3773 | --rate_process=poisson --io_limit=32M --name=read --bs=128k \ | |
3774 | --rate=11M --name=write --rw=write --bs=2k --rate=700k | |
3775 | ||
71bfa161 | 3776 | After each client has been listed, the group statistics are printed. They |
f80dba8d | 3777 | will look like this:: |
71bfa161 | 3778 | |
f80dba8d | 3779 | Run status group 0 (all jobs): |
36214730 SW |
3780 | 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 |
3781 | WRITE: bw=1231KiB/s (1261kB/s), 616KiB/s-621KiB/s (630kB/s-636kB/s), io=64.0MiB (67.1MB), run=52747-53223msec | |
71bfa161 | 3782 | |
36214730 | 3783 | For each data direction it prints: |
71bfa161 | 3784 | |
36214730 SW |
3785 | **bw** |
3786 | Aggregate bandwidth of threads in this group followed by the | |
3787 | minimum and maximum bandwidth of all the threads in this group. | |
3788 | Values outside of brackets are power-of-2 format and those | |
3789 | within are the equivalent value in a power-of-10 format. | |
f80dba8d | 3790 | **io** |
36214730 SW |
3791 | Aggregate I/O performed of all threads in this group. The |
3792 | format is the same as bw. | |
3793 | **run** | |
3794 | The smallest and longest runtimes of the threads in this group. | |
71bfa161 | 3795 | |
f50fbdda | 3796 | And finally, the disk statistics are printed. This is Linux specific. They will look like this:: |
71bfa161 | 3797 | |
f80dba8d MT |
3798 | Disk stats (read/write): |
3799 | sda: ios=16398/16511, merge=30/162, ticks=6853/819634, in_queue=826487, util=100.00% | |
71bfa161 JA |
3800 | |
3801 | Each value is printed for both reads and writes, with reads first. The | |
3802 | numbers denote: | |
3803 | ||
f80dba8d | 3804 | **ios** |
c60ebc45 | 3805 | Number of I/Os performed by all groups. |
f80dba8d | 3806 | **merge** |
007c7be9 | 3807 | Number of merges performed by the I/O scheduler. |
f80dba8d MT |
3808 | **ticks** |
3809 | Number of ticks we kept the disk busy. | |
36214730 | 3810 | **in_queue** |
f80dba8d MT |
3811 | Total time spent in the disk queue. |
3812 | **util** | |
3813 | The disk utilization. A value of 100% means we kept the disk | |
71bfa161 JA |
3814 | busy constantly, 50% would be a disk idling half of the time. |
3815 | ||
f80dba8d MT |
3816 | It is also possible to get fio to dump the current output while it is running, |
3817 | without terminating the job. To do that, send fio the **USR1** signal. You can | |
3818 | also get regularly timed dumps by using the :option:`--status-interval` | |
3819 | parameter, or by creating a file in :file:`/tmp` named | |
3820 | :file:`fio-dump-status`. If fio sees this file, it will unlink it and dump the | |
3821 | current output status. | |
8423bd11 | 3822 | |
71bfa161 | 3823 | |
f80dba8d MT |
3824 | Terse output |
3825 | ------------ | |
71bfa161 | 3826 | |
f80dba8d MT |
3827 | For scripted usage where you typically want to generate tables or graphs of the |
3828 | results, fio can output the results in a semicolon separated format. The format | |
3829 | is one long line of values, such as:: | |
71bfa161 | 3830 | |
f80dba8d MT |
3831 | 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% |
3832 | A description of this job goes here. | |
562c2d2f | 3833 | |
4e757af1 VF |
3834 | The job description (if provided) follows on a second line for terse v2. |
3835 | It appears on the same line for other terse versions. | |
71bfa161 | 3836 | |
a7f77fa6 SW |
3837 | To enable terse output, use the :option:`--minimal` or |
3838 | :option:`--output-format`\=terse command line options. The | |
f80dba8d MT |
3839 | first value is the version of the terse output format. If the output has to be |
3840 | changed for some reason, this number will be incremented by 1 to signify that | |
3841 | change. | |
6820cb3b | 3842 | |
a2c95580 | 3843 | Split up, the format is as follows (comments in brackets denote when a |
007c7be9 | 3844 | field was introduced or whether it's specific to some terse version): |
71bfa161 | 3845 | |
f80dba8d MT |
3846 | :: |
3847 | ||
f50fbdda | 3848 | terse version, fio version [v3], jobname, groupid, error |
f80dba8d MT |
3849 | |
3850 | READ status:: | |
3851 | ||
3852 | Total IO (KiB), bandwidth (KiB/sec), IOPS, runtime (msec) | |
3853 | Submission latency: min, max, mean, stdev (usec) | |
3854 | Completion latency: min, max, mean, stdev (usec) | |
3855 | Completion latency percentiles: 20 fields (see below) | |
3856 | Total latency: min, max, mean, stdev (usec) | |
f50fbdda TK |
3857 | Bw (KiB/s): min, max, aggregate percentage of total, mean, stdev, number of samples [v5] |
3858 | IOPS [v5]: min, max, mean, stdev, number of samples | |
f80dba8d MT |
3859 | |
3860 | WRITE status: | |
3861 | ||
3862 | :: | |
3863 | ||
3864 | Total IO (KiB), bandwidth (KiB/sec), IOPS, runtime (msec) | |
3865 | Submission latency: min, max, mean, stdev (usec) | |
247823cc | 3866 | Completion latency: min, max, mean, stdev (usec) |
f80dba8d MT |
3867 | Completion latency percentiles: 20 fields (see below) |
3868 | Total latency: min, max, mean, stdev (usec) | |
f50fbdda TK |
3869 | Bw (KiB/s): min, max, aggregate percentage of total, mean, stdev, number of samples [v5] |
3870 | IOPS [v5]: min, max, mean, stdev, number of samples | |
a2c95580 AH |
3871 | |
3872 | TRIM status [all but version 3]: | |
3873 | ||
f50fbdda | 3874 | Fields are similar to READ/WRITE status. |
f80dba8d MT |
3875 | |
3876 | CPU usage:: | |
3877 | ||
3878 | user, system, context switches, major faults, minor faults | |
3879 | ||
3880 | I/O depths:: | |
3881 | ||
3882 | <=1, 2, 4, 8, 16, 32, >=64 | |
3883 | ||
3884 | I/O latencies microseconds:: | |
3885 | ||
3886 | <=2, 4, 10, 20, 50, 100, 250, 500, 750, 1000 | |
3887 | ||
3888 | I/O latencies milliseconds:: | |
3889 | ||
3890 | <=2, 4, 10, 20, 50, 100, 250, 500, 750, 1000, 2000, >=2000 | |
3891 | ||
a2c95580 | 3892 | Disk utilization [v3]:: |
f80dba8d | 3893 | |
f50fbdda TK |
3894 | disk name, read ios, write ios, read merges, write merges, read ticks, write ticks, |
3895 | time spent in queue, disk utilization percentage | |
f80dba8d MT |
3896 | |
3897 | Additional Info (dependent on continue_on_error, default off):: | |
3898 | ||
3899 | total # errors, first error code | |
3900 | ||
3901 | Additional Info (dependent on description being set):: | |
3902 | ||
3903 | Text description | |
3904 | ||
3905 | Completion latency percentiles can be a grouping of up to 20 sets, so for the | |
3906 | terse output fio writes all of them. Each field will look like this:: | |
1db92cb6 | 3907 | |
f50fbdda | 3908 | 1.00%=6112 |
1db92cb6 | 3909 | |
f80dba8d | 3910 | which is the Xth percentile, and the `usec` latency associated with it. |
1db92cb6 | 3911 | |
f50fbdda | 3912 | For `Disk utilization`, all disks used by fio are shown. So for each disk there |
f80dba8d | 3913 | will be a disk utilization section. |
f2f788dd | 3914 | |
2fc26c3d | 3915 | Below is a single line containing short names for each of the fields in the |
2831be97 | 3916 | minimal output v3, separated by semicolons:: |
2fc26c3d | 3917 | |
f50fbdda | 3918 | terse_version_3;fio_version;jobname;groupid;error;read_kb;read_bandwidth;read_iops;read_runtime_ms;read_slat_min;read_slat_max;read_slat_mean;read_slat_dev;read_clat_min;read_clat_max;read_clat_mean;read_clat_dev;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;read_lat_max;read_lat_mean;read_lat_dev;read_bw_min;read_bw_max;read_bw_agg_pct;read_bw_mean;read_bw_dev;write_kb;write_bandwidth;write_iops;write_runtime_ms;write_slat_min;write_slat_max;write_slat_mean;write_slat_dev;write_clat_min;write_clat_max;write_clat_mean;write_clat_dev;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;write_lat_max;write_lat_mean;write_lat_dev;write_bw_min;write_bw_max;write_bw_agg_pct;write_bw_mean;write_bw_dev;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 |
2fc26c3d | 3919 | |
4e757af1 VF |
3920 | In client/server mode terse output differs from what appears when jobs are run |
3921 | locally. Disk utilization data is omitted from the standard terse output and | |
3922 | for v3 and later appears on its own separate line at the end of each terse | |
3923 | reporting cycle. | |
3924 | ||
25c8b9d7 | 3925 | |
44c82dba VF |
3926 | JSON output |
3927 | ------------ | |
3928 | ||
3929 | The `json` output format is intended to be both human readable and convenient | |
3930 | for automated parsing. For the most part its sections mirror those of the | |
3931 | `normal` output. The `runtime` value is reported in msec and the `bw` value is | |
3932 | reported in 1024 bytes per second units. | |
3933 | ||
3934 | ||
d29c4a91 VF |
3935 | JSON+ output |
3936 | ------------ | |
3937 | ||
3938 | The `json+` output format is identical to the `json` output format except that it | |
3939 | adds a full dump of the completion latency bins. Each `bins` object contains a | |
3940 | set of (key, value) pairs where keys are latency durations and values count how | |
3941 | many I/Os had completion latencies of the corresponding duration. For example, | |
3942 | consider: | |
3943 | ||
3944 | "bins" : { "87552" : 1, "89600" : 1, "94720" : 1, "96768" : 1, "97792" : 1, "99840" : 1, "100864" : 2, "103936" : 6, "104960" : 534, "105984" : 5995, "107008" : 7529, ... } | |
3945 | ||
3946 | This data indicates that one I/O required 87,552ns to complete, two I/Os required | |
3947 | 100,864ns to complete, and 7529 I/Os required 107,008ns to complete. | |
3948 | ||
3949 | Also included with fio is a Python script `fio_jsonplus_clat2csv` that takes | |
3950 | json+ output and generates CSV-formatted latency data suitable for plotting. | |
3951 | ||
3952 | The latency durations actually represent the midpoints of latency intervals. | |
f50fbdda | 3953 | For details refer to :file:`stat.h`. |
d29c4a91 VF |
3954 | |
3955 | ||
f80dba8d MT |
3956 | Trace file format |
3957 | ----------------- | |
3958 | ||
3959 | There are two trace file format that you can encounter. The older (v1) format is | |
3960 | unsupported since version 1.20-rc3 (March 2008). It will still be described | |
25c8b9d7 PD |
3961 | below in case that you get an old trace and want to understand it. |
3962 | ||
3963 | In any case the trace is a simple text file with a single action per line. | |
3964 | ||
3965 | ||
f80dba8d MT |
3966 | Trace file format v1 |
3967 | ~~~~~~~~~~~~~~~~~~~~ | |
3968 | ||
3969 | Each line represents a single I/O action in the following format:: | |
3970 | ||
3971 | rw, offset, length | |
25c8b9d7 | 3972 | |
f50fbdda | 3973 | where `rw=0/1` for read/write, and the `offset` and `length` entries being in bytes. |
25c8b9d7 | 3974 | |
22413915 | 3975 | This format is not supported in fio versions >= 1.20-rc3. |
25c8b9d7 | 3976 | |
25c8b9d7 | 3977 | |
f80dba8d MT |
3978 | Trace file format v2 |
3979 | ~~~~~~~~~~~~~~~~~~~~ | |
25c8b9d7 | 3980 | |
f80dba8d MT |
3981 | The second version of the trace file format was added in fio version 1.17. It |
3982 | allows to access more then one file per trace and has a bigger set of possible | |
3983 | file actions. | |
25c8b9d7 | 3984 | |
f80dba8d | 3985 | The first line of the trace file has to be:: |
25c8b9d7 | 3986 | |
f80dba8d | 3987 | fio version 2 iolog |
25c8b9d7 PD |
3988 | |
3989 | Following this can be lines in two different formats, which are described below. | |
3990 | ||
f80dba8d | 3991 | The file management format:: |
25c8b9d7 | 3992 | |
f80dba8d | 3993 | filename action |
25c8b9d7 | 3994 | |
f50fbdda | 3995 | The `filename` is given as an absolute path. The `action` can be one of these: |
25c8b9d7 | 3996 | |
f80dba8d | 3997 | **add** |
f50fbdda | 3998 | Add the given `filename` to the trace. |
f80dba8d | 3999 | **open** |
f50fbdda | 4000 | Open the file with the given `filename`. The `filename` has to have |
f80dba8d MT |
4001 | been added with the **add** action before. |
4002 | **close** | |
f50fbdda | 4003 | Close the file with the given `filename`. The file has to have been |
f80dba8d MT |
4004 | opened before. |
4005 | ||
4006 | ||
4007 | The file I/O action format:: | |
4008 | ||
4009 | filename action offset length | |
4010 | ||
4011 | The `filename` is given as an absolute path, and has to have been added and | |
4012 | opened before it can be used with this format. The `offset` and `length` are | |
4013 | given in bytes. The `action` can be one of these: | |
4014 | ||
4015 | **wait** | |
4016 | Wait for `offset` microseconds. Everything below 100 is discarded. | |
4017 | The time is relative to the previous `wait` statement. | |
4018 | **read** | |
4019 | Read `length` bytes beginning from `offset`. | |
4020 | **write** | |
4021 | Write `length` bytes beginning from `offset`. | |
4022 | **sync** | |
4023 | :manpage:`fsync(2)` the file. | |
4024 | **datasync** | |
4025 | :manpage:`fdatasync(2)` the file. | |
4026 | **trim** | |
4027 | Trim the given file from the given `offset` for `length` bytes. | |
4028 | ||
b9921d1a DZ |
4029 | |
4030 | I/O Replay - Merging Traces | |
4031 | --------------------------- | |
4032 | ||
4033 | Colocation is a common practice used to get the most out of a machine. | |
4034 | Knowing which workloads play nicely with each other and which ones don't is | |
4035 | a much harder task. While fio can replay workloads concurrently via multiple | |
4036 | jobs, it leaves some variability up to the scheduler making results harder to | |
4037 | reproduce. Merging is a way to make the order of events consistent. | |
4038 | ||
4039 | Merging is integrated into I/O replay and done when a | |
4040 | :option:`merge_blktrace_file` is specified. The list of files passed to | |
4041 | :option:`read_iolog` go through the merge process and output a single file | |
4042 | stored to the specified file. The output file is passed on as if it were the | |
4043 | only file passed to :option:`read_iolog`. An example would look like:: | |
4044 | ||
4045 | $ fio --read_iolog="<file1>:<file2>" --merge_blktrace_file="<output_file>" | |
4046 | ||
4047 | Creating only the merged file can be done by passing the command line argument | |
d443e3af | 4048 | :option:`--merge-blktrace-only`. |
b9921d1a | 4049 | |
87a48ada DZ |
4050 | Scaling traces can be done to see the relative impact of any particular trace |
4051 | being slowed down or sped up. :option:`merge_blktrace_scalars` takes in a colon | |
4052 | separated list of percentage scalars. It is index paired with the files passed | |
4053 | to :option:`read_iolog`. | |
4054 | ||
55bfd8c8 DZ |
4055 | With scaling, it may be desirable to match the running time of all traces. |
4056 | This can be done with :option:`merge_blktrace_iters`. It is index paired with | |
4057 | :option:`read_iolog` just like :option:`merge_blktrace_scalars`. | |
4058 | ||
4059 | In an example, given two traces, A and B, each 60s long. If we want to see | |
4060 | the impact of trace A issuing IOs twice as fast and repeat trace A over the | |
4061 | runtime of trace B, the following can be done:: | |
4062 | ||
4063 | $ fio --read_iolog="<trace_a>:"<trace_b>" --merge_blktrace_file"<output_file>" --merge_blktrace_scalars="50:100" --merge_blktrace_iters="2:1" | |
4064 | ||
4065 | This runs trace A at 2x the speed twice for approximately the same runtime as | |
4066 | a single run of trace B. | |
4067 | ||
b9921d1a | 4068 | |
f80dba8d MT |
4069 | CPU idleness profiling |
4070 | ---------------------- | |
4071 | ||
4072 | In some cases, we want to understand CPU overhead in a test. For example, we | |
4073 | test patches for the specific goodness of whether they reduce CPU usage. | |
4074 | Fio implements a balloon approach to create a thread per CPU that runs at idle | |
4075 | priority, meaning that it only runs when nobody else needs the cpu. | |
4076 | By measuring the amount of work completed by the thread, idleness of each CPU | |
4077 | can be derived accordingly. | |
4078 | ||
4079 | An unit work is defined as touching a full page of unsigned characters. Mean and | |
4080 | standard deviation of time to complete an unit work is reported in "unit work" | |
4081 | section. Options can be chosen to report detailed percpu idleness or overall | |
4082 | system idleness by aggregating percpu stats. | |
4083 | ||
4084 | ||
4085 | Verification and triggers | |
4086 | ------------------------- | |
4087 | ||
4088 | Fio is usually run in one of two ways, when data verification is done. The first | |
4089 | is a normal write job of some sort with verify enabled. When the write phase has | |
4090 | completed, fio switches to reads and verifies everything it wrote. The second | |
4091 | model is running just the write phase, and then later on running the same job | |
4092 | (but with reads instead of writes) to repeat the same I/O patterns and verify | |
4093 | the contents. Both of these methods depend on the write phase being completed, | |
4094 | as fio otherwise has no idea how much data was written. | |
4095 | ||
4096 | With verification triggers, fio supports dumping the current write state to | |
4097 | local files. Then a subsequent read verify workload can load this state and know | |
4098 | exactly where to stop. This is useful for testing cases where power is cut to a | |
4099 | server in a managed fashion, for instance. | |
99b9a85a JA |
4100 | |
4101 | A verification trigger consists of two things: | |
4102 | ||
f80dba8d MT |
4103 | 1) Storing the write state of each job. |
4104 | 2) Executing a trigger command. | |
99b9a85a | 4105 | |
f80dba8d MT |
4106 | The write state is relatively small, on the order of hundreds of bytes to single |
4107 | kilobytes. It contains information on the number of completions done, the last X | |
4108 | completions, etc. | |
99b9a85a | 4109 | |
f80dba8d MT |
4110 | A trigger is invoked either through creation ('touch') of a specified file in |
4111 | the system, or through a timeout setting. If fio is run with | |
9207a0cb | 4112 | :option:`--trigger-file`\= :file:`/tmp/trigger-file`, then it will continually |
f80dba8d MT |
4113 | check for the existence of :file:`/tmp/trigger-file`. When it sees this file, it |
4114 | will fire off the trigger (thus saving state, and executing the trigger | |
99b9a85a JA |
4115 | command). |
4116 | ||
f80dba8d MT |
4117 | For client/server runs, there's both a local and remote trigger. If fio is |
4118 | running as a server backend, it will send the job states back to the client for | |
4119 | safe storage, then execute the remote trigger, if specified. If a local trigger | |
4120 | is specified, the server will still send back the write state, but the client | |
4121 | will then execute the trigger. | |
99b9a85a | 4122 | |
f80dba8d MT |
4123 | Verification trigger example |
4124 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
99b9a85a | 4125 | |
f50fbdda TK |
4126 | Let's say we want to run a powercut test on the remote Linux machine 'server'. |
4127 | Our write workload is in :file:`write-test.fio`. We want to cut power to 'server' at | |
f80dba8d MT |
4128 | some point during the run, and we'll run this test from the safety or our local |
4129 | machine, 'localbox'. On the server, we'll start the fio backend normally:: | |
99b9a85a | 4130 | |
f80dba8d | 4131 | server# fio --server |
99b9a85a | 4132 | |
f80dba8d | 4133 | and on the client, we'll fire off the workload:: |
99b9a85a | 4134 | |
f80dba8d | 4135 | localbox$ fio --client=server --trigger-file=/tmp/my-trigger --trigger-remote="bash -c \"echo b > /proc/sysrq-triger\"" |
99b9a85a | 4136 | |
f80dba8d | 4137 | We set :file:`/tmp/my-trigger` as the trigger file, and we tell fio to execute:: |
99b9a85a | 4138 | |
f80dba8d | 4139 | echo b > /proc/sysrq-trigger |
99b9a85a | 4140 | |
f80dba8d MT |
4141 | on the server once it has received the trigger and sent us the write state. This |
4142 | will work, but it's not **really** cutting power to the server, it's merely | |
4143 | abruptly rebooting it. If we have a remote way of cutting power to the server | |
4144 | through IPMI or similar, we could do that through a local trigger command | |
4502cb42 | 4145 | instead. Let's assume we have a script that does IPMI reboot of a given hostname, |
f80dba8d MT |
4146 | ipmi-reboot. On localbox, we could then have run fio with a local trigger |
4147 | instead:: | |
99b9a85a | 4148 | |
f80dba8d | 4149 | localbox$ fio --client=server --trigger-file=/tmp/my-trigger --trigger="ipmi-reboot server" |
99b9a85a | 4150 | |
f80dba8d MT |
4151 | For this case, fio would wait for the server to send us the write state, then |
4152 | execute ``ipmi-reboot server`` when that happened. | |
4153 | ||
4154 | Loading verify state | |
4155 | ~~~~~~~~~~~~~~~~~~~~ | |
4156 | ||
4502cb42 | 4157 | To load stored write state, a read verification job file must contain the |
f80dba8d | 4158 | :option:`verify_state_load` option. If that is set, fio will load the previously |
99b9a85a | 4159 | stored state. For a local fio run this is done by loading the files directly, |
f80dba8d MT |
4160 | and on a client/server run, the server backend will ask the client to send the |
4161 | files over and load them from there. | |
a3ae5b05 JA |
4162 | |
4163 | ||
f80dba8d MT |
4164 | Log File Formats |
4165 | ---------------- | |
a3ae5b05 JA |
4166 | |
4167 | Fio supports a variety of log file formats, for logging latencies, bandwidth, | |
4168 | and IOPS. The logs share a common format, which looks like this: | |
4169 | ||
5a83478f | 4170 | *time* (`msec`), *value*, *data direction*, *block size* (`bytes`), |
1a953d97 | 4171 | *offset* (`bytes`), *command priority* |
a3ae5b05 | 4172 | |
5a83478f | 4173 | *Time* for the log entry is always in milliseconds. The *value* logged depends |
a3ae5b05 JA |
4174 | on the type of log, it will be one of the following: |
4175 | ||
f80dba8d | 4176 | **Latency log** |
168bb587 | 4177 | Value is latency in nsecs |
f80dba8d MT |
4178 | **Bandwidth log** |
4179 | Value is in KiB/sec | |
4180 | **IOPS log** | |
4181 | Value is IOPS | |
4182 | ||
4183 | *Data direction* is one of the following: | |
4184 | ||
4185 | **0** | |
4186 | I/O is a READ | |
4187 | **1** | |
4188 | I/O is a WRITE | |
4189 | **2** | |
4190 | I/O is a TRIM | |
4191 | ||
15417073 SW |
4192 | The entry's *block size* is always in bytes. The *offset* is the position in bytes |
4193 | from the start of the file for that particular I/O. The logging of the offset can be | |
5a83478f | 4194 | toggled with :option:`log_offset`. |
f80dba8d | 4195 | |
1a953d97 PC |
4196 | *Command priority* is 0 for normal priority and 1 for high priority. This is controlled |
4197 | by the ioengine specific :option:`cmdprio_percentage`. | |
4198 | ||
15417073 SW |
4199 | Fio defaults to logging every individual I/O but when windowed logging is set |
4200 | through :option:`log_avg_msec`, either the average (by default) or the maximum | |
4201 | (:option:`log_max_value` is set) *value* seen over the specified period of time | |
4202 | is recorded. Each *data direction* seen within the window period will aggregate | |
4203 | its values in a separate row. Further, when using windowed logging the *block | |
4204 | size* and *offset* entries will always contain 0. | |
f80dba8d | 4205 | |
4e757af1 | 4206 | |
b8f7e412 | 4207 | Client/Server |
f80dba8d MT |
4208 | ------------- |
4209 | ||
4210 | Normally fio is invoked as a stand-alone application on the machine where the | |
6cf30ac0 SW |
4211 | I/O workload should be generated. However, the backend and frontend of fio can |
4212 | be run separately i.e., the fio server can generate an I/O workload on the "Device | |
4213 | Under Test" while being controlled by a client on another machine. | |
f80dba8d MT |
4214 | |
4215 | Start the server on the machine which has access to the storage DUT:: | |
4216 | ||
f50fbdda | 4217 | $ fio --server=args |
f80dba8d | 4218 | |
dbb257bb | 4219 | where `args` defines what fio listens to. The arguments are of the form |
f80dba8d MT |
4220 | ``type,hostname`` or ``IP,port``. *type* is either ``ip`` (or ip4) for TCP/IP |
4221 | v4, ``ip6`` for TCP/IP v6, or ``sock`` for a local unix domain socket. | |
4222 | *hostname* is either a hostname or IP address, and *port* is the port to listen | |
4223 | to (only valid for TCP/IP, not a local socket). Some examples: | |
4224 | ||
4225 | 1) ``fio --server`` | |
4226 | ||
4227 | Start a fio server, listening on all interfaces on the default port (8765). | |
4228 | ||
4229 | 2) ``fio --server=ip:hostname,4444`` | |
4230 | ||
4231 | Start a fio server, listening on IP belonging to hostname and on port 4444. | |
4232 | ||
4233 | 3) ``fio --server=ip6:::1,4444`` | |
4234 | ||
4235 | Start a fio server, listening on IPv6 localhost ::1 and on port 4444. | |
4236 | ||
4237 | 4) ``fio --server=,4444`` | |
4238 | ||
4239 | Start a fio server, listening on all interfaces on port 4444. | |
4240 | ||
4241 | 5) ``fio --server=1.2.3.4`` | |
4242 | ||
4243 | Start a fio server, listening on IP 1.2.3.4 on the default port. | |
4244 | ||
4245 | 6) ``fio --server=sock:/tmp/fio.sock`` | |
4246 | ||
dbb257bb | 4247 | Start a fio server, listening on the local socket :file:`/tmp/fio.sock`. |
f80dba8d MT |
4248 | |
4249 | Once a server is running, a "client" can connect to the fio server with:: | |
4250 | ||
4251 | fio <local-args> --client=<server> <remote-args> <job file(s)> | |
4252 | ||
4253 | where `local-args` are arguments for the client where it is running, `server` | |
4254 | is the connect string, and `remote-args` and `job file(s)` are sent to the | |
4255 | server. The `server` string follows the same format as it does on the server | |
4256 | side, to allow IP/hostname/socket and port strings. | |
4257 | ||
4258 | Fio can connect to multiple servers this way:: | |
4259 | ||
4260 | fio --client=<server1> <job file(s)> --client=<server2> <job file(s)> | |
4261 | ||
4262 | If the job file is located on the fio server, then you can tell the server to | |
4263 | load a local file as well. This is done by using :option:`--remote-config` :: | |
4264 | ||
4265 | fio --client=server --remote-config /path/to/file.fio | |
4266 | ||
4267 | Then fio will open this local (to the server) job file instead of being passed | |
4268 | one from the client. | |
4269 | ||
4270 | If you have many servers (example: 100 VMs/containers), you can input a pathname | |
4271 | of a file containing host IPs/names as the parameter value for the | |
4272 | :option:`--client` option. For example, here is an example :file:`host.list` | |
4273 | file containing 2 hostnames:: | |
4274 | ||
4275 | host1.your.dns.domain | |
4276 | host2.your.dns.domain | |
4277 | ||
4278 | The fio command would then be:: | |
a3ae5b05 | 4279 | |
f80dba8d | 4280 | fio --client=host.list <job file(s)> |
a3ae5b05 | 4281 | |
f80dba8d MT |
4282 | In this mode, you cannot input server-specific parameters or job files -- all |
4283 | servers receive the same job file. | |
a3ae5b05 | 4284 | |
f80dba8d MT |
4285 | In order to let ``fio --client`` runs use a shared filesystem from multiple |
4286 | hosts, ``fio --client`` now prepends the IP address of the server to the | |
4502cb42 | 4287 | filename. For example, if fio is using the directory :file:`/mnt/nfs/fio` and is |
f80dba8d MT |
4288 | writing filename :file:`fileio.tmp`, with a :option:`--client` `hostfile` |
4289 | containing two hostnames ``h1`` and ``h2`` with IP addresses 192.168.10.120 and | |
4290 | 192.168.10.121, then fio will create two files:: | |
a3ae5b05 | 4291 | |
f80dba8d MT |
4292 | /mnt/nfs/fio/192.168.10.120.fileio.tmp |
4293 | /mnt/nfs/fio/192.168.10.121.fileio.tmp | |
4e757af1 VF |
4294 | |
4295 | Terse output in client/server mode will differ slightly from what is produced | |
4296 | when fio is run in stand-alone mode. See the terse output section for details. |