Commit | Line | Data |
---|---|---|
f8b8f7da | 1 | .TH fio 1 "December 2014" "User Manual" |
d60e92d1 AC |
2 | .SH NAME |
3 | fio \- flexible I/O tester | |
4 | .SH SYNOPSIS | |
5 | .B fio | |
6 | [\fIoptions\fR] [\fIjobfile\fR]... | |
7 | .SH DESCRIPTION | |
8 | .B fio | |
9 | is a tool that will spawn a number of threads or processes doing a | |
10 | particular type of I/O action as specified by the user. | |
11 | The typical use of fio is to write a job file matching the I/O load | |
12 | one wants to simulate. | |
13 | .SH OPTIONS | |
14 | .TP | |
49da1240 JA |
15 | .BI \-\-debug \fR=\fPtype |
16 | Enable verbose tracing of various fio actions. May be `all' for all types | |
17 | or individual types separated by a comma (eg \-\-debug=io,file). `help' will | |
18 | list all available tracing options. | |
19 | .TP | |
d60e92d1 AC |
20 | .BI \-\-output \fR=\fPfilename |
21 | Write output to \fIfilename\fR. | |
22 | .TP | |
e28ee21d | 23 | .BI \-\-output-format \fR=\fPformat |
513e37ee VF |
24 | Set the reporting format to \fInormal\fR, \fIterse\fR, \fIjson\fR, or |
25 | \fIjson+\fR. Multiple formats can be selected, separate by a comma. \fIterse\fR | |
26 | is a CSV based format. \fIjson+\fR is like \fIjson\fR, except it adds a full | |
27 | dump of the latency buckets. | |
e28ee21d | 28 | .TP |
b2cecdc2 | 29 | .BI \-\-runtime \fR=\fPruntime |
30 | Limit run time to \fIruntime\fR seconds. | |
d60e92d1 | 31 | .TP |
d60e92d1 AC |
32 | .B \-\-bandwidth\-log |
33 | Generate per-job bandwidth logs. | |
34 | .TP | |
35 | .B \-\-minimal | |
d1429b5c | 36 | Print statistics in a terse, semicolon-delimited format. |
d60e92d1 | 37 | .TP |
f6a7df53 JA |
38 | .B \-\-append-terse |
39 | Print statistics in selected mode AND terse, semicolon-delimited format. | |
40 | Deprecated, use \-\-output-format instead to select multiple formats. | |
41 | .TP | |
49da1240 JA |
42 | .B \-\-version |
43 | Display version information and exit. | |
44 | .TP | |
065248bf | 45 | .BI \-\-terse\-version \fR=\fPversion |
4d658652 | 46 | Set terse version output format (Current version 3, or older version 2). |
49da1240 JA |
47 | .TP |
48 | .B \-\-help | |
49 | Display usage information and exit. | |
50 | .TP | |
fec0f21c JA |
51 | .B \-\-cpuclock-test |
52 | Perform test and validation of internal CPU clock | |
53 | .TP | |
54 | .BI \-\-crctest[\fR=\fPtest] | |
55 | Test the speed of the builtin checksumming functions. If no argument is given, | |
56 | all of them are tested. Or a comma separated list can be passed, in which | |
57 | case the given ones are tested. | |
58 | .TP | |
49da1240 JA |
59 | .BI \-\-cmdhelp \fR=\fPcommand |
60 | Print help information for \fIcommand\fR. May be `all' for all commands. | |
61 | .TP | |
de890a1e SL |
62 | .BI \-\-enghelp \fR=\fPioengine[,command] |
63 | List all commands defined by \fIioengine\fR, or print help for \fIcommand\fR defined by \fIioengine\fR. | |
64 | .TP | |
d60e92d1 AC |
65 | .BI \-\-showcmd \fR=\fPjobfile |
66 | Convert \fIjobfile\fR to a set of command-line options. | |
67 | .TP | |
d60e92d1 AC |
68 | .BI \-\-eta \fR=\fPwhen |
69 | Specifies when real-time ETA estimate should be printed. \fIwhen\fR may | |
70 | be one of `always', `never' or `auto'. | |
71 | .TP | |
30b5d57f JA |
72 | .BI \-\-eta\-newline \fR=\fPtime |
73 | Force an ETA newline for every `time` period passed. | |
74 | .TP | |
75 | .BI \-\-status\-interval \fR=\fPtime | |
76 | Report full output status every `time` period passed. | |
77 | .TP | |
49da1240 JA |
78 | .BI \-\-readonly |
79 | Turn on safety read-only checks, preventing any attempted write. | |
80 | .TP | |
c0a5d35e | 81 | .BI \-\-section \fR=\fPsec |
cf145d90 | 82 | Only run section \fIsec\fR from job file. This option can be used multiple times to add more sections to run. |
c0a5d35e | 83 | .TP |
49da1240 JA |
84 | .BI \-\-alloc\-size \fR=\fPkb |
85 | Set the internal smalloc pool size to \fIkb\fP kilobytes. | |
d60e92d1 | 86 | .TP |
49da1240 JA |
87 | .BI \-\-warnings\-fatal |
88 | All fio parser warnings are fatal, causing fio to exit with an error. | |
9183788d | 89 | .TP |
49da1240 | 90 | .BI \-\-max\-jobs \fR=\fPnr |
57e118a2 | 91 | Set the maximum allowed number of jobs (threads/processes) to support. |
d60e92d1 | 92 | .TP |
49da1240 JA |
93 | .BI \-\-server \fR=\fPargs |
94 | Start a backend server, with \fIargs\fP specifying what to listen to. See client/server section. | |
f57a9c59 | 95 | .TP |
49da1240 JA |
96 | .BI \-\-daemonize \fR=\fPpidfile |
97 | Background a fio server, writing the pid to the given pid file. | |
98 | .TP | |
99 | .BI \-\-client \fR=\fPhost | |
39b5f61e | 100 | Instead of running the jobs locally, send and run them on the given host or set of hosts. See client/server section. |
f2a2ce0e HL |
101 | .TP |
102 | .BI \-\-idle\-prof \fR=\fPoption | |
103 | Report cpu idleness on a system or percpu basis (\fIoption\fP=system,percpu) or run unit work calibration only (\fIoption\fP=calibrate). | |
d60e92d1 AC |
104 | .SH "JOB FILE FORMAT" |
105 | Job files are in `ini' format. They consist of one or more | |
106 | job definitions, which begin with a job name in square brackets and | |
107 | extend to the next job name. The job name can be any ASCII string | |
108 | except `global', which has a special meaning. Following the job name is | |
109 | a sequence of zero or more parameters, one per line, that define the | |
110 | behavior of the job. Any line starting with a `;' or `#' character is | |
d1429b5c | 111 | considered a comment and ignored. |
d9956b64 AC |
112 | .P |
113 | If \fIjobfile\fR is specified as `-', the job file will be read from | |
114 | standard input. | |
d60e92d1 AC |
115 | .SS "Global Section" |
116 | The global section contains default parameters for jobs specified in the | |
117 | job file. A job is only affected by global sections residing above it, | |
118 | and there may be any number of global sections. Specific job definitions | |
119 | may override any parameter set in global sections. | |
120 | .SH "JOB PARAMETERS" | |
121 | .SS Types | |
b470a02c SC |
122 | Some parameters may take arguments of a specific type. |
123 | Anywhere a numeric value is required, an arithmetic expression may be used, | |
d59aa780 JA |
124 | provided it is surrounded by parentheses. Supported operators are: |
125 | .RS | |
126 | .RS | |
127 | .TP | |
128 | .B addition (+) | |
129 | .TP | |
130 | .B subtraction (-) | |
131 | .TP | |
132 | .B multiplication (*) | |
133 | .TP | |
134 | .B division (/) | |
135 | .TP | |
136 | .B modulus (%) | |
137 | .TP | |
138 | .B exponentiation (^) | |
139 | .RE | |
140 | .RE | |
141 | .P | |
142 | For time values in expressions, units are microseconds by default. This is | |
143 | different than for time values not in expressions (not enclosed in | |
144 | parentheses). The types used are: | |
d60e92d1 AC |
145 | .TP |
146 | .I str | |
147 | String: a sequence of alphanumeric characters. | |
148 | .TP | |
149 | .I int | |
d60e92d1 | 150 | SI integer: a whole number, possibly containing a suffix denoting the base unit |
b09da8fa JA |
151 | of the value. Accepted suffixes are `k', 'M', 'G', 'T', and 'P', denoting |
152 | kilo (1024), mega (1024^2), giga (1024^3), tera (1024^4), and peta (1024^5) | |
74454ce4 CE |
153 | respectively. If prefixed with '0x', the value is assumed to be base 16 |
154 | (hexadecimal). A suffix may include a trailing 'b', for instance 'kb' is | |
155 | identical to 'k'. You can specify a base 10 value by using 'KiB', 'MiB','GiB', | |
156 | etc. This is useful for disk drives where values are often given in base 10 | |
157 | values. Specifying '30GiB' will get you 30*1000^3 bytes. | |
158 | When specifying times the default suffix meaning changes, still denoting the | |
159 | base unit of the value, but accepted suffixes are 'D' (days), 'H' (hours), 'M' | |
0de5b26f JA |
160 | (minutes), 'S' Seconds, 'ms' (or msec) milli seconds, 'us' (or 'usec') micro |
161 | seconds. Time values without a unit specify seconds. | |
74454ce4 | 162 | The suffixes are not case sensitive. |
d60e92d1 AC |
163 | .TP |
164 | .I bool | |
165 | Boolean: a true or false value. `0' denotes false, `1' denotes true. | |
166 | .TP | |
167 | .I irange | |
168 | Integer range: a range of integers specified in the format | |
d1429b5c AC |
169 | \fIlower\fR:\fIupper\fR or \fIlower\fR\-\fIupper\fR. \fIlower\fR and |
170 | \fIupper\fR may contain a suffix as described above. If an option allows two | |
171 | sets of ranges, they are separated with a `,' or `/' character. For example: | |
172 | `8\-8k/8M\-4G'. | |
83349190 YH |
173 | .TP |
174 | .I float_list | |
175 | List of floating numbers: A list of floating numbers, separated by | |
cecbfd47 | 176 | a ':' character. |
d60e92d1 AC |
177 | .SS "Parameter List" |
178 | .TP | |
179 | .BI name \fR=\fPstr | |
d9956b64 | 180 | May be used to override the job name. On the command line, this parameter |
d60e92d1 AC |
181 | has the special purpose of signalling the start of a new job. |
182 | .TP | |
9cc8cb91 AK |
183 | .BI wait_for \fR=\fPstr |
184 | Specifies the name of the already defined job to wait for. Single waitee name | |
185 | only may be specified. If set, the job won't be started until all workers of | |
186 | the waitee job are done. Wait_for operates on the job name basis, so there are | |
187 | a few limitations. First, the waitee must be defined prior to the waiter job | |
188 | (meaning no forward references). Second, if a job is being referenced as a | |
189 | waitee, it must have a unique name (no duplicate waitees). | |
190 | .TP | |
d60e92d1 AC |
191 | .BI description \fR=\fPstr |
192 | Human-readable description of the job. It is printed when the job is run, but | |
193 | otherwise has no special purpose. | |
194 | .TP | |
195 | .BI directory \fR=\fPstr | |
196 | Prefix filenames with this directory. Used to place files in a location other | |
197 | than `./'. | |
bcbfeefa CE |
198 | You can specify a number of directories by separating the names with a ':' |
199 | character. These directories will be assigned equally distributed to job clones | |
200 | creates with \fInumjobs\fR as long as they are using generated filenames. | |
201 | If specific \fIfilename(s)\fR are set fio will use the first listed directory, | |
202 | and thereby matching the \fIfilename\fR semantic which generates a file each | |
67445b63 JA |
203 | clone if not specified, but let all clones use the same if set. See |
204 | \fIfilename\fR for considerations regarding escaping certain characters on | |
205 | some platforms. | |
d60e92d1 AC |
206 | .TP |
207 | .BI filename \fR=\fPstr | |
208 | .B fio | |
209 | normally makes up a file name based on the job name, thread number, and file | |
d1429b5c | 210 | number. If you want to share files between threads in a job or several jobs, |
de890a1e SL |
211 | specify a \fIfilename\fR for each of them to override the default. |
212 | If the I/O engine is file-based, you can specify | |
d1429b5c AC |
213 | a number of files by separating the names with a `:' character. `\-' is a |
214 | reserved name, meaning stdin or stdout, depending on the read/write direction | |
67445b63 JA |
215 | set. On Windows, disk devices are accessed as \\.\PhysicalDrive0 for the first |
216 | device, \\.\PhysicalDrive1 for the second etc. Note: Windows and FreeBSD | |
217 | prevent write access to areas of the disk containing in-use data | |
218 | (e.g. filesystems). If the wanted filename does need to include a colon, then | |
4904acd5 JM |
219 | escape that with a '\\' character. For instance, if the filename is |
220 | "/dev/dsk/foo@3,0:c", then you would use filename="/dev/dsk/foo@3,0\\:c". | |
d60e92d1 | 221 | .TP |
de98bd30 | 222 | .BI filename_format \fR=\fPstr |
ce594fbe | 223 | If sharing multiple files between jobs, it is usually necessary to have |
de98bd30 JA |
224 | fio generate the exact names that you want. By default, fio will name a file |
225 | based on the default file format specification of | |
226 | \fBjobname.jobnumber.filenumber\fP. With this option, that can be | |
227 | customized. Fio will recognize and replace the following keywords in this | |
228 | string: | |
229 | .RS | |
230 | .RS | |
231 | .TP | |
232 | .B $jobname | |
233 | The name of the worker thread or process. | |
234 | .TP | |
235 | .B $jobnum | |
236 | The incremental number of the worker thread or process. | |
237 | .TP | |
238 | .B $filenum | |
239 | The incremental number of the file for that worker thread or process. | |
240 | .RE | |
241 | .P | |
242 | To have dependent jobs share a set of files, this option can be set to | |
243 | have fio generate filenames that are shared between the two. For instance, | |
244 | if \fBtestfiles.$filenum\fR is specified, file number 4 for any job will | |
245 | be named \fBtestfiles.4\fR. The default of \fB$jobname.$jobnum.$filenum\fR | |
246 | will be used if no other format specifier is given. | |
247 | .RE | |
248 | .P | |
249 | .TP | |
3ce9dcaf JA |
250 | .BI lockfile \fR=\fPstr |
251 | Fio defaults to not locking any files before it does IO to them. If a file or | |
252 | file descriptor is shared, fio can serialize IO to that file to make the end | |
253 | result consistent. This is usual for emulating real workloads that share files. | |
254 | The lock modes are: | |
255 | .RS | |
256 | .RS | |
257 | .TP | |
258 | .B none | |
259 | No locking. This is the default. | |
260 | .TP | |
261 | .B exclusive | |
cf145d90 | 262 | Only one thread or process may do IO at a time, excluding all others. |
3ce9dcaf JA |
263 | .TP |
264 | .B readwrite | |
265 | Read-write locking on the file. Many readers may access the file at the same | |
266 | time, but writes get exclusive access. | |
267 | .RE | |
ce594fbe | 268 | .RE |
3ce9dcaf | 269 | .P |
d60e92d1 AC |
270 | .BI opendir \fR=\fPstr |
271 | Recursively open any files below directory \fIstr\fR. | |
272 | .TP | |
273 | .BI readwrite \fR=\fPstr "\fR,\fP rw" \fR=\fPstr | |
274 | Type of I/O pattern. Accepted values are: | |
275 | .RS | |
276 | .RS | |
277 | .TP | |
278 | .B read | |
d1429b5c | 279 | Sequential reads. |
d60e92d1 AC |
280 | .TP |
281 | .B write | |
d1429b5c | 282 | Sequential writes. |
d60e92d1 | 283 | .TP |
fa769d44 SW |
284 | .B trim |
285 | Sequential trim (Linux block devices only). | |
286 | .TP | |
d60e92d1 | 287 | .B randread |
d1429b5c | 288 | Random reads. |
d60e92d1 AC |
289 | .TP |
290 | .B randwrite | |
d1429b5c | 291 | Random writes. |
d60e92d1 | 292 | .TP |
fa769d44 SW |
293 | .B randtrim |
294 | Random trim (Linux block devices only). | |
295 | .TP | |
10b023db | 296 | .B rw, readwrite |
d1429b5c | 297 | Mixed sequential reads and writes. |
d60e92d1 | 298 | .TP |
ff6bb260 | 299 | .B randrw |
d1429b5c | 300 | Mixed random reads and writes. |
82a90686 JA |
301 | .TP |
302 | .B trimwrite | |
303 | Trim and write mixed workload. Blocks will be trimmed first, then the same | |
304 | blocks will be written to. | |
d60e92d1 AC |
305 | .RE |
306 | .P | |
38dad62d JA |
307 | For mixed I/O, the default split is 50/50. For certain types of io the result |
308 | may still be skewed a bit, since the speed may be different. It is possible to | |
3b7fa9ec | 309 | specify a number of IO's to do before getting a new offset, this is done by |
38dad62d JA |
310 | appending a `:\fI<nr>\fR to the end of the string given. For a random read, it |
311 | would look like \fBrw=randread:8\fR for passing in an offset modifier with a | |
059b0802 JA |
312 | value of 8. If the postfix is used with a sequential IO pattern, then the value |
313 | specified will be added to the generated offset for each IO. For instance, | |
314 | using \fBrw=write:4k\fR will skip 4k for every write. It turns sequential IO | |
315 | into sequential IO with holes. See the \fBrw_sequencer\fR option. | |
d60e92d1 AC |
316 | .RE |
317 | .TP | |
38dad62d JA |
318 | .BI rw_sequencer \fR=\fPstr |
319 | If an offset modifier is given by appending a number to the \fBrw=<str>\fR line, | |
320 | then this option controls how that number modifies the IO offset being | |
321 | generated. Accepted values are: | |
322 | .RS | |
323 | .RS | |
324 | .TP | |
325 | .B sequential | |
326 | Generate sequential offset | |
327 | .TP | |
328 | .B identical | |
329 | Generate the same offset | |
330 | .RE | |
331 | .P | |
332 | \fBsequential\fR is only useful for random IO, where fio would normally | |
333 | generate a new random offset for every IO. If you append eg 8 to randread, you | |
334 | would get a new random offset for every 8 IO's. The result would be a seek for | |
335 | only every 8 IO's, instead of for every IO. Use \fBrw=randread:8\fR to specify | |
336 | that. As sequential IO is already sequential, setting \fBsequential\fR for that | |
337 | would not result in any differences. \fBidentical\fR behaves in a similar | |
338 | fashion, except it sends the same offset 8 number of times before generating a | |
339 | new offset. | |
340 | .RE | |
341 | .P | |
342 | .TP | |
90fef2d1 JA |
343 | .BI kb_base \fR=\fPint |
344 | The base unit for a kilobyte. The defacto base is 2^10, 1024. Storage | |
345 | manufacturers like to use 10^3 or 1000 as a base ten unit instead, for obvious | |
5c9323fb | 346 | reasons. Allowed values are 1024 or 1000, with 1024 being the default. |
90fef2d1 | 347 | .TP |
771e58be JA |
348 | .BI unified_rw_reporting \fR=\fPbool |
349 | Fio normally reports statistics on a per data direction basis, meaning that | |
350 | read, write, and trim are accounted and reported separately. If this option is | |
cf145d90 | 351 | set fio sums the results and reports them as "mixed" instead. |
771e58be | 352 | .TP |
d60e92d1 | 353 | .BI randrepeat \fR=\fPbool |
56e2a5fc CE |
354 | Seed the random number generator used for random I/O patterns in a predictable |
355 | way so the pattern is repeatable across runs. Default: true. | |
356 | .TP | |
357 | .BI allrandrepeat \fR=\fPbool | |
358 | Seed all random number generators in a predictable way so results are | |
359 | repeatable across runs. Default: false. | |
d60e92d1 | 360 | .TP |
04778baf JA |
361 | .BI randseed \fR=\fPint |
362 | Seed the random number generators based on this seed value, to be able to | |
363 | control what sequence of output is being generated. If not set, the random | |
364 | sequence depends on the \fBrandrepeat\fR setting. | |
365 | .TP | |
a596f047 EG |
366 | .BI fallocate \fR=\fPstr |
367 | Whether pre-allocation is performed when laying down files. Accepted values | |
368 | are: | |
369 | .RS | |
370 | .RS | |
371 | .TP | |
372 | .B none | |
373 | Do not pre-allocate space. | |
374 | .TP | |
375 | .B posix | |
ccc2b328 | 376 | Pre-allocate via \fBposix_fallocate\fR\|(3). |
a596f047 EG |
377 | .TP |
378 | .B keep | |
ccc2b328 | 379 | Pre-allocate via \fBfallocate\fR\|(2) with FALLOC_FL_KEEP_SIZE set. |
a596f047 EG |
380 | .TP |
381 | .B 0 | |
382 | Backward-compatible alias for 'none'. | |
383 | .TP | |
384 | .B 1 | |
385 | Backward-compatible alias for 'posix'. | |
386 | .RE | |
387 | .P | |
388 | May not be available on all supported platforms. 'keep' is only | |
389 | available on Linux. If using ZFS on Solaris this must be set to 'none' | |
390 | because ZFS doesn't support it. Default: 'posix'. | |
391 | .RE | |
7bc8c2cf | 392 | .TP |
d60e92d1 | 393 | .BI fadvise_hint \fR=\fPbool |
cf145d90 | 394 | Use \fBposix_fadvise\fR\|(2) to advise the kernel what I/O patterns |
d1429b5c | 395 | are likely to be issued. Default: true. |
d60e92d1 | 396 | .TP |
37659335 JA |
397 | .BI fadvise_stream \fR=\fPint |
398 | Use \fBposix_fadvise\fR\|(2) to advise the kernel what stream ID the | |
399 | writes issued belong to. Only supported on Linux. Note, this option | |
400 | may change going forward. | |
401 | .TP | |
f7fa2653 | 402 | .BI size \fR=\fPint |
d60e92d1 | 403 | Total size of I/O for this job. \fBfio\fR will run until this many bytes have |
a4d3b4db JA |
404 | been transferred, unless limited by other options (\fBruntime\fR, for instance, |
405 | or increased/descreased by \fBio_size\fR). Unless \fBnrfiles\fR and | |
406 | \fBfilesize\fR options are given, this amount will be divided between the | |
407 | available files for the job. If not set, fio will use the full size of the | |
408 | given files or devices. If the files do not exist, size must be given. It is | |
409 | also possible to give size as a percentage between 1 and 100. If size=20% is | |
410 | given, fio will use 20% of the full size of the given files or devices. | |
411 | .TP | |
412 | .BI io_size \fR=\fPint "\fR,\fB io_limit \fR=\fPint | |
77731b29 JA |
413 | Normally fio operates within the region set by \fBsize\fR, which means that |
414 | the \fBsize\fR option sets both the region and size of IO to be performed. | |
415 | Sometimes that is not what you want. With this option, it is possible to | |
416 | define just the amount of IO that fio should do. For instance, if \fBsize\fR | |
417 | is set to 20G and \fBio_limit\fR is set to 5G, fio will perform IO within | |
a4d3b4db JA |
418 | the first 20G but exit when 5G have been done. The opposite is also |
419 | possible - if \fBsize\fR is set to 20G, and \fBio_size\fR is set to 40G, then | |
420 | fio will do 40G of IO within the 0..20G region. | |
d60e92d1 | 421 | .TP |
74586c1e | 422 | .BI fill_device \fR=\fPbool "\fR,\fB fill_fs" \fR=\fPbool |
3ce9dcaf JA |
423 | Sets size to something really large and waits for ENOSPC (no space left on |
424 | device) as the terminating condition. Only makes sense with sequential write. | |
425 | For a read workload, the mount point will be filled first then IO started on | |
4f12432e JA |
426 | the result. This option doesn't make sense if operating on a raw device node, |
427 | since the size of that is already known by the file system. Additionally, | |
428 | writing beyond end-of-device will not return ENOSPC there. | |
3ce9dcaf | 429 | .TP |
d60e92d1 AC |
430 | .BI filesize \fR=\fPirange |
431 | Individual file sizes. May be a range, in which case \fBfio\fR will select sizes | |
d1429b5c AC |
432 | for files at random within the given range, limited to \fBsize\fR in total (if |
433 | that is given). If \fBfilesize\fR is not specified, each created file is the | |
434 | same size. | |
d60e92d1 | 435 | .TP |
bedc9dc2 JA |
436 | .BI file_append \fR=\fPbool |
437 | Perform IO after the end of the file. Normally fio will operate within the | |
438 | size of a file. If this option is set, then fio will append to the file | |
439 | instead. This has identical behavior to setting \fRoffset\fP to the size | |
0aae4ce7 | 440 | of a file. This option is ignored on non-regular files. |
bedc9dc2 | 441 | .TP |
f7fa2653 | 442 | .BI blocksize \fR=\fPint[,int] "\fR,\fB bs" \fR=\fPint[,int] |
d9472271 JA |
443 | Block size for I/O units. Default: 4k. Values for reads, writes, and trims |
444 | can be specified separately in the format \fIread\fR,\fIwrite\fR,\fItrim\fR | |
445 | either of which may be empty to leave that value at its default. If a trailing | |
446 | comma isn't given, the remainder will inherit the last value set. | |
d60e92d1 | 447 | .TP |
9183788d | 448 | .BI blocksize_range \fR=\fPirange[,irange] "\fR,\fB bsrange" \fR=\fPirange[,irange] |
d1429b5c AC |
449 | Specify a range of I/O block sizes. The issued I/O unit will always be a |
450 | multiple of the minimum size, unless \fBblocksize_unaligned\fR is set. Applies | |
9183788d | 451 | to both reads and writes if only one range is given, but can be specified |
de8f6de9 | 452 | separately with a comma separating the values. Example: bsrange=1k-4k,2k-8k. |
9183788d JA |
453 | Also (see \fBblocksize\fR). |
454 | .TP | |
455 | .BI bssplit \fR=\fPstr | |
456 | This option allows even finer grained control of the block sizes issued, | |
457 | not just even splits between them. With this option, you can weight various | |
458 | block sizes for exact control of the issued IO for a job that has mixed | |
459 | block sizes. The format of the option is bssplit=blocksize/percentage, | |
5982a925 | 460 | optionally adding as many definitions as needed separated by a colon. |
9183788d | 461 | Example: bssplit=4k/10:64k/50:32k/40 would issue 50% 64k blocks, 10% 4k |
c83cdd3e JA |
462 | blocks and 40% 32k blocks. \fBbssplit\fR also supports giving separate |
463 | splits to reads and writes. The format is identical to what the | |
464 | \fBbs\fR option accepts, the read and write parts are separated with a | |
465 | comma. | |
d60e92d1 AC |
466 | .TP |
467 | .B blocksize_unaligned\fR,\fP bs_unaligned | |
d1429b5c AC |
468 | If set, any size in \fBblocksize_range\fR may be used. This typically won't |
469 | work with direct I/O, as that normally requires sector alignment. | |
d60e92d1 | 470 | .TP |
2b7a01d0 | 471 | .BI blockalign \fR=\fPint[,int] "\fR,\fB ba" \fR=\fPint[,int] |
639ce0f3 MS |
472 | At what boundary to align random IO offsets. Defaults to the same as 'blocksize' |
473 | the minimum blocksize given. Minimum alignment is typically 512b | |
2b7a01d0 JA |
474 | for using direct IO, though it usually depends on the hardware block size. |
475 | This option is mutually exclusive with using a random map for files, so it | |
476 | will turn off that option. | |
43602667 | 477 | .TP |
6aca9b3d JA |
478 | .BI bs_is_seq_rand \fR=\fPbool |
479 | If this option is set, fio will use the normal read,write blocksize settings as | |
480 | sequential,random instead. Any random read or write will use the WRITE | |
481 | blocksize settings, and any sequential read or write will use the READ | |
482 | blocksize setting. | |
483 | .TP | |
d60e92d1 | 484 | .B zero_buffers |
cf145d90 | 485 | Initialize buffers with all zeros. Default: fill buffers with random data. |
d60e92d1 | 486 | .TP |
901bb994 JA |
487 | .B refill_buffers |
488 | If this option is given, fio will refill the IO buffers on every submit. The | |
489 | default is to only fill it at init time and reuse that data. Only makes sense | |
490 | if zero_buffers isn't specified, naturally. If data verification is enabled, | |
491 | refill_buffers is also automatically enabled. | |
492 | .TP | |
fd68418e JA |
493 | .BI scramble_buffers \fR=\fPbool |
494 | If \fBrefill_buffers\fR is too costly and the target is using data | |
495 | deduplication, then setting this option will slightly modify the IO buffer | |
496 | contents to defeat normal de-dupe attempts. This is not enough to defeat | |
497 | more clever block compression attempts, but it will stop naive dedupe | |
498 | of blocks. Default: true. | |
499 | .TP | |
c5751c62 JA |
500 | .BI buffer_compress_percentage \fR=\fPint |
501 | If this is set, then fio will attempt to provide IO buffer content (on WRITEs) | |
502 | that compress to the specified level. Fio does this by providing a mix of | |
d1af2894 JA |
503 | random data and a fixed pattern. The fixed pattern is either zeroes, or the |
504 | pattern specified by \fBbuffer_pattern\fR. If the pattern option is used, it | |
505 | might skew the compression ratio slightly. Note that this is per block size | |
506 | unit, for file/disk wide compression level that matches this setting. Note | |
507 | that this is per block size unit, for file/disk wide compression level that | |
508 | matches this setting, you'll also want to set refill_buffers. | |
c5751c62 JA |
509 | .TP |
510 | .BI buffer_compress_chunk \fR=\fPint | |
511 | See \fBbuffer_compress_percentage\fR. This setting allows fio to manage how | |
512 | big the ranges of random data and zeroed data is. Without this set, fio will | |
513 | provide \fBbuffer_compress_percentage\fR of blocksize random data, followed by | |
514 | the remaining zeroed. With this set to some chunk size smaller than the block | |
515 | size, fio can alternate random and zeroed data throughout the IO buffer. | |
516 | .TP | |
ce35b1ec | 517 | .BI buffer_pattern \fR=\fPstr |
cf145d90 CVB |
518 | If set, fio will fill the IO buffers with this pattern. If not set, the contents |
519 | of IO buffers is defined by the other options related to buffer contents. The | |
ce35b1ec | 520 | setting can be any pattern of bytes, and can be prefixed with 0x for hex |
02975b64 | 521 | values. It may also be a string, where the string must then be wrapped with |
2fa5a241 RP |
522 | "", e.g.: |
523 | .RS | |
524 | .RS | |
525 | \fBbuffer_pattern\fR="abcd" | |
526 | .RS | |
527 | or | |
528 | .RE | |
529 | \fBbuffer_pattern\fR=-12 | |
530 | .RS | |
531 | or | |
532 | .RE | |
533 | \fBbuffer_pattern\fR=0xdeadface | |
534 | .RE | |
535 | .LP | |
536 | Also you can combine everything together in any order: | |
537 | .LP | |
538 | .RS | |
539 | \fBbuffer_pattern\fR=0xdeadface"abcd"-12 | |
540 | .RE | |
541 | .RE | |
ce35b1ec | 542 | .TP |
5c94b008 JA |
543 | .BI dedupe_percentage \fR=\fPint |
544 | If set, fio will generate this percentage of identical buffers when writing. | |
545 | These buffers will be naturally dedupable. The contents of the buffers depend | |
546 | on what other buffer compression settings have been set. It's possible to have | |
547 | the individual buffers either fully compressible, or not at all. This option | |
548 | only controls the distribution of unique buffers. | |
549 | .TP | |
d60e92d1 AC |
550 | .BI nrfiles \fR=\fPint |
551 | Number of files to use for this job. Default: 1. | |
552 | .TP | |
553 | .BI openfiles \fR=\fPint | |
554 | Number of files to keep open at the same time. Default: \fBnrfiles\fR. | |
555 | .TP | |
556 | .BI file_service_type \fR=\fPstr | |
557 | Defines how files to service are selected. The following types are defined: | |
558 | .RS | |
559 | .RS | |
560 | .TP | |
561 | .B random | |
5c9323fb | 562 | Choose a file at random. |
d60e92d1 AC |
563 | .TP |
564 | .B roundrobin | |
cf145d90 | 565 | Round robin over opened files (default). |
5c9323fb | 566 | .TP |
6b7f6851 JA |
567 | .B sequential |
568 | Do each file in the set sequentially. | |
d60e92d1 AC |
569 | .RE |
570 | .P | |
cf145d90 | 571 | The number of I/Os to issue before switching to a new file can be specified by |
d60e92d1 AC |
572 | appending `:\fIint\fR' to the service type. |
573 | .RE | |
574 | .TP | |
575 | .BI ioengine \fR=\fPstr | |
576 | Defines how the job issues I/O. The following types are defined: | |
577 | .RS | |
578 | .RS | |
579 | .TP | |
580 | .B sync | |
ccc2b328 | 581 | Basic \fBread\fR\|(2) or \fBwrite\fR\|(2) I/O. \fBfseek\fR\|(2) is used to |
d60e92d1 AC |
582 | position the I/O location. |
583 | .TP | |
a31041ea | 584 | .B psync |
ccc2b328 | 585 | Basic \fBpread\fR\|(2) or \fBpwrite\fR\|(2) I/O. |
a31041ea | 586 | .TP |
9183788d | 587 | .B vsync |
ccc2b328 | 588 | Basic \fBreadv\fR\|(2) or \fBwritev\fR\|(2) I/O. Will emulate queuing by |
cecbfd47 | 589 | coalescing adjacent IOs into a single submission. |
9183788d | 590 | .TP |
a46c5e01 | 591 | .B pvsync |
ccc2b328 | 592 | Basic \fBpreadv\fR\|(2) or \fBpwritev\fR\|(2) I/O. |
a46c5e01 | 593 | .TP |
2cafffbe JA |
594 | .B pvsync2 |
595 | Basic \fBpreadv2\fR\|(2) or \fBpwritev2\fR\|(2) I/O. | |
596 | .TP | |
d60e92d1 | 597 | .B libaio |
de890a1e | 598 | Linux native asynchronous I/O. This ioengine defines engine specific options. |
d60e92d1 AC |
599 | .TP |
600 | .B posixaio | |
ccc2b328 | 601 | POSIX asynchronous I/O using \fBaio_read\fR\|(3) and \fBaio_write\fR\|(3). |
03e20d68 BC |
602 | .TP |
603 | .B solarisaio | |
604 | Solaris native asynchronous I/O. | |
605 | .TP | |
606 | .B windowsaio | |
607 | Windows native asynchronous I/O. | |
d60e92d1 AC |
608 | .TP |
609 | .B mmap | |
ccc2b328 SW |
610 | File is memory mapped with \fBmmap\fR\|(2) and data copied using |
611 | \fBmemcpy\fR\|(3). | |
d60e92d1 AC |
612 | .TP |
613 | .B splice | |
ccc2b328 | 614 | \fBsplice\fR\|(2) is used to transfer the data and \fBvmsplice\fR\|(2) to |
d1429b5c | 615 | transfer data from user-space to the kernel. |
d60e92d1 AC |
616 | .TP |
617 | .B syslet-rw | |
618 | Use the syslet system calls to make regular read/write asynchronous. | |
619 | .TP | |
620 | .B sg | |
621 | SCSI generic sg v3 I/O. May be either synchronous using the SG_IO ioctl, or if | |
ccc2b328 SW |
622 | the target is an sg character device, we use \fBread\fR\|(2) and |
623 | \fBwrite\fR\|(2) for asynchronous I/O. | |
d60e92d1 AC |
624 | .TP |
625 | .B null | |
626 | Doesn't transfer any data, just pretends to. Mainly used to exercise \fBfio\fR | |
627 | itself and for debugging and testing purposes. | |
628 | .TP | |
629 | .B net | |
de890a1e SL |
630 | Transfer over the network. The protocol to be used can be defined with the |
631 | \fBprotocol\fR parameter. Depending on the protocol, \fBfilename\fR, | |
632 | \fBhostname\fR, \fBport\fR, or \fBlisten\fR must be specified. | |
633 | This ioengine defines engine specific options. | |
d60e92d1 AC |
634 | .TP |
635 | .B netsplice | |
ccc2b328 | 636 | Like \fBnet\fR, but uses \fBsplice\fR\|(2) and \fBvmsplice\fR\|(2) to map data |
de890a1e | 637 | and send/receive. This ioengine defines engine specific options. |
d60e92d1 | 638 | .TP |
53aec0a4 | 639 | .B cpuio |
d60e92d1 AC |
640 | Doesn't transfer any data, but burns CPU cycles according to \fBcpuload\fR and |
641 | \fBcpucycles\fR parameters. | |
642 | .TP | |
643 | .B guasi | |
644 | The GUASI I/O engine is the Generic Userspace Asynchronous Syscall Interface | |
cecbfd47 | 645 | approach to asynchronous I/O. |
d1429b5c AC |
646 | .br |
647 | See <http://www.xmailserver.org/guasi\-lib.html>. | |
d60e92d1 | 648 | .TP |
21b8aee8 | 649 | .B rdma |
85286c5c BVA |
650 | The RDMA I/O engine supports both RDMA memory semantics (RDMA_WRITE/RDMA_READ) |
651 | and channel semantics (Send/Recv) for the InfiniBand, RoCE and iWARP protocols. | |
21b8aee8 | 652 | .TP |
d60e92d1 AC |
653 | .B external |
654 | Loads an external I/O engine object file. Append the engine filename as | |
655 | `:\fIenginepath\fR'. | |
d54fce84 DM |
656 | .TP |
657 | .B falloc | |
cecbfd47 | 658 | IO engine that does regular linux native fallocate call to simulate data |
d54fce84 DM |
659 | transfer as fio ioengine |
660 | .br | |
661 | DDIR_READ does fallocate(,mode = FALLOC_FL_KEEP_SIZE,) | |
662 | .br | |
0981fd71 | 663 | DIR_WRITE does fallocate(,mode = 0) |
d54fce84 DM |
664 | .br |
665 | DDIR_TRIM does fallocate(,mode = FALLOC_FL_KEEP_SIZE|FALLOC_FL_PUNCH_HOLE) | |
666 | .TP | |
667 | .B e4defrag | |
668 | IO engine that does regular EXT4_IOC_MOVE_EXT ioctls to simulate defragment activity | |
669 | request to DDIR_WRITE event | |
0d978694 DAG |
670 | .TP |
671 | .B rbd | |
ff6bb260 SL |
672 | IO engine supporting direct access to Ceph Rados Block Devices (RBD) via librbd |
673 | without the need to use the kernel rbd driver. This ioengine defines engine specific | |
0d978694 | 674 | options. |
a7c386f4 | 675 | .TP |
676 | .B gfapi | |
cc47f094 | 677 | Using Glusterfs libgfapi sync interface to direct access to Glusterfs volumes without |
678 | having to go through FUSE. This ioengine defines engine specific | |
679 | options. | |
680 | .TP | |
681 | .B gfapi_async | |
682 | Using Glusterfs libgfapi async interface to direct access to Glusterfs volumes without | |
a7c386f4 | 683 | having to go through FUSE. This ioengine defines engine specific |
684 | options. | |
1b10477b | 685 | .TP |
b74e419e MM |
686 | .B libhdfs |
687 | Read and write through Hadoop (HDFS). The \fBfilename\fR option is used to | |
688 | specify host,port of the hdfs name-node to connect. This engine interprets | |
689 | offsets a little differently. In HDFS, files once created cannot be modified. | |
690 | So random writes are not possible. To imitate this, libhdfs engine expects | |
691 | bunch of small files to be created over HDFS, and engine will randomly pick a | |
692 | file out of those files based on the offset generated by fio backend. (see the | |
693 | example job file to create such files, use rw=write option). Please note, you | |
694 | might want to set necessary environment variables to work with hdfs/libhdfs | |
695 | properly. | |
65fa28ca DE |
696 | .TP |
697 | .B mtd | |
698 | Read, write and erase an MTD character device (e.g., /dev/mtd0). Discards are | |
699 | treated as erases. Depending on the underlying device type, the I/O may have | |
700 | to go in a certain pattern, e.g., on NAND, writing sequentially to erase blocks | |
701 | and discarding before overwriting. The writetrim mode works well for this | |
702 | constraint. | |
d60e92d1 | 703 | .RE |
595e1734 | 704 | .P |
d60e92d1 AC |
705 | .RE |
706 | .TP | |
707 | .BI iodepth \fR=\fPint | |
8489dae4 SK |
708 | Number of I/O units to keep in flight against the file. Note that increasing |
709 | iodepth beyond 1 will not affect synchronous ioengines (except for small | |
cf145d90 | 710 | degress when verify_async is in use). Even async engines may impose OS |
ee72ca09 JA |
711 | restrictions causing the desired depth not to be achieved. This may happen on |
712 | Linux when using libaio and not setting \fBdirect\fR=1, since buffered IO is | |
713 | not async on that OS. Keep an eye on the IO depth distribution in the | |
714 | fio output to verify that the achieved depth is as expected. Default: 1. | |
d60e92d1 | 715 | .TP |
e63a0b2f RP |
716 | .BI iodepth_batch \fR=\fPint "\fR,\fP iodepth_batch_submit" \fR=\fPint |
717 | This defines how many pieces of IO to submit at once. It defaults to 1 | |
718 | which means that we submit each IO as soon as it is available, but can | |
719 | be raised to submit bigger batches of IO at the time. If it is set to 0 | |
720 | the \fBiodepth\fR value will be used. | |
d60e92d1 | 721 | .TP |
82407585 | 722 | .BI iodepth_batch_complete_min \fR=\fPint "\fR,\fP iodepth_batch_complete" \fR=\fPint |
3ce9dcaf JA |
723 | This defines how many pieces of IO to retrieve at once. It defaults to 1 which |
724 | means that we'll ask for a minimum of 1 IO in the retrieval process from the | |
725 | kernel. The IO retrieval will go on until we hit the limit set by | |
726 | \fBiodepth_low\fR. If this variable is set to 0, then fio will always check for | |
727 | completed events before queuing more IO. This helps reduce IO latency, at the | |
728 | cost of more retrieval system calls. | |
729 | .TP | |
82407585 RP |
730 | .BI iodepth_batch_complete_max \fR=\fPint |
731 | This defines maximum pieces of IO to | |
732 | retrieve at once. This variable should be used along with | |
733 | \fBiodepth_batch_complete_min\fR=int variable, specifying the range | |
734 | of min and max amount of IO which should be retrieved. By default | |
735 | it is equal to \fBiodepth_batch_complete_min\fR value. | |
736 | ||
737 | Example #1: | |
738 | .RS | |
739 | .RS | |
740 | \fBiodepth_batch_complete_min\fR=1 | |
741 | .LP | |
742 | \fBiodepth_batch_complete_max\fR=<iodepth> | |
743 | .RE | |
744 | ||
745 | which means that we will retrieve at leat 1 IO and up to the | |
746 | whole submitted queue depth. If none of IO has been completed | |
747 | yet, we will wait. | |
748 | ||
749 | Example #2: | |
750 | .RS | |
751 | \fBiodepth_batch_complete_min\fR=0 | |
752 | .LP | |
753 | \fBiodepth_batch_complete_max\fR=<iodepth> | |
754 | .RE | |
755 | ||
756 | which means that we can retrieve up to the whole submitted | |
757 | queue depth, but if none of IO has been completed yet, we will | |
758 | NOT wait and immediately exit the system call. In this example | |
759 | we simply do polling. | |
760 | .RE | |
761 | .TP | |
d60e92d1 AC |
762 | .BI iodepth_low \fR=\fPint |
763 | Low watermark indicating when to start filling the queue again. Default: | |
ff6bb260 | 764 | \fBiodepth\fR. |
d60e92d1 | 765 | .TP |
1ad01bd1 JA |
766 | .BI io_submit_mode \fR=\fPstr |
767 | This option controls how fio submits the IO to the IO engine. The default is | |
768 | \fBinline\fR, which means that the fio job threads submit and reap IO directly. | |
769 | If set to \fBoffload\fR, the job threads will offload IO submission to a | |
770 | dedicated pool of IO threads. This requires some coordination and thus has a | |
771 | bit of extra overhead, especially for lower queue depth IO where it can | |
772 | increase latencies. The benefit is that fio can manage submission rates | |
773 | independently of the device completion rates. This avoids skewed latency | |
774 | reporting if IO gets back up on the device side (the coordinated omission | |
775 | problem). | |
776 | .TP | |
d60e92d1 AC |
777 | .BI direct \fR=\fPbool |
778 | If true, use non-buffered I/O (usually O_DIRECT). Default: false. | |
779 | .TP | |
d01612f3 CM |
780 | .BI atomic \fR=\fPbool |
781 | If value is true, attempt to use atomic direct IO. Atomic writes are guaranteed | |
782 | to be stable once acknowledged by the operating system. Only Linux supports | |
783 | O_ATOMIC right now. | |
784 | .TP | |
d60e92d1 AC |
785 | .BI buffered \fR=\fPbool |
786 | If true, use buffered I/O. This is the opposite of the \fBdirect\fR parameter. | |
787 | Default: true. | |
788 | .TP | |
f7fa2653 | 789 | .BI offset \fR=\fPint |
d60e92d1 AC |
790 | Offset in the file to start I/O. Data before the offset will not be touched. |
791 | .TP | |
591e9e06 JA |
792 | .BI offset_increment \fR=\fPint |
793 | If this is provided, then the real offset becomes the | |
69bdd6ba JH |
794 | offset + offset_increment * thread_number, where the thread number is a |
795 | counter that starts at 0 and is incremented for each sub-job (i.e. when | |
796 | numjobs option is specified). This option is useful if there are several jobs | |
797 | which are intended to operate on a file in parallel disjoint segments, with | |
798 | even spacing between the starting points. | |
591e9e06 | 799 | .TP |
ddf24e42 JA |
800 | .BI number_ios \fR=\fPint |
801 | Fio will normally perform IOs until it has exhausted the size of the region | |
802 | set by \fBsize\fR, or if it exhaust the allocated time (or hits an error | |
803 | condition). With this setting, the range/size can be set independently of | |
804 | the number of IOs to perform. When fio reaches this number, it will exit | |
be3fec7d JA |
805 | normally and report status. Note that this does not extend the amount |
806 | of IO that will be done, it will only stop fio if this condition is met | |
807 | before other end-of-job criteria. | |
ddf24e42 | 808 | .TP |
d60e92d1 | 809 | .BI fsync \fR=\fPint |
d1429b5c AC |
810 | How many I/Os to perform before issuing an \fBfsync\fR\|(2) of dirty data. If |
811 | 0, don't sync. Default: 0. | |
d60e92d1 | 812 | .TP |
5f9099ea JA |
813 | .BI fdatasync \fR=\fPint |
814 | Like \fBfsync\fR, but uses \fBfdatasync\fR\|(2) instead to only sync the | |
815 | data parts of the file. Default: 0. | |
816 | .TP | |
fa769d44 SW |
817 | .BI write_barrier \fR=\fPint |
818 | Make every Nth write a barrier write. | |
819 | .TP | |
e76b1da4 | 820 | .BI sync_file_range \fR=\fPstr:int |
ccc2b328 SW |
821 | Use \fBsync_file_range\fR\|(2) for every \fRval\fP number of write operations. Fio will |
822 | track range of writes that have happened since the last \fBsync_file_range\fR\|(2) call. | |
e76b1da4 JA |
823 | \fRstr\fP can currently be one or more of: |
824 | .RS | |
825 | .TP | |
826 | .B wait_before | |
827 | SYNC_FILE_RANGE_WAIT_BEFORE | |
828 | .TP | |
829 | .B write | |
830 | SYNC_FILE_RANGE_WRITE | |
831 | .TP | |
832 | .B wait_after | |
833 | SYNC_FILE_RANGE_WRITE | |
834 | .TP | |
835 | .RE | |
836 | .P | |
837 | So if you do sync_file_range=wait_before,write:8, fio would use | |
838 | \fBSYNC_FILE_RANGE_WAIT_BEFORE | SYNC_FILE_RANGE_WRITE\fP for every 8 writes. | |
ccc2b328 | 839 | Also see the \fBsync_file_range\fR\|(2) man page. This option is Linux specific. |
e76b1da4 | 840 | .TP |
d60e92d1 | 841 | .BI overwrite \fR=\fPbool |
d1429b5c | 842 | If writing, setup the file first and do overwrites. Default: false. |
d60e92d1 AC |
843 | .TP |
844 | .BI end_fsync \fR=\fPbool | |
dbd11ead | 845 | Sync file contents when a write stage has completed. Default: false. |
d60e92d1 AC |
846 | .TP |
847 | .BI fsync_on_close \fR=\fPbool | |
848 | If true, sync file contents on close. This differs from \fBend_fsync\fR in that | |
d1429b5c | 849 | it will happen on every close, not just at the end of the job. Default: false. |
d60e92d1 | 850 | .TP |
d60e92d1 AC |
851 | .BI rwmixread \fR=\fPint |
852 | Percentage of a mixed workload that should be reads. Default: 50. | |
853 | .TP | |
854 | .BI rwmixwrite \fR=\fPint | |
d1429b5c | 855 | Percentage of a mixed workload that should be writes. If \fBrwmixread\fR and |
c35dd7a6 JA |
856 | \fBrwmixwrite\fR are given and do not sum to 100%, the latter of the two |
857 | overrides the first. This may interfere with a given rate setting, if fio is | |
858 | asked to limit reads or writes to a certain rate. If that is the case, then | |
859 | the distribution may be skewed. Default: 50. | |
d60e92d1 | 860 | .TP |
92d42d69 JA |
861 | .BI random_distribution \fR=\fPstr:float |
862 | By default, fio will use a completely uniform random distribution when asked | |
863 | to perform random IO. Sometimes it is useful to skew the distribution in | |
864 | specific ways, ensuring that some parts of the data is more hot than others. | |
865 | Fio includes the following distribution models: | |
866 | .RS | |
867 | .TP | |
868 | .B random | |
869 | Uniform random distribution | |
870 | .TP | |
871 | .B zipf | |
872 | Zipf distribution | |
873 | .TP | |
874 | .B pareto | |
875 | Pareto distribution | |
876 | .TP | |
8116fd24 JA |
877 | .B gauss |
878 | Normal (gaussian) distribution | |
879 | .TP | |
e0a04ac1 JA |
880 | .B zoned |
881 | Zoned random distribution | |
882 | .TP | |
92d42d69 | 883 | .RE |
8116fd24 JA |
884 | When using a \fBzipf\fR or \fBpareto\fR distribution, an input value is also |
885 | needed to define the access pattern. For \fBzipf\fR, this is the zipf theta. | |
886 | For \fBpareto\fR, it's the pareto power. Fio includes a test program, genzipf, | |
887 | that can be used visualize what the given input values will yield in terms of | |
888 | hit rates. If you wanted to use \fBzipf\fR with a theta of 1.2, you would use | |
92d42d69 | 889 | random_distribution=zipf:1.2 as the option. If a non-uniform model is used, |
8116fd24 JA |
890 | fio will disable use of the random map. For the \fBgauss\fR distribution, a |
891 | normal deviation is supplied as a value between 0 and 100. | |
e0a04ac1 JA |
892 | .P |
893 | .RS | |
894 | For a \fBzoned\fR distribution, fio supports specifying percentages of IO | |
895 | access that should fall within what range of the file or device. For example, | |
896 | given a criteria of: | |
897 | .P | |
898 | .RS | |
899 | 60% of accesses should be to the first 10% | |
900 | .RE | |
901 | .RS | |
902 | 30% of accesses should be to the next 20% | |
903 | .RE | |
904 | .RS | |
905 | 8% of accesses should be to to the next 30% | |
906 | .RE | |
907 | .RS | |
908 | 2% of accesses should be to the next 40% | |
909 | .RE | |
910 | .P | |
911 | we can define that through zoning of the random accesses. For the above | |
912 | example, the user would do: | |
913 | .P | |
914 | .RS | |
915 | .B random_distribution=zoned:60/10:30/20:8/30:2/40 | |
916 | .RE | |
917 | .P | |
918 | similarly to how \fBbssplit\fR works for setting ranges and percentages of block | |
919 | sizes. Like \fBbssplit\fR, it's possible to specify separate zones for reads, | |
920 | writes, and trims. If just one set is given, it'll apply to all of them. | |
921 | .RE | |
92d42d69 | 922 | .TP |
211c9b89 JA |
923 | .BI percentage_random \fR=\fPint |
924 | For a random workload, set how big a percentage should be random. This defaults | |
925 | to 100%, in which case the workload is fully random. It can be set from | |
926 | anywhere from 0 to 100. Setting it to 0 would make the workload fully | |
d9472271 JA |
927 | sequential. It is possible to set different values for reads, writes, and |
928 | trim. To do so, simply use a comma separated list. See \fBblocksize\fR. | |
211c9b89 | 929 | .TP |
d60e92d1 AC |
930 | .B norandommap |
931 | Normally \fBfio\fR will cover every block of the file when doing random I/O. If | |
932 | this parameter is given, a new offset will be chosen without looking at past | |
933 | I/O history. This parameter is mutually exclusive with \fBverify\fR. | |
934 | .TP | |
744492c9 | 935 | .BI softrandommap \fR=\fPbool |
3ce9dcaf JA |
936 | See \fBnorandommap\fR. If fio runs with the random block map enabled and it |
937 | fails to allocate the map, if this option is set it will continue without a | |
938 | random block map. As coverage will not be as complete as with random maps, this | |
939 | option is disabled by default. | |
940 | .TP | |
e8b1961d JA |
941 | .BI random_generator \fR=\fPstr |
942 | Fio supports the following engines for generating IO offsets for random IO: | |
943 | .RS | |
944 | .TP | |
945 | .B tausworthe | |
946 | Strong 2^88 cycle random number generator | |
947 | .TP | |
948 | .B lfsr | |
949 | Linear feedback shift register generator | |
950 | .TP | |
c3546b53 JA |
951 | .B tausworthe64 |
952 | Strong 64-bit 2^258 cycle random number generator | |
953 | .TP | |
e8b1961d JA |
954 | .RE |
955 | .P | |
956 | Tausworthe is a strong random number generator, but it requires tracking on the | |
957 | side if we want to ensure that blocks are only read or written once. LFSR | |
958 | guarantees that we never generate the same offset twice, and it's also less | |
959 | computationally expensive. It's not a true random generator, however, though | |
960 | for IO purposes it's typically good enough. LFSR only works with single block | |
961 | sizes, not with workloads that use multiple block sizes. If used with such a | |
3bb85e84 JA |
962 | workload, fio may read or write some blocks multiple times. The default |
963 | value is tausworthe, unless the required space exceeds 2^32 blocks. If it does, | |
964 | then tausworthe64 is selected automatically. | |
e8b1961d | 965 | .TP |
d60e92d1 | 966 | .BI nice \fR=\fPint |
ccc2b328 | 967 | Run job with given nice value. See \fBnice\fR\|(2). |
d60e92d1 AC |
968 | .TP |
969 | .BI prio \fR=\fPint | |
970 | Set I/O priority value of this job between 0 (highest) and 7 (lowest). See | |
ccc2b328 | 971 | \fBionice\fR\|(1). |
d60e92d1 AC |
972 | .TP |
973 | .BI prioclass \fR=\fPint | |
ccc2b328 | 974 | Set I/O priority class. See \fBionice\fR\|(1). |
d60e92d1 AC |
975 | .TP |
976 | .BI thinktime \fR=\fPint | |
977 | Stall job for given number of microseconds between issuing I/Os. | |
978 | .TP | |
979 | .BI thinktime_spin \fR=\fPint | |
980 | Pretend to spend CPU time for given number of microseconds, sleeping the rest | |
981 | of the time specified by \fBthinktime\fR. Only valid if \fBthinktime\fR is set. | |
982 | .TP | |
983 | .BI thinktime_blocks \fR=\fPint | |
4d01ece6 JA |
984 | Only valid if thinktime is set - control how many blocks to issue, before |
985 | waiting \fBthinktime\fR microseconds. If not set, defaults to 1 which will | |
986 | make fio wait \fBthinktime\fR microseconds after every block. This | |
987 | effectively makes any queue depth setting redundant, since no more than 1 IO | |
988 | will be queued before we have to complete it and do our thinktime. In other | |
989 | words, this setting effectively caps the queue depth if the latter is larger. | |
d60e92d1 AC |
990 | Default: 1. |
991 | .TP | |
992 | .BI rate \fR=\fPint | |
c35dd7a6 JA |
993 | Cap bandwidth used by this job. The number is in bytes/sec, the normal postfix |
994 | rules apply. You can use \fBrate\fR=500k to limit reads and writes to 500k each, | |
995 | or you can specify read and writes separately. Using \fBrate\fR=1m,500k would | |
996 | limit reads to 1MB/sec and writes to 500KB/sec. Capping only reads or writes | |
997 | can be done with \fBrate\fR=,500k or \fBrate\fR=500k,. The former will only | |
998 | limit writes (to 500KB/sec), the latter will only limit reads. | |
d60e92d1 | 999 | .TP |
6d428bcd | 1000 | .BI rate_min \fR=\fPint |
d60e92d1 | 1001 | Tell \fBfio\fR to do whatever it can to maintain at least the given bandwidth. |
c35dd7a6 JA |
1002 | Failing to meet this requirement will cause the job to exit. The same format |
1003 | as \fBrate\fR is used for read vs write separation. | |
d60e92d1 AC |
1004 | .TP |
1005 | .BI rate_iops \fR=\fPint | |
c35dd7a6 JA |
1006 | Cap the bandwidth to this number of IOPS. Basically the same as rate, just |
1007 | specified independently of bandwidth. The same format as \fBrate\fR is used for | |
de8f6de9 | 1008 | read vs write separation. If \fBblocksize\fR is a range, the smallest block |
c35dd7a6 | 1009 | size is used as the metric. |
d60e92d1 AC |
1010 | .TP |
1011 | .BI rate_iops_min \fR=\fPint | |
c35dd7a6 | 1012 | If this rate of I/O is not met, the job will exit. The same format as \fBrate\fR |
de8f6de9 | 1013 | is used for read vs write separation. |
d60e92d1 | 1014 | .TP |
6de65959 JA |
1015 | .BI rate_process \fR=\fPstr |
1016 | This option controls how fio manages rated IO submissions. The default is | |
1017 | \fBlinear\fR, which submits IO in a linear fashion with fixed delays between | |
1018 | IOs that gets adjusted based on IO completion rates. If this is set to | |
1019 | \fBpoisson\fR, fio will submit IO based on a more real world random request | |
1020 | flow, known as the Poisson process | |
5d02b083 JA |
1021 | (https://en.wikipedia.org/wiki/Poisson_process). The lambda will be |
1022 | 10^6 / IOPS for the given workload. | |
ff6bb260 | 1023 | .TP |
6d428bcd JA |
1024 | .BI rate_cycle \fR=\fPint |
1025 | Average bandwidth for \fBrate\fR and \fBrate_min\fR over this number of | |
d60e92d1 AC |
1026 | milliseconds. Default: 1000ms. |
1027 | .TP | |
3e260a46 JA |
1028 | .BI latency_target \fR=\fPint |
1029 | If set, fio will attempt to find the max performance point that the given | |
1030 | workload will run at while maintaining a latency below this target. The | |
1031 | values is given in microseconds. See \fBlatency_window\fR and | |
1032 | \fBlatency_percentile\fR. | |
1033 | .TP | |
1034 | .BI latency_window \fR=\fPint | |
1035 | Used with \fBlatency_target\fR to specify the sample window that the job | |
1036 | is run at varying queue depths to test the performance. The value is given | |
1037 | in microseconds. | |
1038 | .TP | |
1039 | .BI latency_percentile \fR=\fPfloat | |
1040 | The percentage of IOs that must fall within the criteria specified by | |
1041 | \fBlatency_target\fR and \fBlatency_window\fR. If not set, this defaults | |
1042 | to 100.0, meaning that all IOs must be equal or below to the value set | |
1043 | by \fBlatency_target\fR. | |
1044 | .TP | |
15501535 JA |
1045 | .BI max_latency \fR=\fPint |
1046 | If set, fio will exit the job if it exceeds this maximum latency. It will exit | |
1047 | with an ETIME error. | |
1048 | .TP | |
d60e92d1 AC |
1049 | .BI cpumask \fR=\fPint |
1050 | Set CPU affinity for this job. \fIint\fR is a bitmask of allowed CPUs the job | |
1051 | may run on. See \fBsched_setaffinity\fR\|(2). | |
1052 | .TP | |
1053 | .BI cpus_allowed \fR=\fPstr | |
1054 | Same as \fBcpumask\fR, but allows a comma-delimited list of CPU numbers. | |
1055 | .TP | |
c2acfbac JA |
1056 | .BI cpus_allowed_policy \fR=\fPstr |
1057 | Set the policy of how fio distributes the CPUs specified by \fBcpus_allowed\fR | |
1058 | or \fBcpumask\fR. Two policies are supported: | |
1059 | .RS | |
1060 | .RS | |
1061 | .TP | |
1062 | .B shared | |
1063 | All jobs will share the CPU set specified. | |
1064 | .TP | |
1065 | .B split | |
1066 | Each job will get a unique CPU from the CPU set. | |
1067 | .RE | |
1068 | .P | |
1069 | \fBshared\fR is the default behaviour, if the option isn't specified. If | |
ada083cd JA |
1070 | \fBsplit\fR is specified, then fio will assign one cpu per job. If not enough |
1071 | CPUs are given for the jobs listed, then fio will roundrobin the CPUs in | |
1072 | the set. | |
c2acfbac JA |
1073 | .RE |
1074 | .P | |
1075 | .TP | |
d0b937ed | 1076 | .BI numa_cpu_nodes \fR=\fPstr |
cecbfd47 | 1077 | Set this job running on specified NUMA nodes' CPUs. The arguments allow |
d0b937ed YR |
1078 | comma delimited list of cpu numbers, A-B ranges, or 'all'. |
1079 | .TP | |
1080 | .BI numa_mem_policy \fR=\fPstr | |
1081 | Set this job's memory policy and corresponding NUMA nodes. Format of | |
cecbfd47 | 1082 | the arguments: |
d0b937ed YR |
1083 | .RS |
1084 | .TP | |
1085 | .B <mode>[:<nodelist>] | |
1086 | .TP | |
1087 | .B mode | |
1088 | is one of the following memory policy: | |
1089 | .TP | |
1090 | .B default, prefer, bind, interleave, local | |
1091 | .TP | |
1092 | .RE | |
1093 | For \fBdefault\fR and \fBlocal\fR memory policy, no \fBnodelist\fR is | |
1094 | needed to be specified. For \fBprefer\fR, only one node is | |
1095 | allowed. For \fBbind\fR and \fBinterleave\fR, \fBnodelist\fR allows | |
1096 | comma delimited list of numbers, A-B ranges, or 'all'. | |
1097 | .TP | |
23ed19b0 CE |
1098 | .BI startdelay \fR=\fPirange |
1099 | Delay start of job for the specified number of seconds. Supports all time | |
1100 | suffixes to allow specification of hours, minutes, seconds and | |
bd66aa2c | 1101 | milliseconds - seconds are the default if a unit is omitted. |
23ed19b0 CE |
1102 | Can be given as a range which causes each thread to choose randomly out of the |
1103 | range. | |
d60e92d1 AC |
1104 | .TP |
1105 | .BI runtime \fR=\fPint | |
1106 | Terminate processing after the specified number of seconds. | |
1107 | .TP | |
1108 | .B time_based | |
1109 | If given, run for the specified \fBruntime\fR duration even if the files are | |
1110 | completely read or written. The same workload will be repeated as many times | |
1111 | as \fBruntime\fR allows. | |
1112 | .TP | |
901bb994 JA |
1113 | .BI ramp_time \fR=\fPint |
1114 | If set, fio will run the specified workload for this amount of time before | |
1115 | logging any performance numbers. Useful for letting performance settle before | |
1116 | logging results, thus minimizing the runtime required for stable results. Note | |
c35dd7a6 JA |
1117 | that the \fBramp_time\fR is considered lead in time for a job, thus it will |
1118 | increase the total runtime if a special timeout or runtime is specified. | |
901bb994 | 1119 | .TP |
d60e92d1 AC |
1120 | .BI invalidate \fR=\fPbool |
1121 | Invalidate buffer-cache for the file prior to starting I/O. Default: true. | |
1122 | .TP | |
1123 | .BI sync \fR=\fPbool | |
1124 | Use synchronous I/O for buffered writes. For the majority of I/O engines, | |
d1429b5c | 1125 | this means using O_SYNC. Default: false. |
d60e92d1 AC |
1126 | .TP |
1127 | .BI iomem \fR=\fPstr "\fR,\fP mem" \fR=\fPstr | |
1128 | Allocation method for I/O unit buffer. Allowed values are: | |
1129 | .RS | |
1130 | .RS | |
1131 | .TP | |
1132 | .B malloc | |
ccc2b328 | 1133 | Allocate memory with \fBmalloc\fR\|(3). |
d60e92d1 AC |
1134 | .TP |
1135 | .B shm | |
ccc2b328 | 1136 | Use shared memory buffers allocated through \fBshmget\fR\|(2). |
d60e92d1 AC |
1137 | .TP |
1138 | .B shmhuge | |
1139 | Same as \fBshm\fR, but use huge pages as backing. | |
1140 | .TP | |
1141 | .B mmap | |
ccc2b328 | 1142 | Use \fBmmap\fR\|(2) for allocation. Uses anonymous memory unless a filename |
d60e92d1 AC |
1143 | is given after the option in the format `:\fIfile\fR'. |
1144 | .TP | |
1145 | .B mmaphuge | |
1146 | Same as \fBmmap\fR, but use huge files as backing. | |
09c782bb JA |
1147 | .TP |
1148 | .B mmapshared | |
1149 | Same as \fBmmap\fR, but use a MMAP_SHARED mapping. | |
d60e92d1 AC |
1150 | .RE |
1151 | .P | |
1152 | The amount of memory allocated is the maximum allowed \fBblocksize\fR for the | |
1153 | job multiplied by \fBiodepth\fR. For \fBshmhuge\fR or \fBmmaphuge\fR to work, | |
1154 | the system must have free huge pages allocated. \fBmmaphuge\fR also needs to | |
2e266ba6 JA |
1155 | have hugetlbfs mounted, and \fIfile\fR must point there. At least on Linux, |
1156 | huge pages must be manually allocated. See \fB/proc/sys/vm/nr_hugehages\fR | |
1157 | and the documentation for that. Normally you just need to echo an appropriate | |
1158 | number, eg echoing 8 will ensure that the OS has 8 huge pages ready for | |
1159 | use. | |
d60e92d1 AC |
1160 | .RE |
1161 | .TP | |
d392365e | 1162 | .BI iomem_align \fR=\fPint "\fR,\fP mem_align" \fR=\fPint |
cecbfd47 | 1163 | This indicates the memory alignment of the IO memory buffers. Note that the |
d529ee19 JA |
1164 | given alignment is applied to the first IO unit buffer, if using \fBiodepth\fR |
1165 | the alignment of the following buffers are given by the \fBbs\fR used. In | |
1166 | other words, if using a \fBbs\fR that is a multiple of the page sized in the | |
1167 | system, all buffers will be aligned to this value. If using a \fBbs\fR that | |
1168 | is not page aligned, the alignment of subsequent IO memory buffers is the | |
1169 | sum of the \fBiomem_align\fR and \fBbs\fR used. | |
1170 | .TP | |
f7fa2653 | 1171 | .BI hugepage\-size \fR=\fPint |
d60e92d1 | 1172 | Defines the size of a huge page. Must be at least equal to the system setting. |
b22989b9 | 1173 | Should be a multiple of 1MB. Default: 4MB. |
d60e92d1 AC |
1174 | .TP |
1175 | .B exitall | |
1176 | Terminate all jobs when one finishes. Default: wait for each job to finish. | |
1177 | .TP | |
f9cafb12 JA |
1178 | .B exitall_on_error \fR=\fPbool |
1179 | Terminate all jobs if one job finishes in error. Default: wait for each job | |
1180 | to finish. | |
1181 | .TP | |
d60e92d1 AC |
1182 | .BI bwavgtime \fR=\fPint |
1183 | Average bandwidth calculations over the given time in milliseconds. Default: | |
1184 | 500ms. | |
1185 | .TP | |
c8eeb9df JA |
1186 | .BI iopsavgtime \fR=\fPint |
1187 | Average IOPS calculations over the given time in milliseconds. Default: | |
1188 | 500ms. | |
1189 | .TP | |
d60e92d1 | 1190 | .BI create_serialize \fR=\fPbool |
d1429b5c | 1191 | If true, serialize file creation for the jobs. Default: true. |
d60e92d1 AC |
1192 | .TP |
1193 | .BI create_fsync \fR=\fPbool | |
ccc2b328 | 1194 | \fBfsync\fR\|(2) data file after creation. Default: true. |
d60e92d1 | 1195 | .TP |
6b7f6851 JA |
1196 | .BI create_on_open \fR=\fPbool |
1197 | If true, the files are not created until they are opened for IO by the job. | |
1198 | .TP | |
25460cf6 JA |
1199 | .BI create_only \fR=\fPbool |
1200 | If true, fio will only run the setup phase of the job. If files need to be | |
1201 | laid out or updated on disk, only that will be done. The actual job contents | |
1202 | are not executed. | |
1203 | .TP | |
2378826d JA |
1204 | .BI allow_file_create \fR=\fPbool |
1205 | If true, fio is permitted to create files as part of its workload. This is | |
1206 | the default behavior. If this option is false, then fio will error out if the | |
1207 | files it needs to use don't already exist. Default: true. | |
1208 | .TP | |
e81ecca3 JA |
1209 | .BI allow_mounted_write \fR=\fPbool |
1210 | If this isn't set, fio will abort jobs that are destructive (eg that write) | |
1211 | to what appears to be a mounted device or partition. This should help catch | |
1212 | creating inadvertently destructive tests, not realizing that the test will | |
1213 | destroy data on the mounted file system. Default: false. | |
1214 | .TP | |
e9f48479 JA |
1215 | .BI pre_read \fR=\fPbool |
1216 | If this is given, files will be pre-read into memory before starting the given | |
1217 | IO operation. This will also clear the \fR \fBinvalidate\fR flag, since it is | |
9c0d2241 JA |
1218 | pointless to pre-read and then drop the cache. This will only work for IO |
1219 | engines that are seekable, since they allow you to read the same data | |
1220 | multiple times. Thus it will not work on eg network or splice IO. | |
e9f48479 | 1221 | .TP |
d60e92d1 AC |
1222 | .BI unlink \fR=\fPbool |
1223 | Unlink job files when done. Default: false. | |
1224 | .TP | |
1225 | .BI loops \fR=\fPint | |
1226 | Specifies the number of iterations (runs of the same workload) of this job. | |
1227 | Default: 1. | |
1228 | .TP | |
5e4c7118 JA |
1229 | .BI verify_only \fR=\fPbool |
1230 | Do not perform the specified workload, only verify data still matches previous | |
1231 | invocation of this workload. This option allows one to check data multiple | |
1232 | times at a later date without overwriting it. This option makes sense only for | |
1233 | workloads that write data, and does not support workloads with the | |
1234 | \fBtime_based\fR option set. | |
1235 | .TP | |
d60e92d1 AC |
1236 | .BI do_verify \fR=\fPbool |
1237 | Run the verify phase after a write phase. Only valid if \fBverify\fR is set. | |
1238 | Default: true. | |
1239 | .TP | |
1240 | .BI verify \fR=\fPstr | |
b638d82f RP |
1241 | Method of verifying file contents after each iteration of the job. Each |
1242 | verification method also implies verification of special header, which is | |
1243 | written to the beginning of each block. This header also includes meta | |
1244 | information, like offset of the block, block number, timestamp when block | |
1245 | was written, etc. \fBverify\fR=str can be combined with \fBverify_pattern\fR=str | |
1246 | option. The allowed values are: | |
d60e92d1 AC |
1247 | .RS |
1248 | .RS | |
1249 | .TP | |
844ea602 | 1250 | .B md5 crc16 crc32 crc32c crc32c-intel crc64 crc7 sha256 sha512 sha1 xxhash |
0539d758 JA |
1251 | Store appropriate checksum in the header of each block. crc32c-intel is |
1252 | hardware accelerated SSE4.2 driven, falls back to regular crc32c if | |
1253 | not supported by the system. | |
d60e92d1 AC |
1254 | .TP |
1255 | .B meta | |
b638d82f RP |
1256 | This option is deprecated, since now meta information is included in generic |
1257 | verification header and meta verification happens by default. For detailed | |
1258 | information see the description of the \fBverify\fR=str setting. This option | |
1259 | is kept because of compatibility's sake with old configurations. Do not use it. | |
d60e92d1 | 1260 | .TP |
59245381 JA |
1261 | .B pattern |
1262 | Verify a strict pattern. Normally fio includes a header with some basic | |
1263 | information and checksumming, but if this option is set, only the | |
1264 | specific pattern set with \fBverify_pattern\fR is verified. | |
1265 | .TP | |
d60e92d1 AC |
1266 | .B null |
1267 | Pretend to verify. Used for testing internals. | |
1268 | .RE | |
b892dc08 JA |
1269 | |
1270 | This option can be used for repeated burn-in tests of a system to make sure | |
1271 | that the written data is also correctly read back. If the data direction given | |
1272 | is a read or random read, fio will assume that it should verify a previously | |
1273 | written file. If the data direction includes any form of write, the verify will | |
1274 | be of the newly written data. | |
d60e92d1 AC |
1275 | .RE |
1276 | .TP | |
5c9323fb | 1277 | .BI verifysort \fR=\fPbool |
d60e92d1 AC |
1278 | If true, written verify blocks are sorted if \fBfio\fR deems it to be faster to |
1279 | read them back in a sorted manner. Default: true. | |
1280 | .TP | |
fa769d44 SW |
1281 | .BI verifysort_nr \fR=\fPint |
1282 | Pre-load and sort verify blocks for a read workload. | |
1283 | .TP | |
f7fa2653 | 1284 | .BI verify_offset \fR=\fPint |
d60e92d1 | 1285 | Swap the verification header with data somewhere else in the block before |
d1429b5c | 1286 | writing. It is swapped back before verifying. |
d60e92d1 | 1287 | .TP |
f7fa2653 | 1288 | .BI verify_interval \fR=\fPint |
d60e92d1 AC |
1289 | Write the verification header for this number of bytes, which should divide |
1290 | \fBblocksize\fR. Default: \fBblocksize\fR. | |
1291 | .TP | |
996093bb JA |
1292 | .BI verify_pattern \fR=\fPstr |
1293 | If set, fio will fill the io buffers with this pattern. Fio defaults to filling | |
1294 | with totally random bytes, but sometimes it's interesting to fill with a known | |
1295 | pattern for io verification purposes. Depending on the width of the pattern, | |
1296 | fio will fill 1/2/3/4 bytes of the buffer at the time(it can be either a | |
1297 | decimal or a hex number). The verify_pattern if larger than a 32-bit quantity | |
1298 | has to be a hex number that starts with either "0x" or "0X". Use with | |
b638d82f RP |
1299 | \fBverify\fP=str. Also, verify_pattern supports %o format, which means that for |
1300 | each block offset will be written and then verifyied back, e.g.: | |
2fa5a241 RP |
1301 | .RS |
1302 | .RS | |
1303 | \fBverify_pattern\fR=%o | |
1304 | .RE | |
1305 | Or use combination of everything: | |
1306 | .LP | |
1307 | .RS | |
1308 | \fBverify_pattern\fR=0xff%o"abcd"-21 | |
1309 | .RE | |
1310 | .RE | |
996093bb | 1311 | .TP |
d60e92d1 AC |
1312 | .BI verify_fatal \fR=\fPbool |
1313 | If true, exit the job on the first observed verification failure. Default: | |
1314 | false. | |
1315 | .TP | |
b463e936 JA |
1316 | .BI verify_dump \fR=\fPbool |
1317 | If set, dump the contents of both the original data block and the data block we | |
1318 | read off disk to files. This allows later analysis to inspect just what kind of | |
ef71e317 | 1319 | data corruption occurred. Off by default. |
b463e936 | 1320 | .TP |
e8462bd8 JA |
1321 | .BI verify_async \fR=\fPint |
1322 | Fio will normally verify IO inline from the submitting thread. This option | |
1323 | takes an integer describing how many async offload threads to create for IO | |
1324 | verification instead, causing fio to offload the duty of verifying IO contents | |
c85c324c JA |
1325 | to one or more separate threads. If using this offload option, even sync IO |
1326 | engines can benefit from using an \fBiodepth\fR setting higher than 1, as it | |
1327 | allows them to have IO in flight while verifies are running. | |
e8462bd8 JA |
1328 | .TP |
1329 | .BI verify_async_cpus \fR=\fPstr | |
1330 | Tell fio to set the given CPU affinity on the async IO verification threads. | |
1331 | See \fBcpus_allowed\fP for the format used. | |
1332 | .TP | |
6f87418f JA |
1333 | .BI verify_backlog \fR=\fPint |
1334 | Fio will normally verify the written contents of a job that utilizes verify | |
1335 | once that job has completed. In other words, everything is written then | |
1336 | everything is read back and verified. You may want to verify continually | |
1337 | instead for a variety of reasons. Fio stores the meta data associated with an | |
1338 | IO block in memory, so for large verify workloads, quite a bit of memory would | |
092f707f DN |
1339 | be used up holding this meta data. If this option is enabled, fio will write |
1340 | only N blocks before verifying these blocks. | |
6f87418f JA |
1341 | .TP |
1342 | .BI verify_backlog_batch \fR=\fPint | |
1343 | Control how many blocks fio will verify if verify_backlog is set. If not set, | |
1344 | will default to the value of \fBverify_backlog\fR (meaning the entire queue is | |
ff6bb260 SL |
1345 | read back and verified). If \fBverify_backlog_batch\fR is less than |
1346 | \fBverify_backlog\fR then not all blocks will be verified, if | |
092f707f DN |
1347 | \fBverify_backlog_batch\fR is larger than \fBverify_backlog\fR, some blocks |
1348 | will be verified more than once. | |
6f87418f | 1349 | .TP |
fa769d44 SW |
1350 | .BI trim_percentage \fR=\fPint |
1351 | Number of verify blocks to discard/trim. | |
1352 | .TP | |
1353 | .BI trim_verify_zero \fR=\fPbool | |
1354 | Verify that trim/discarded blocks are returned as zeroes. | |
1355 | .TP | |
1356 | .BI trim_backlog \fR=\fPint | |
1357 | Trim after this number of blocks are written. | |
1358 | .TP | |
1359 | .BI trim_backlog_batch \fR=\fPint | |
1360 | Trim this number of IO blocks. | |
1361 | .TP | |
1362 | .BI experimental_verify \fR=\fPbool | |
1363 | Enable experimental verification. | |
1364 | .TP | |
ca09be4b JA |
1365 | .BI verify_state_save \fR=\fPbool |
1366 | When a job exits during the write phase of a verify workload, save its | |
1367 | current state. This allows fio to replay up until that point, if the | |
1368 | verify state is loaded for the verify read phase. | |
1369 | .TP | |
1370 | .BI verify_state_load \fR=\fPbool | |
1371 | If a verify termination trigger was used, fio stores the current write | |
1372 | state of each thread. This can be used at verification time so that fio | |
1373 | knows how far it should verify. Without this information, fio will run | |
1374 | a full verification pass, according to the settings in the job file used. | |
1375 | .TP | |
d392365e | 1376 | .B stonewall "\fR,\fP wait_for_previous" |
5982a925 | 1377 | Wait for preceding jobs in the job file to exit before starting this one. |
d60e92d1 AC |
1378 | \fBstonewall\fR implies \fBnew_group\fR. |
1379 | .TP | |
1380 | .B new_group | |
1381 | Start a new reporting group. If not given, all jobs in a file will be part | |
1382 | of the same reporting group, unless separated by a stonewall. | |
1383 | .TP | |
1384 | .BI numjobs \fR=\fPint | |
ff6bb260 | 1385 | Number of clones (processes/threads performing the same workload) of this job. |
d60e92d1 AC |
1386 | Default: 1. |
1387 | .TP | |
1388 | .B group_reporting | |
1389 | If set, display per-group reports instead of per-job when \fBnumjobs\fR is | |
1390 | specified. | |
1391 | .TP | |
1392 | .B thread | |
1393 | Use threads created with \fBpthread_create\fR\|(3) instead of processes created | |
1394 | with \fBfork\fR\|(2). | |
1395 | .TP | |
f7fa2653 | 1396 | .BI zonesize \fR=\fPint |
d60e92d1 AC |
1397 | Divide file into zones of the specified size in bytes. See \fBzoneskip\fR. |
1398 | .TP | |
fa769d44 SW |
1399 | .BI zonerange \fR=\fPint |
1400 | Give size of an IO zone. See \fBzoneskip\fR. | |
1401 | .TP | |
f7fa2653 | 1402 | .BI zoneskip \fR=\fPint |
d1429b5c | 1403 | Skip the specified number of bytes when \fBzonesize\fR bytes of data have been |
d60e92d1 AC |
1404 | read. |
1405 | .TP | |
1406 | .BI write_iolog \fR=\fPstr | |
5b42a488 SH |
1407 | Write the issued I/O patterns to the specified file. Specify a separate file |
1408 | for each job, otherwise the iologs will be interspersed and the file may be | |
1409 | corrupt. | |
d60e92d1 AC |
1410 | .TP |
1411 | .BI read_iolog \fR=\fPstr | |
1412 | Replay the I/O patterns contained in the specified file generated by | |
1413 | \fBwrite_iolog\fR, or may be a \fBblktrace\fR binary file. | |
1414 | .TP | |
64bbb865 DN |
1415 | .BI replay_no_stall \fR=\fPint |
1416 | While replaying I/O patterns using \fBread_iolog\fR the default behavior | |
1417 | attempts to respect timing information between I/Os. Enabling | |
1418 | \fBreplay_no_stall\fR causes I/Os to be replayed as fast as possible while | |
1419 | still respecting ordering. | |
1420 | .TP | |
d1c46c04 DN |
1421 | .BI replay_redirect \fR=\fPstr |
1422 | While replaying I/O patterns using \fBread_iolog\fR the default behavior | |
1423 | is to replay the IOPS onto the major/minor device that each IOP was recorded | |
1424 | from. Setting \fBreplay_redirect\fR causes all IOPS to be replayed onto the | |
1425 | single specified device regardless of the device it was recorded from. | |
1426 | .TP | |
0c63576e JA |
1427 | .BI replay_align \fR=\fPint |
1428 | Force alignment of IO offsets and lengths in a trace to this power of 2 value. | |
1429 | .TP | |
1430 | .BI replay_scale \fR=\fPint | |
1431 | Scale sector offsets down by this factor when replaying traces. | |
1432 | .TP | |
3a5db920 JA |
1433 | .BI per_job_logs \fR=\fPbool |
1434 | If set, this generates bw/clat/iops log with per file private filenames. If | |
1435 | not set, jobs with identical names will share the log filename. Default: true. | |
1436 | .TP | |
836bad52 | 1437 | .BI write_bw_log \fR=\fPstr |
901bb994 JA |
1438 | If given, write a bandwidth log of the jobs in this job file. Can be used to |
1439 | store data of the bandwidth of the jobs in their lifetime. The included | |
1440 | fio_generate_plots script uses gnuplot to turn these text files into nice | |
26b26fca | 1441 | graphs. See \fBwrite_lat_log\fR for behaviour of given filename. For this |
8ad3b3dd | 1442 | option, the postfix is _bw.x.log, where x is the index of the job (1..N, |
3a5db920 | 1443 | where N is the number of jobs). If \fBper_job_logs\fR is false, then the |
a3ae5b05 JA |
1444 | filename will not include the job index. See the \fBLOG FILE FORMATS\fR |
1445 | section. | |
d60e92d1 | 1446 | .TP |
836bad52 | 1447 | .BI write_lat_log \fR=\fPstr |
901bb994 | 1448 | Same as \fBwrite_bw_log\fR, but writes I/O completion latencies. If no |
8ad3b3dd JA |
1449 | filename is given with this option, the default filename of |
1450 | "jobname_type.x.log" is used, where x is the index of the job (1..N, where | |
1451 | N is the number of jobs). Even if the filename is given, fio will still | |
3a5db920 | 1452 | append the type of log. If \fBper_job_logs\fR is false, then the filename will |
a3ae5b05 | 1453 | not include the job index. See the \fBLOG FILE FORMATS\fR section. |
901bb994 | 1454 | .TP |
c8eeb9df JA |
1455 | .BI write_iops_log \fR=\fPstr |
1456 | Same as \fBwrite_bw_log\fR, but writes IOPS. If no filename is given with this | |
8ad3b3dd JA |
1457 | option, the default filename of "jobname_type.x.log" is used, where x is the |
1458 | index of the job (1..N, where N is the number of jobs). Even if the filename | |
3a5db920 | 1459 | is given, fio will still append the type of log. If \fBper_job_logs\fR is false, |
a3ae5b05 JA |
1460 | then the filename will not include the job index. See the \fBLOG FILE FORMATS\fR |
1461 | section. | |
c8eeb9df | 1462 | .TP |
b8bc8cba JA |
1463 | .BI log_avg_msec \fR=\fPint |
1464 | By default, fio will log an entry in the iops, latency, or bw log for every | |
1465 | IO that completes. When writing to the disk log, that can quickly grow to a | |
1466 | very large size. Setting this option makes fio average the each log entry | |
e6989e10 JA |
1467 | over the specified period of time, reducing the resolution of the log. See |
1468 | \fBlog_max\fR as well. Defaults to 0, logging all entries. | |
1469 | .TP | |
1470 | .BI log_max \fR=\fPbool | |
1471 | If \fBlog_avg_msec\fR is set, fio logs the average over that window. If you | |
1472 | instead want to log the maximum value, set this option to 1. Defaults to | |
1473 | 0, meaning that averaged values are logged. | |
b8bc8cba | 1474 | .TP |
ae588852 JA |
1475 | .BI log_offset \fR=\fPbool |
1476 | If this is set, the iolog options will include the byte offset for the IO | |
1477 | entry as well as the other data values. | |
1478 | .TP | |
aee2ab67 JA |
1479 | .BI log_compression \fR=\fPint |
1480 | If this is set, fio will compress the IO logs as it goes, to keep the memory | |
1481 | footprint lower. When a log reaches the specified size, that chunk is removed | |
1482 | and compressed in the background. Given that IO logs are fairly highly | |
1483 | compressible, this yields a nice memory savings for longer runs. The downside | |
1484 | is that the compression will consume some background CPU cycles, so it may | |
1485 | impact the run. This, however, is also true if the logging ends up consuming | |
1486 | most of the system memory. So pick your poison. The IO logs are saved | |
1487 | normally at the end of a run, by decompressing the chunks and storing them | |
1488 | in the specified log file. This feature depends on the availability of zlib. | |
1489 | .TP | |
c08f9fe2 JA |
1490 | .BI log_compression_cpus \fR=\fPstr |
1491 | Define the set of CPUs that are allowed to handle online log compression | |
1492 | for the IO jobs. This can provide better isolation between performance | |
1493 | sensitive jobs, and background compression work. | |
1494 | .TP | |
b26317c9 | 1495 | .BI log_store_compressed \fR=\fPbool |
c08f9fe2 JA |
1496 | If set, fio will store the log files in a compressed format. They can be |
1497 | decompressed with fio, using the \fB\-\-inflate-log\fR command line parameter. | |
1498 | The files will be stored with a \fB\.fz\fR suffix. | |
b26317c9 | 1499 | .TP |
66347cfa DE |
1500 | .BI block_error_percentiles \fR=\fPbool |
1501 | If set, record errors in trim block-sized units from writes and trims and output | |
1502 | a histogram of how many trims it took to get to errors, and what kind of error | |
1503 | was encountered. | |
1504 | .TP | |
836bad52 | 1505 | .BI disable_lat \fR=\fPbool |
02af0988 | 1506 | Disable measurements of total latency numbers. Useful only for cutting |
ccc2b328 | 1507 | back the number of calls to \fBgettimeofday\fR\|(2), as that does impact performance at |
901bb994 JA |
1508 | really high IOPS rates. Note that to really get rid of a large amount of these |
1509 | calls, this option must be used with disable_slat and disable_bw as well. | |
1510 | .TP | |
836bad52 | 1511 | .BI disable_clat \fR=\fPbool |
c95f9daf | 1512 | Disable measurements of completion latency numbers. See \fBdisable_lat\fR. |
02af0988 | 1513 | .TP |
836bad52 | 1514 | .BI disable_slat \fR=\fPbool |
02af0988 | 1515 | Disable measurements of submission latency numbers. See \fBdisable_lat\fR. |
901bb994 | 1516 | .TP |
836bad52 | 1517 | .BI disable_bw_measurement \fR=\fPbool |
02af0988 | 1518 | Disable measurements of throughput/bandwidth numbers. See \fBdisable_lat\fR. |
d60e92d1 | 1519 | .TP |
f7fa2653 | 1520 | .BI lockmem \fR=\fPint |
d60e92d1 | 1521 | Pin the specified amount of memory with \fBmlock\fR\|(2). Can be used to |
81c6b6cd | 1522 | simulate a smaller amount of memory. The amount specified is per worker. |
d60e92d1 AC |
1523 | .TP |
1524 | .BI exec_prerun \fR=\fPstr | |
1525 | Before running the job, execute the specified command with \fBsystem\fR\|(3). | |
ce486495 EV |
1526 | .RS |
1527 | Output is redirected in a file called \fBjobname.prerun.txt\fR | |
1528 | .RE | |
d60e92d1 AC |
1529 | .TP |
1530 | .BI exec_postrun \fR=\fPstr | |
1531 | Same as \fBexec_prerun\fR, but the command is executed after the job completes. | |
ce486495 EV |
1532 | .RS |
1533 | Output is redirected in a file called \fBjobname.postrun.txt\fR | |
1534 | .RE | |
d60e92d1 AC |
1535 | .TP |
1536 | .BI ioscheduler \fR=\fPstr | |
1537 | Attempt to switch the device hosting the file to the specified I/O scheduler. | |
1538 | .TP | |
d60e92d1 | 1539 | .BI disk_util \fR=\fPbool |
d1429b5c | 1540 | Generate disk utilization statistics if the platform supports it. Default: true. |
901bb994 | 1541 | .TP |
23893646 JA |
1542 | .BI clocksource \fR=\fPstr |
1543 | Use the given clocksource as the base of timing. The supported options are: | |
1544 | .RS | |
1545 | .TP | |
1546 | .B gettimeofday | |
ccc2b328 | 1547 | \fBgettimeofday\fR\|(2) |
23893646 JA |
1548 | .TP |
1549 | .B clock_gettime | |
ccc2b328 | 1550 | \fBclock_gettime\fR\|(2) |
23893646 JA |
1551 | .TP |
1552 | .B cpu | |
1553 | Internal CPU clock source | |
1554 | .TP | |
1555 | .RE | |
1556 | .P | |
1557 | \fBcpu\fR is the preferred clocksource if it is reliable, as it is very fast | |
1558 | (and fio is heavy on time calls). Fio will automatically use this clocksource | |
1559 | if it's supported and considered reliable on the system it is running on, | |
1560 | unless another clocksource is specifically set. For x86/x86-64 CPUs, this | |
1561 | means supporting TSC Invariant. | |
1562 | .TP | |
901bb994 | 1563 | .BI gtod_reduce \fR=\fPbool |
ccc2b328 | 1564 | Enable all of the \fBgettimeofday\fR\|(2) reducing options (disable_clat, disable_slat, |
901bb994 | 1565 | disable_bw) plus reduce precision of the timeout somewhat to really shrink the |
ccc2b328 | 1566 | \fBgettimeofday\fR\|(2) call count. With this option enabled, we only do about 0.4% of |
901bb994 JA |
1567 | the gtod() calls we would have done if all time keeping was enabled. |
1568 | .TP | |
1569 | .BI gtod_cpu \fR=\fPint | |
1570 | Sometimes it's cheaper to dedicate a single thread of execution to just getting | |
1571 | the current time. Fio (and databases, for instance) are very intensive on | |
ccc2b328 | 1572 | \fBgettimeofday\fR\|(2) calls. With this option, you can set one CPU aside for doing |
901bb994 JA |
1573 | nothing but logging current time to a shared memory location. Then the other |
1574 | threads/processes that run IO workloads need only copy that segment, instead of | |
ccc2b328 | 1575 | entering the kernel with a \fBgettimeofday\fR\|(2) call. The CPU set aside for doing |
901bb994 JA |
1576 | these time calls will be excluded from other uses. Fio will manually clear it |
1577 | from the CPU mask of other jobs. | |
f2bba182 | 1578 | .TP |
8b28bd41 DM |
1579 | .BI ignore_error \fR=\fPstr |
1580 | Sometimes you want to ignore some errors during test in that case you can specify | |
1581 | error list for each error type. | |
1582 | .br | |
1583 | ignore_error=READ_ERR_LIST,WRITE_ERR_LIST,VERIFY_ERR_LIST | |
1584 | .br | |
1585 | errors for given error type is separated with ':'. | |
1586 | Error may be symbol ('ENOSPC', 'ENOMEM') or an integer. | |
1587 | .br | |
1588 | Example: ignore_error=EAGAIN,ENOSPC:122 . | |
ff6bb260 SL |
1589 | .br |
1590 | This option will ignore EAGAIN from READ, and ENOSPC and 122(EDQUOT) from WRITE. | |
8b28bd41 DM |
1591 | .TP |
1592 | .BI error_dump \fR=\fPbool | |
1593 | If set dump every error even if it is non fatal, true by default. If disabled | |
1594 | only fatal error will be dumped | |
1595 | .TP | |
fa769d44 SW |
1596 | .BI profile \fR=\fPstr |
1597 | Select a specific builtin performance test. | |
1598 | .TP | |
a696fa2a JA |
1599 | .BI cgroup \fR=\fPstr |
1600 | Add job to this control group. If it doesn't exist, it will be created. | |
6adb38a1 JA |
1601 | The system must have a mounted cgroup blkio mount point for this to work. If |
1602 | your system doesn't have it mounted, you can do so with: | |
1603 | ||
5982a925 | 1604 | # mount \-t cgroup \-o blkio none /cgroup |
a696fa2a JA |
1605 | .TP |
1606 | .BI cgroup_weight \fR=\fPint | |
1607 | Set the weight of the cgroup to this value. See the documentation that comes | |
1608 | with the kernel, allowed values are in the range of 100..1000. | |
e0b0d892 | 1609 | .TP |
7de87099 VG |
1610 | .BI cgroup_nodelete \fR=\fPbool |
1611 | Normally fio will delete the cgroups it has created after the job completion. | |
1612 | To override this behavior and to leave cgroups around after the job completion, | |
1613 | set cgroup_nodelete=1. This can be useful if one wants to inspect various | |
1614 | cgroup files after job completion. Default: false | |
1615 | .TP | |
e0b0d892 JA |
1616 | .BI uid \fR=\fPint |
1617 | Instead of running as the invoking user, set the user ID to this value before | |
1618 | the thread/process does any work. | |
1619 | .TP | |
1620 | .BI gid \fR=\fPint | |
1621 | Set group ID, see \fBuid\fR. | |
83349190 | 1622 | .TP |
fa769d44 SW |
1623 | .BI unit_base \fR=\fPint |
1624 | Base unit for reporting. Allowed values are: | |
1625 | .RS | |
1626 | .TP | |
1627 | .B 0 | |
1628 | Use auto-detection (default). | |
1629 | .TP | |
1630 | .B 8 | |
1631 | Byte based. | |
1632 | .TP | |
1633 | .B 1 | |
1634 | Bit based. | |
1635 | .RE | |
1636 | .P | |
1637 | .TP | |
9e684a49 DE |
1638 | .BI flow_id \fR=\fPint |
1639 | The ID of the flow. If not specified, it defaults to being a global flow. See | |
1640 | \fBflow\fR. | |
1641 | .TP | |
1642 | .BI flow \fR=\fPint | |
1643 | Weight in token-based flow control. If this value is used, then there is a | |
1644 | \fBflow counter\fR which is used to regulate the proportion of activity between | |
1645 | two or more jobs. fio attempts to keep this flow counter near zero. The | |
1646 | \fBflow\fR parameter stands for how much should be added or subtracted to the | |
1647 | flow counter on each iteration of the main I/O loop. That is, if one job has | |
1648 | \fBflow=8\fR and another job has \fBflow=-1\fR, then there will be a roughly | |
1649 | 1:8 ratio in how much one runs vs the other. | |
1650 | .TP | |
1651 | .BI flow_watermark \fR=\fPint | |
1652 | The maximum value that the absolute value of the flow counter is allowed to | |
1653 | reach before the job must wait for a lower value of the counter. | |
1654 | .TP | |
1655 | .BI flow_sleep \fR=\fPint | |
1656 | The period of time, in microseconds, to wait after the flow watermark has been | |
1657 | exceeded before retrying operations | |
1658 | .TP | |
83349190 YH |
1659 | .BI clat_percentiles \fR=\fPbool |
1660 | Enable the reporting of percentiles of completion latencies. | |
1661 | .TP | |
1662 | .BI percentile_list \fR=\fPfloat_list | |
66347cfa DE |
1663 | Overwrite the default list of percentiles for completion latencies and the |
1664 | block error histogram. Each number is a floating number in the range (0,100], | |
1665 | and the maximum length of the list is 20. Use ':' to separate the | |
3eb07285 | 1666 | numbers. For example, \-\-percentile_list=99.5:99.9 will cause fio to |
83349190 YH |
1667 | report the values of completion latency below which 99.5% and 99.9% of |
1668 | the observed latencies fell, respectively. | |
de890a1e SL |
1669 | .SS "Ioengine Parameters List" |
1670 | Some parameters are only valid when a specific ioengine is in use. These are | |
1671 | used identically to normal parameters, with the caveat that when used on the | |
cf145d90 | 1672 | command line, they must come after the ioengine. |
de890a1e | 1673 | .TP |
e4585935 JA |
1674 | .BI (cpu)cpuload \fR=\fPint |
1675 | Attempt to use the specified percentage of CPU cycles. | |
1676 | .TP | |
1677 | .BI (cpu)cpuchunks \fR=\fPint | |
1678 | Split the load into cycles of the given time. In microseconds. | |
1679 | .TP | |
046395d7 JA |
1680 | .BI (cpu)exit_on_io_done \fR=\fPbool |
1681 | Detect when IO threads are done, then exit. | |
1682 | .TP | |
de890a1e SL |
1683 | .BI (libaio)userspace_reap |
1684 | Normally, with the libaio engine in use, fio will use | |
1685 | the io_getevents system call to reap newly returned events. | |
1686 | With this flag turned on, the AIO ring will be read directly | |
1687 | from user-space to reap events. The reaping mode is only | |
1688 | enabled when polling for a minimum of 0 events (eg when | |
1689 | iodepth_batch_complete=0). | |
1690 | .TP | |
2cafffbe JA |
1691 | .BI (psyncv2)hipri |
1692 | Set RWF_HIPRI on IO, indicating to the kernel that it's of | |
1693 | higher priority than normal. | |
1694 | .TP | |
de890a1e SL |
1695 | .BI (net,netsplice)hostname \fR=\fPstr |
1696 | The host name or IP address to use for TCP or UDP based IO. | |
1697 | If the job is a TCP listener or UDP reader, the hostname is not | |
b511c9aa | 1698 | used and must be omitted unless it is a valid UDP multicast address. |
de890a1e SL |
1699 | .TP |
1700 | .BI (net,netsplice)port \fR=\fPint | |
6315af9d JA |
1701 | The TCP or UDP port to bind to or connect to. If this is used with |
1702 | \fBnumjobs\fR to spawn multiple instances of the same job type, then | |
1703 | this will be the starting port number since fio will use a range of ports. | |
de890a1e | 1704 | .TP |
b93b6a2e SB |
1705 | .BI (net,netsplice)interface \fR=\fPstr |
1706 | The IP address of the network interface used to send or receive UDP multicast | |
1707 | packets. | |
1708 | .TP | |
d3a623de SB |
1709 | .BI (net,netsplice)ttl \fR=\fPint |
1710 | Time-to-live value for outgoing UDP multicast packets. Default: 1 | |
1711 | .TP | |
1d360ffb JA |
1712 | .BI (net,netsplice)nodelay \fR=\fPbool |
1713 | Set TCP_NODELAY on TCP connections. | |
1714 | .TP | |
de890a1e SL |
1715 | .BI (net,netsplice)protocol \fR=\fPstr "\fR,\fP proto" \fR=\fPstr |
1716 | The network protocol to use. Accepted values are: | |
1717 | .RS | |
1718 | .RS | |
1719 | .TP | |
1720 | .B tcp | |
1721 | Transmission control protocol | |
1722 | .TP | |
49ccb8c1 JA |
1723 | .B tcpv6 |
1724 | Transmission control protocol V6 | |
1725 | .TP | |
de890a1e | 1726 | .B udp |
f5cc3d0e | 1727 | User datagram protocol |
de890a1e | 1728 | .TP |
49ccb8c1 JA |
1729 | .B udpv6 |
1730 | User datagram protocol V6 | |
1731 | .TP | |
de890a1e SL |
1732 | .B unix |
1733 | UNIX domain socket | |
1734 | .RE | |
1735 | .P | |
1736 | When the protocol is TCP or UDP, the port must also be given, | |
1737 | as well as the hostname if the job is a TCP listener or UDP | |
1738 | reader. For unix sockets, the normal filename option should be | |
1739 | used and the port is invalid. | |
1740 | .RE | |
1741 | .TP | |
1742 | .BI (net,netsplice)listen | |
1743 | For TCP network connections, tell fio to listen for incoming | |
1744 | connections rather than initiating an outgoing connection. The | |
1745 | hostname must be omitted if this option is used. | |
d54fce84 | 1746 | .TP |
7aeb1e94 | 1747 | .BI (net, pingpong) \fR=\fPbool |
cecbfd47 | 1748 | Normally a network writer will just continue writing data, and a network reader |
cf145d90 | 1749 | will just consume packets. If pingpong=1 is set, a writer will send its normal |
7aeb1e94 JA |
1750 | payload to the reader, then wait for the reader to send the same payload back. |
1751 | This allows fio to measure network latencies. The submission and completion | |
1752 | latencies then measure local time spent sending or receiving, and the | |
1753 | completion latency measures how long it took for the other end to receive and | |
b511c9aa SB |
1754 | send back. For UDP multicast traffic pingpong=1 should only be set for a single |
1755 | reader when multiple readers are listening to the same address. | |
7aeb1e94 | 1756 | .TP |
1008602c JA |
1757 | .BI (net, window_size) \fR=\fPint |
1758 | Set the desired socket buffer size for the connection. | |
1759 | .TP | |
e5f34d95 JA |
1760 | .BI (net, mss) \fR=\fPint |
1761 | Set the TCP maximum segment size (TCP_MAXSEG). | |
1762 | .TP | |
d54fce84 DM |
1763 | .BI (e4defrag,donorname) \fR=\fPstr |
1764 | File will be used as a block donor (swap extents between files) | |
1765 | .TP | |
1766 | .BI (e4defrag,inplace) \fR=\fPint | |
ff6bb260 | 1767 | Configure donor file block allocation strategy |
d54fce84 DM |
1768 | .RS |
1769 | .BI 0(default) : | |
1770 | Preallocate donor's file on init | |
1771 | .TP | |
1772 | .BI 1: | |
cecbfd47 | 1773 | allocate space immediately inside defragment event, and free right after event |
d54fce84 | 1774 | .RE |
0d978694 DAG |
1775 | .TP |
1776 | .BI (rbd)rbdname \fR=\fPstr | |
1777 | Specifies the name of the RBD. | |
1778 | .TP | |
1779 | .BI (rbd)pool \fR=\fPstr | |
1780 | Specifies the name of the Ceph pool containing the RBD. | |
1781 | .TP | |
1782 | .BI (rbd)clientname \fR=\fPstr | |
1783 | Specifies the username (without the 'client.' prefix) used to access the Ceph cluster. | |
65fa28ca DE |
1784 | .TP |
1785 | .BI (mtd)skipbad \fR=\fPbool | |
1786 | Skip operations against known bad blocks. | |
d60e92d1 | 1787 | .SH OUTPUT |
d1429b5c AC |
1788 | While running, \fBfio\fR will display the status of the created jobs. For |
1789 | example: | |
d60e92d1 | 1790 | .RS |
d1429b5c | 1791 | .P |
d60e92d1 AC |
1792 | Threads: 1: [_r] [24.8% done] [ 13509/ 8334 kb/s] [eta 00h:01m:31s] |
1793 | .RE | |
1794 | .P | |
d1429b5c AC |
1795 | The characters in the first set of brackets denote the current status of each |
1796 | threads. The possible values are: | |
1797 | .P | |
1798 | .PD 0 | |
d60e92d1 AC |
1799 | .RS |
1800 | .TP | |
1801 | .B P | |
1802 | Setup but not started. | |
1803 | .TP | |
1804 | .B C | |
1805 | Thread created. | |
1806 | .TP | |
1807 | .B I | |
1808 | Initialized, waiting. | |
1809 | .TP | |
1810 | .B R | |
1811 | Running, doing sequential reads. | |
1812 | .TP | |
1813 | .B r | |
1814 | Running, doing random reads. | |
1815 | .TP | |
1816 | .B W | |
1817 | Running, doing sequential writes. | |
1818 | .TP | |
1819 | .B w | |
1820 | Running, doing random writes. | |
1821 | .TP | |
1822 | .B M | |
1823 | Running, doing mixed sequential reads/writes. | |
1824 | .TP | |
1825 | .B m | |
1826 | Running, doing mixed random reads/writes. | |
1827 | .TP | |
1828 | .B F | |
1829 | Running, currently waiting for \fBfsync\fR\|(2). | |
1830 | .TP | |
1831 | .B V | |
1832 | Running, verifying written data. | |
1833 | .TP | |
1834 | .B E | |
1835 | Exited, not reaped by main thread. | |
1836 | .TP | |
1837 | .B \- | |
1838 | Exited, thread reaped. | |
1839 | .RE | |
d1429b5c | 1840 | .PD |
d60e92d1 AC |
1841 | .P |
1842 | The second set of brackets shows the estimated completion percentage of | |
1843 | the current group. The third set shows the read and write I/O rate, | |
1844 | respectively. Finally, the estimated run time of the job is displayed. | |
1845 | .P | |
1846 | When \fBfio\fR completes (or is interrupted by Ctrl-C), it will show data | |
1847 | for each thread, each group of threads, and each disk, in that order. | |
1848 | .P | |
1849 | Per-thread statistics first show the threads client number, group-id, and | |
1850 | error code. The remaining figures are as follows: | |
1851 | .RS | |
d60e92d1 AC |
1852 | .TP |
1853 | .B io | |
1854 | Number of megabytes of I/O performed. | |
1855 | .TP | |
1856 | .B bw | |
1857 | Average data rate (bandwidth). | |
1858 | .TP | |
1859 | .B runt | |
1860 | Threads run time. | |
1861 | .TP | |
1862 | .B slat | |
1863 | Submission latency minimum, maximum, average and standard deviation. This is | |
1864 | the time it took to submit the I/O. | |
1865 | .TP | |
1866 | .B clat | |
1867 | Completion latency minimum, maximum, average and standard deviation. This | |
1868 | is the time between submission and completion. | |
1869 | .TP | |
1870 | .B bw | |
1871 | Bandwidth minimum, maximum, percentage of aggregate bandwidth received, average | |
1872 | and standard deviation. | |
1873 | .TP | |
1874 | .B cpu | |
1875 | CPU usage statistics. Includes user and system time, number of context switches | |
1876 | this thread went through and number of major and minor page faults. | |
1877 | .TP | |
1878 | .B IO depths | |
1879 | Distribution of I/O depths. Each depth includes everything less than (or equal) | |
1880 | to it, but greater than the previous depth. | |
1881 | .TP | |
1882 | .B IO issued | |
1883 | Number of read/write requests issued, and number of short read/write requests. | |
1884 | .TP | |
1885 | .B IO latencies | |
1886 | Distribution of I/O completion latencies. The numbers follow the same pattern | |
1887 | as \fBIO depths\fR. | |
1888 | .RE | |
d60e92d1 AC |
1889 | .P |
1890 | The group statistics show: | |
d1429b5c | 1891 | .PD 0 |
d60e92d1 AC |
1892 | .RS |
1893 | .TP | |
1894 | .B io | |
1895 | Number of megabytes I/O performed. | |
1896 | .TP | |
1897 | .B aggrb | |
1898 | Aggregate bandwidth of threads in the group. | |
1899 | .TP | |
1900 | .B minb | |
1901 | Minimum average bandwidth a thread saw. | |
1902 | .TP | |
1903 | .B maxb | |
1904 | Maximum average bandwidth a thread saw. | |
1905 | .TP | |
1906 | .B mint | |
d1429b5c | 1907 | Shortest runtime of threads in the group. |
d60e92d1 AC |
1908 | .TP |
1909 | .B maxt | |
1910 | Longest runtime of threads in the group. | |
1911 | .RE | |
d1429b5c | 1912 | .PD |
d60e92d1 AC |
1913 | .P |
1914 | Finally, disk statistics are printed with reads first: | |
d1429b5c | 1915 | .PD 0 |
d60e92d1 AC |
1916 | .RS |
1917 | .TP | |
1918 | .B ios | |
1919 | Number of I/Os performed by all groups. | |
1920 | .TP | |
1921 | .B merge | |
1922 | Number of merges in the I/O scheduler. | |
1923 | .TP | |
1924 | .B ticks | |
1925 | Number of ticks we kept the disk busy. | |
1926 | .TP | |
1927 | .B io_queue | |
1928 | Total time spent in the disk queue. | |
1929 | .TP | |
1930 | .B util | |
1931 | Disk utilization. | |
1932 | .RE | |
d1429b5c | 1933 | .PD |
8423bd11 JA |
1934 | .P |
1935 | It is also possible to get fio to dump the current output while it is | |
1936 | running, without terminating the job. To do that, send fio the \fBUSR1\fR | |
1937 | signal. | |
d60e92d1 | 1938 | .SH TERSE OUTPUT |
2b8c71b0 CE |
1939 | If the \fB\-\-minimal\fR / \fB\-\-append-terse\fR options are given, the |
1940 | results will be printed/appended in a semicolon-delimited format suitable for | |
1941 | scripted use. | |
1942 | A job description (if provided) follows on a new line. Note that the first | |
525c2bfa JA |
1943 | number in the line is the version number. If the output has to be changed |
1944 | for some reason, this number will be incremented by 1 to signify that | |
1945 | change. The fields are: | |
d60e92d1 AC |
1946 | .P |
1947 | .RS | |
5e726d0a | 1948 | .B terse version, fio version, jobname, groupid, error |
d60e92d1 AC |
1949 | .P |
1950 | Read status: | |
1951 | .RS | |
312b4af2 | 1952 | .B Total I/O \fR(KB)\fP, bandwidth \fR(KB/s)\fP, IOPS, runtime \fR(ms)\fP |
d60e92d1 AC |
1953 | .P |
1954 | Submission latency: | |
1955 | .RS | |
1956 | .B min, max, mean, standard deviation | |
1957 | .RE | |
1958 | Completion latency: | |
1959 | .RS | |
1960 | .B min, max, mean, standard deviation | |
1961 | .RE | |
1db92cb6 JA |
1962 | Completion latency percentiles (20 fields): |
1963 | .RS | |
1964 | .B Xth percentile=usec | |
1965 | .RE | |
525c2bfa JA |
1966 | Total latency: |
1967 | .RS | |
1968 | .B min, max, mean, standard deviation | |
1969 | .RE | |
d60e92d1 AC |
1970 | Bandwidth: |
1971 | .RS | |
1972 | .B min, max, aggregate percentage of total, mean, standard deviation | |
1973 | .RE | |
1974 | .RE | |
1975 | .P | |
1976 | Write status: | |
1977 | .RS | |
312b4af2 | 1978 | .B Total I/O \fR(KB)\fP, bandwidth \fR(KB/s)\fP, IOPS, runtime \fR(ms)\fP |
d60e92d1 AC |
1979 | .P |
1980 | Submission latency: | |
1981 | .RS | |
1982 | .B min, max, mean, standard deviation | |
1983 | .RE | |
1984 | Completion latency: | |
1985 | .RS | |
1986 | .B min, max, mean, standard deviation | |
1987 | .RE | |
1db92cb6 JA |
1988 | Completion latency percentiles (20 fields): |
1989 | .RS | |
1990 | .B Xth percentile=usec | |
1991 | .RE | |
525c2bfa JA |
1992 | Total latency: |
1993 | .RS | |
1994 | .B min, max, mean, standard deviation | |
1995 | .RE | |
d60e92d1 AC |
1996 | Bandwidth: |
1997 | .RS | |
1998 | .B min, max, aggregate percentage of total, mean, standard deviation | |
1999 | .RE | |
2000 | .RE | |
2001 | .P | |
d1429b5c | 2002 | CPU usage: |
d60e92d1 | 2003 | .RS |
bd2626f0 | 2004 | .B user, system, context switches, major page faults, minor page faults |
d60e92d1 AC |
2005 | .RE |
2006 | .P | |
2007 | IO depth distribution: | |
2008 | .RS | |
2009 | .B <=1, 2, 4, 8, 16, 32, >=64 | |
2010 | .RE | |
2011 | .P | |
562c2d2f | 2012 | IO latency distribution: |
d60e92d1 | 2013 | .RS |
562c2d2f DN |
2014 | Microseconds: |
2015 | .RS | |
2016 | .B <=2, 4, 10, 20, 50, 100, 250, 500, 750, 1000 | |
2017 | .RE | |
2018 | Milliseconds: | |
2019 | .RS | |
2020 | .B <=2, 4, 10, 20, 50, 100, 250, 500, 750, 1000, 2000, >=2000 | |
2021 | .RE | |
2022 | .RE | |
2023 | .P | |
f2f788dd JA |
2024 | Disk utilization (1 for each disk used): |
2025 | .RS | |
2026 | .B name, read ios, write ios, read merges, write merges, read ticks, write ticks, read in-queue time, write in-queue time, disk utilization percentage | |
2027 | .RE | |
2028 | .P | |
5982a925 | 2029 | Error Info (dependent on continue_on_error, default off): |
562c2d2f | 2030 | .RS |
ff6bb260 | 2031 | .B total # errors, first error code |
d60e92d1 AC |
2032 | .RE |
2033 | .P | |
562c2d2f | 2034 | .B text description (if provided in config - appears on newline) |
d60e92d1 | 2035 | .RE |
29dbd1e5 JA |
2036 | .SH TRACE FILE FORMAT |
2037 | There are two trace file format that you can encounter. The older (v1) format | |
2038 | is unsupported since version 1.20-rc3 (March 2008). It will still be described | |
2039 | below in case that you get an old trace and want to understand it. | |
2040 | ||
2041 | In any case the trace is a simple text file with a single action per line. | |
2042 | ||
2043 | .P | |
2044 | .B Trace file format v1 | |
2045 | .RS | |
2046 | Each line represents a single io action in the following format: | |
2047 | ||
2048 | rw, offset, length | |
2049 | ||
2050 | where rw=0/1 for read/write, and the offset and length entries being in bytes. | |
2051 | ||
2052 | This format is not supported in Fio versions => 1.20-rc3. | |
2053 | ||
2054 | .RE | |
2055 | .P | |
2056 | .B Trace file format v2 | |
2057 | .RS | |
2058 | The second version of the trace file format was added in Fio version 1.17. | |
2059 | It allows to access more then one file per trace and has a bigger set of | |
2060 | possible file actions. | |
2061 | ||
2062 | The first line of the trace file has to be: | |
2063 | ||
2064 | \fBfio version 2 iolog\fR | |
2065 | ||
2066 | Following this can be lines in two different formats, which are described below. | |
2067 | The file management format: | |
2068 | ||
2069 | \fBfilename action\fR | |
2070 | ||
2071 | The filename is given as an absolute path. The action can be one of these: | |
2072 | ||
2073 | .P | |
2074 | .PD 0 | |
2075 | .RS | |
2076 | .TP | |
2077 | .B add | |
2078 | Add the given filename to the trace | |
2079 | .TP | |
2080 | .B open | |
2081 | Open the file with the given filename. The filename has to have been previously | |
2082 | added with the \fBadd\fR action. | |
2083 | .TP | |
2084 | .B close | |
2085 | Close the file with the given filename. The file must have previously been | |
2086 | opened. | |
2087 | .RE | |
2088 | .PD | |
2089 | .P | |
2090 | ||
2091 | The file io action format: | |
2092 | ||
2093 | \fBfilename action offset length\fR | |
2094 | ||
2095 | The filename is given as an absolute path, and has to have been added and opened | |
2096 | before it can be used with this format. The offset and length are given in | |
2097 | bytes. The action can be one of these: | |
2098 | ||
2099 | .P | |
2100 | .PD 0 | |
2101 | .RS | |
2102 | .TP | |
2103 | .B wait | |
2104 | Wait for 'offset' microseconds. Everything below 100 is discarded. The time is | |
2105 | relative to the previous wait statement. | |
2106 | .TP | |
2107 | .B read | |
2108 | Read \fBlength\fR bytes beginning from \fBoffset\fR | |
2109 | .TP | |
2110 | .B write | |
2111 | Write \fBlength\fR bytes beginning from \fBoffset\fR | |
2112 | .TP | |
2113 | .B sync | |
2114 | fsync() the file | |
2115 | .TP | |
2116 | .B datasync | |
2117 | fdatasync() the file | |
2118 | .TP | |
2119 | .B trim | |
2120 | trim the given file from the given \fBoffset\fR for \fBlength\fR bytes | |
2121 | .RE | |
2122 | .PD | |
2123 | .P | |
2124 | ||
2125 | .SH CPU IDLENESS PROFILING | |
2126 | In some cases, we want to understand CPU overhead in a test. For example, | |
2127 | we test patches for the specific goodness of whether they reduce CPU usage. | |
2128 | fio implements a balloon approach to create a thread per CPU that runs at | |
2129 | idle priority, meaning that it only runs when nobody else needs the cpu. | |
2130 | By measuring the amount of work completed by the thread, idleness of each | |
2131 | CPU can be derived accordingly. | |
2132 | ||
2133 | An unit work is defined as touching a full page of unsigned characters. Mean | |
2134 | and standard deviation of time to complete an unit work is reported in "unit | |
2135 | work" section. Options can be chosen to report detailed percpu idleness or | |
2136 | overall system idleness by aggregating percpu stats. | |
2137 | ||
2138 | .SH VERIFICATION AND TRIGGERS | |
2139 | Fio is usually run in one of two ways, when data verification is done. The | |
2140 | first is a normal write job of some sort with verify enabled. When the | |
2141 | write phase has completed, fio switches to reads and verifies everything | |
2142 | it wrote. The second model is running just the write phase, and then later | |
2143 | on running the same job (but with reads instead of writes) to repeat the | |
2144 | same IO patterns and verify the contents. Both of these methods depend | |
2145 | on the write phase being completed, as fio otherwise has no idea how much | |
2146 | data was written. | |
2147 | ||
2148 | With verification triggers, fio supports dumping the current write state | |
2149 | to local files. Then a subsequent read verify workload can load this state | |
2150 | and know exactly where to stop. This is useful for testing cases where | |
2151 | power is cut to a server in a managed fashion, for instance. | |
2152 | ||
2153 | A verification trigger consists of two things: | |
2154 | ||
2155 | .RS | |
2156 | Storing the write state of each job | |
2157 | .LP | |
2158 | Executing a trigger command | |
2159 | .RE | |
2160 | ||
2161 | The write state is relatively small, on the order of hundreds of bytes | |
2162 | to single kilobytes. It contains information on the number of completions | |
2163 | done, the last X completions, etc. | |
2164 | ||
2165 | A trigger is invoked either through creation (\fBtouch\fR) of a specified | |
2166 | file in the system, or through a timeout setting. If fio is run with | |
2167 | \fB\-\-trigger\-file=/tmp/trigger-file\fR, then it will continually check for | |
2168 | the existence of /tmp/trigger-file. When it sees this file, it will | |
2169 | fire off the trigger (thus saving state, and executing the trigger | |
2170 | command). | |
2171 | ||
2172 | For client/server runs, there's both a local and remote trigger. If | |
2173 | fio is running as a server backend, it will send the job states back | |
2174 | to the client for safe storage, then execute the remote trigger, if | |
2175 | specified. If a local trigger is specified, the server will still send | |
2176 | back the write state, but the client will then execute the trigger. | |
2177 | ||
2178 | .RE | |
2179 | .P | |
2180 | .B Verification trigger example | |
2181 | .RS | |
2182 | ||
2183 | Lets say we want to run a powercut test on the remote machine 'server'. | |
2184 | Our write workload is in write-test.fio. We want to cut power to 'server' | |
2185 | at some point during the run, and we'll run this test from the safety | |
2186 | or our local machine, 'localbox'. On the server, we'll start the fio | |
2187 | backend normally: | |
2188 | ||
2189 | server# \fBfio \-\-server\fR | |
2190 | ||
2191 | and on the client, we'll fire off the workload: | |
2192 | ||
e0ee7a8b | 2193 | localbox$ \fBfio \-\-client=server \-\-trigger\-file=/tmp/my\-trigger \-\-trigger-remote="bash \-c "echo b > /proc/sysrq-triger""\fR |
29dbd1e5 JA |
2194 | |
2195 | We set \fB/tmp/my-trigger\fR as the trigger file, and we tell fio to execute | |
2196 | ||
2197 | \fBecho b > /proc/sysrq-trigger\fR | |
2198 | ||
2199 | on the server once it has received the trigger and sent us the write | |
2200 | state. This will work, but it's not \fIreally\fR cutting power to the server, | |
2201 | it's merely abruptly rebooting it. If we have a remote way of cutting | |
2202 | power to the server through IPMI or similar, we could do that through | |
2203 | a local trigger command instead. Lets assume we have a script that does | |
2204 | IPMI reboot of a given hostname, ipmi-reboot. On localbox, we could | |
2205 | then have run fio with a local trigger instead: | |
2206 | ||
2207 | localbox$ \fBfio \-\-client=server \-\-trigger\-file=/tmp/my\-trigger \-\-trigger="ipmi-reboot server"\fR | |
2208 | ||
2209 | For this case, fio would wait for the server to send us the write state, | |
2210 | then execute 'ipmi-reboot server' when that happened. | |
2211 | ||
2212 | .RE | |
2213 | .P | |
2214 | .B Loading verify state | |
2215 | .RS | |
2216 | To load store write state, read verification job file must contain | |
2217 | the verify_state_load option. If that is set, fio will load the previously | |
2218 | stored state. For a local fio run this is done by loading the files directly, | |
2219 | and on a client/server run, the server backend will ask the client to send | |
2220 | the files over and load them from there. | |
2221 | ||
2222 | .RE | |
2223 | ||
a3ae5b05 JA |
2224 | .SH LOG FILE FORMATS |
2225 | ||
2226 | Fio supports a variety of log file formats, for logging latencies, bandwidth, | |
2227 | and IOPS. The logs share a common format, which looks like this: | |
2228 | ||
2229 | .B time (msec), value, data direction, offset | |
2230 | ||
2231 | Time for the log entry is always in milliseconds. The value logged depends | |
2232 | on the type of log, it will be one of the following: | |
2233 | ||
2234 | .P | |
2235 | .PD 0 | |
2236 | .TP | |
2237 | .B Latency log | |
2238 | Value is in latency in usecs | |
2239 | .TP | |
2240 | .B Bandwidth log | |
2241 | Value is in KB/sec | |
2242 | .TP | |
2243 | .B IOPS log | |
2244 | Value is in IOPS | |
2245 | .PD | |
2246 | .P | |
2247 | ||
2248 | Data direction is one of the following: | |
2249 | ||
2250 | .P | |
2251 | .PD 0 | |
2252 | .TP | |
2253 | .B 0 | |
2254 | IO is a READ | |
2255 | .TP | |
2256 | .B 1 | |
2257 | IO is a WRITE | |
2258 | .TP | |
2259 | .B 2 | |
2260 | IO is a TRIM | |
2261 | .PD | |
2262 | .P | |
2263 | ||
2264 | The \fIoffset\fR is the offset, in bytes, from the start of the file, for that | |
2265 | particular IO. The logging of the offset can be toggled with \fBlog_offset\fR. | |
2266 | ||
2267 | If windowed logging is enabled though \fBlog_avg_msec\fR, then fio doesn't log | |
2268 | individual IOs. Instead of logs the average values over the specified | |
2269 | period of time. Since \fIdata direction\fR and \fIoffset\fR are per-IO values, | |
2270 | they aren't applicable if windowed logging is enabled. If windowed logging | |
2271 | is enabled and \fBlog_max_value\fR is set, then fio logs maximum values in | |
2272 | that window instead of averages. | |
2273 | ||
2274 | .RE | |
2275 | ||
49da1240 JA |
2276 | .SH CLIENT / SERVER |
2277 | Normally you would run fio as a stand-alone application on the machine | |
2278 | where the IO workload should be generated. However, it is also possible to | |
2279 | run the frontend and backend of fio separately. This makes it possible to | |
2280 | have a fio server running on the machine(s) where the IO workload should | |
2281 | be running, while controlling it from another machine. | |
2282 | ||
2283 | To start the server, you would do: | |
2284 | ||
2285 | \fBfio \-\-server=args\fR | |
2286 | ||
2287 | on that machine, where args defines what fio listens to. The arguments | |
811826be | 2288 | are of the form 'type:hostname or IP:port'. 'type' is either 'ip' (or ip4) |
20c67f10 MS |
2289 | for TCP/IP v4, 'ip6' for TCP/IP v6, or 'sock' for a local unix domain |
2290 | socket. 'hostname' is either a hostname or IP address, and 'port' is the port to | |
811826be | 2291 | listen to (only valid for TCP/IP, not a local socket). Some examples: |
49da1240 | 2292 | |
e0ee7a8b | 2293 | 1) \fBfio \-\-server\fR |
49da1240 JA |
2294 | |
2295 | Start a fio server, listening on all interfaces on the default port (8765). | |
2296 | ||
e0ee7a8b | 2297 | 2) \fBfio \-\-server=ip:hostname,4444\fR |
49da1240 JA |
2298 | |
2299 | Start a fio server, listening on IP belonging to hostname and on port 4444. | |
2300 | ||
e0ee7a8b | 2301 | 3) \fBfio \-\-server=ip6:::1,4444\fR |
811826be JA |
2302 | |
2303 | Start a fio server, listening on IPv6 localhost ::1 and on port 4444. | |
2304 | ||
e0ee7a8b | 2305 | 4) \fBfio \-\-server=,4444\fR |
49da1240 JA |
2306 | |
2307 | Start a fio server, listening on all interfaces on port 4444. | |
2308 | ||
e0ee7a8b | 2309 | 5) \fBfio \-\-server=1.2.3.4\fR |
49da1240 JA |
2310 | |
2311 | Start a fio server, listening on IP 1.2.3.4 on the default port. | |
2312 | ||
e0ee7a8b | 2313 | 6) \fBfio \-\-server=sock:/tmp/fio.sock\fR |
49da1240 JA |
2314 | |
2315 | Start a fio server, listening on the local socket /tmp/fio.sock. | |
2316 | ||
2317 | When a server is running, you can connect to it from a client. The client | |
2318 | is run with: | |
2319 | ||
e0ee7a8b | 2320 | \fBfio \-\-local-args \-\-client=server \-\-remote-args <job file(s)>\fR |
49da1240 | 2321 | |
e01e9745 MS |
2322 | where \-\-local-args are arguments that are local to the client where it is |
2323 | running, 'server' is the connect string, and \-\-remote-args and <job file(s)> | |
49da1240 JA |
2324 | are sent to the server. The 'server' string follows the same format as it |
2325 | does on the server side, to allow IP/hostname/socket and port strings. | |
2326 | You can connect to multiple clients as well, to do that you could run: | |
2327 | ||
e0ee7a8b | 2328 | \fBfio \-\-client=server2 \-\-client=server2 <job file(s)>\fR |
323255cc JA |
2329 | |
2330 | If the job file is located on the fio server, then you can tell the server | |
2331 | to load a local file as well. This is done by using \-\-remote-config: | |
2332 | ||
e0ee7a8b | 2333 | \fBfio \-\-client=server \-\-remote-config /path/to/file.fio\fR |
323255cc | 2334 | |
39b5f61e | 2335 | Then fio will open this local (to the server) job file instead |
323255cc | 2336 | of being passed one from the client. |
39b5f61e | 2337 | |
ff6bb260 | 2338 | If you have many servers (example: 100 VMs/containers), you can input a pathname |
39b5f61e BE |
2339 | of a file containing host IPs/names as the parameter value for the \-\-client option. |
2340 | For example, here is an example "host.list" file containing 2 hostnames: | |
2341 | ||
2342 | host1.your.dns.domain | |
2343 | .br | |
2344 | host2.your.dns.domain | |
2345 | ||
2346 | The fio command would then be: | |
2347 | ||
e0ee7a8b | 2348 | \fBfio \-\-client=host.list <job file>\fR |
39b5f61e BE |
2349 | |
2350 | In this mode, you cannot input server-specific parameters or job files, and all | |
2351 | servers receive the same job file. | |
2352 | ||
2353 | In order to enable fio \-\-client runs utilizing a shared filesystem from multiple hosts, | |
ff6bb260 SL |
2354 | fio \-\-client now prepends the IP address of the server to the filename. For example, |
2355 | if fio is using directory /mnt/nfs/fio and is writing filename fileio.tmp, | |
39b5f61e BE |
2356 | with a \-\-client hostfile |
2357 | containing two hostnames h1 and h2 with IP addresses 192.168.10.120 and 192.168.10.121, then | |
2358 | fio will create two files: | |
2359 | ||
2360 | /mnt/nfs/fio/192.168.10.120.fileio.tmp | |
2361 | .br | |
2362 | /mnt/nfs/fio/192.168.10.121.fileio.tmp | |
2363 | ||
d60e92d1 | 2364 | .SH AUTHORS |
49da1240 | 2365 | |
d60e92d1 | 2366 | .B fio |
aa58d252 | 2367 | was written by Jens Axboe <jens.axboe@oracle.com>, |
f8b8f7da | 2368 | now Jens Axboe <axboe@fb.com>. |
d1429b5c AC |
2369 | .br |
2370 | This man page was written by Aaron Carroll <aaronc@cse.unsw.edu.au> based | |
d60e92d1 AC |
2371 | on documentation by Jens Axboe. |
2372 | .SH "REPORTING BUGS" | |
482900c9 | 2373 | Report bugs to the \fBfio\fR mailing list <fio@vger.kernel.org>. |
d1429b5c | 2374 | See \fBREADME\fR. |
d60e92d1 | 2375 | .SH "SEE ALSO" |
d1429b5c AC |
2376 | For further documentation see \fBHOWTO\fR and \fBREADME\fR. |
2377 | .br | |
2378 | Sample jobfiles are available in the \fBexamples\fR directory. |