1 .TH fio 1 "September 2007" "User Manual"
3 fio \- flexible I/O tester
6 [\fIoptions\fR] [\fIjobfile\fR]...
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.
15 .BI \-\-output \fR=\fPfilename
16 Write output to \fIfilename\fR.
18 .BI \-\-timeout \fR=\fPtimeout
19 Limit run time to \fItimeout\fR seconds.
22 Generate per-job latency logs.
25 Generate per-job bandwidth logs.
28 Print statistics in a terse, semicolon-delimited format.
30 .BI \-\-showcmd \fR=\fPjobfile
31 Convert \fIjobfile\fR to a set of command-line options.
34 Enable read-only safety checks.
36 .BI \-\-eta \fR=\fPwhen
37 Specifies when real-time ETA estimate should be printed. \fIwhen\fR may
38 be one of `always', `never' or `auto'.
40 .BI \-\-cmdhelp \fR=\fPcommand
41 Print help information for \fIcommand\fR. May be `all' for all commands.
44 Display usage information and exit.
47 Display version information and exit.
49 Job files are in `ini' format. They consist of one or more
50 job definitions, which begin with a job name in square brackets and
51 extend to the next job name. The job name can be any ASCII string
52 except `global', which has a special meaning. Following the job name is
53 a sequence of zero or more parameters, one per line, that define the
54 behavior of the job. Any line starting with a `;' or `#' character is
55 considered a comment and ignored.
58 The global section contains default parameters for jobs specified in the
59 job file. A job is only affected by global sections residing above it,
60 and there may be any number of global sections. Specific job definitions
61 may override any parameter set in global sections.
64 Some parameters may take arguments of a specific type. The types used are:
67 String: a sequence of alphanumeric characters.
70 Integer: a whole number, possibly negative. If prefixed with `0x', the value
71 is assumed to be base 16 (hexadecimal).
74 SI integer: a whole number, possibly containing a suffix denoting the base unit
75 of the value. Accepted suffixes are `k', 'M' and 'G', denoting kilo (1024),
76 mega (1024*1024) and giga (1024*1024*1024) respectively.
79 Boolean: a true or false value. `0' denotes false, `1' denotes true.
82 Integer range: a range of integers specified in the format
83 \fIlower\fR:\fIupper\fR or \fIlower\fR\-\fIupper\fR. \fIlower\fR and
84 \fIupper\fR may contain a suffix as described above. If an option allows two
85 sets of ranges, they are separated with a `,' or `/' character. For example:
90 May be used to override the job name. On the command line, this paramter
91 has the special purpose of signalling the start of a new job.
93 .BI description \fR=\fPstr
94 Human-readable description of the job. It is printed when the job is run, but
95 otherwise has no special purpose.
97 .BI directory \fR=\fPstr
98 Prefix filenames with this directory. Used to place files in a location other
101 .BI filename \fR=\fPstr
103 normally makes up a file name based on the job name, thread number, and file
104 number. If you want to share files between threads in a job or several jobs,
105 specify a \fIfilename\fR for each of them to override the default. If the I/O
106 engine used is `net', \fIfilename\fR is the host and port to connect to in the
107 format \fIhost\fR/\fIport\fR. If the I/O engine is file-based, you can specify
108 a number of files by separating the names with a `:' character. `\-' is a
109 reserved name, meaning stdin or stdout, depending on the read/write direction
112 .BI opendir \fR=\fPstr
113 Recursively open any files below directory \fIstr\fR.
115 .BI readwrite \fR=\fPstr "\fR,\fP rw" \fR=\fPstr
116 Type of I/O pattern. Accepted values are:
133 Mixed sequential reads and writes.
136 Mixed random reads and writes.
139 For mixed I/O, the default split is 50/50. For random I/O, the number of I/Os
140 to perform before getting a new offset can be specified by appending
141 `:\fIint\fR' to the pattern type. The default is 1.
144 .BI randrepeat \fR=\fPbool
145 Seed the random number generator in a predictable way so results are repeatable
146 across runs. Default: true.
148 .BI fadvise_hint \fR=\fPbool
149 Disable use of \fIposix_fadvise\fR\|(2) to advise the kernel what I/O patterns
150 are likely to be issued. Default: true.
152 .BI size \fR=\fPsiint
153 Total size of I/O for this job. \fBfio\fR will run until this many bytes have
154 been transfered, unless limited by other options (\fBruntime\fR, for instance).
155 Unless \fBnr_files\fR and \fBfilesize\fR options are given, this amount will be
156 divided between the available files for the job.
158 .BI filesize \fR=\fPirange
159 Individual file sizes. May be a range, in which case \fBfio\fR will select sizes
160 for files at random within the given range, limited to \fBsize\fR in total (if
161 that is given). If \fBfilesize\fR is not specified, each created file is the
164 .BI blocksize \fR=\fPsiint "\fR,\fB bs" \fR=\fPsiint
165 Block size for I/O units. Default: 4k. Values for reads and writes can be
166 specified seperately in the format \fIread\fR,\fIwrite\fR, either of
167 which may be empty to leave that value at its default.
169 .BI blocksize_range \fR=\fPirange "\fR,\fB bsrange" \fR=\fPirange
170 Specify a range of I/O block sizes. The issued I/O unit will always be a
171 multiple of the minimum size, unless \fBblocksize_unaligned\fR is set. Applies
172 to both reads and writes, but can be specified seperately (see \fBblocksize\fR).
174 .B blocksize_unaligned\fR,\fP bs_unaligned
175 If set, any size in \fBblocksize_range\fR may be used. This typically won't
176 work with direct I/O, as that normally requires sector alignment.
179 Initialise buffers with all zeros. Default: fill buffers with random data.
181 .BI nrfiles \fR=\fPint
182 Number of files to use for this job. Default: 1.
184 .BI openfiles \fR=\fPint
185 Number of files to keep open at the same time. Default: \fBnrfiles\fR.
187 .BI file_service_type \fR=\fPstr
188 Defines how files to service are selected. The following types are defined:
193 Choose a file at random
196 Round robin over open files (default).
199 The number of I/Os to issue before switching a new file can be specified by
200 appending `:\fIint\fR' to the service type.
203 .BI ioengine \fR=\fPstr
204 Defines how the job issues I/O. The following types are defined:
209 Basic \fIread\fR\|(2) or \fIwrite\fR\|(2) I/O. \fIfseek\fR\|(2) is used to
210 position the I/O location.
213 Basic \fIpread\fR\|(2) or \fIpwrite\fR\|(2) I/O.
216 Linux native asynchronous I/O.
219 glibc POSIX asynchronous I/O using \fIaio_read\fR\|(3) and \fIaio_write\fR\|(3).
222 File is memory mapped with \fImmap\fR\|(2) and data copied using
226 \fIsplice\fR\|(2) is used to transfer the data and \fIvmsplice\fR\|(2) to
227 transfer data from user-space to the kernel.
230 Use the syslet system calls to make regular read/write asynchronous.
233 SCSI generic sg v3 I/O. May be either synchronous using the SG_IO ioctl, or if
234 the target is an sg character device, we use \fIread\fR\|(2) and
235 \fIwrite\fR\|(2) for asynchronous I/O.
238 Doesn't transfer any data, just pretends to. Mainly used to exercise \fBfio\fR
239 itself and for debugging and testing purposes.
242 Transfer over the network. \fBfilename\fR must be set appropriately to
243 `\fIhost\fR/\fIport\fR' regardless of data direction. If receiving, only the
244 \fIport\fR argument is used.
247 Like \fBnet\fR, but uses \fIsplice\fR\|(2) and \fIvmsplice\fR\|(2) to map data
251 Doesn't transfer any data, but burns CPU cycles according to \fBcpuload\fR and
252 \fBcpucycles\fR parameters.
255 The GUASI I/O engine is the Generic Userspace Asynchronous Syscall Interface
256 approach to asycnronous I/O.
258 See <http://www.xmailserver.org/guasi\-lib.html>.
261 Loads an external I/O engine object file. Append the engine filename as
266 .BI iodepth \fR=\fPint
267 Number of I/O units to keep in flight against the file. Default: 1.
269 .BI iodepth_batch \fR=\fPint
270 Number of I/Os to submit at once. Default: \fBiodepth\fR.
272 .BI iodepth_low \fR=\fPint
273 Low watermark indicating when to start filling the queue again. Default:
276 .BI direct \fR=\fPbool
277 If true, use non-buffered I/O (usually O_DIRECT). Default: false.
279 .BI buffered \fR=\fPbool
280 If true, use buffered I/O. This is the opposite of the \fBdirect\fR parameter.
283 .BI offset \fR=\fPsiint
284 Offset in the file to start I/O. Data before the offset will not be touched.
287 How many I/Os to perform before issuing an \fBfsync\fR\|(2) of dirty data. If
288 0, don't sync. Default: 0.
290 .BI overwrite \fR=\fPbool
291 If writing, setup the file first and do overwrites. Default: false.
293 .BI end_fsync \fR=\fPbool
294 Sync file contents when job exits. Default: false.
296 .BI fsync_on_close \fR=\fPbool
297 If true, sync file contents on close. This differs from \fBend_fsync\fR in that
298 it will happen on every close, not just at the end of the job. Default: false.
300 .BI rwmixcycle \fR=\fPint
301 How many milliseconds before switching between reads and writes for a mixed
302 workload. Default: 500ms.
304 .BI rwmixread \fR=\fPint
305 Percentage of a mixed workload that should be reads. Default: 50.
307 .BI rwmixwrite \fR=\fPint
308 Percentage of a mixed workload that should be writes. If \fBrwmixread\fR and
309 \fBwrmixwrite\fR are given and do not sum to 100%, the latter of the two
310 overrides the first. Default: 50.
313 Normally \fBfio\fR will cover every block of the file when doing random I/O. If
314 this parameter is given, a new offset will be chosen without looking at past
315 I/O history. This parameter is mutually exclusive with \fBverify\fR.
318 Run job with given nice value. See \fInice\fR\|(2).
321 Set I/O priority value of this job between 0 (highest) and 7 (lowest). See
324 .BI prioclass \fR=\fPint
325 Set I/O priority class. See \fIionice\fR\|(1).
327 .BI thinktime \fR=\fPint
328 Stall job for given number of microseconds between issuing I/Os.
330 .BI thinktime_spin \fR=\fPint
331 Pretend to spend CPU time for given number of microseconds, sleeping the rest
332 of the time specified by \fBthinktime\fR. Only valid if \fBthinktime\fR is set.
334 .BI thinktime_blocks \fR=\fPint
335 Number of blocks to issue before waiting \fBthinktime\fR microseconds.
339 Cap bandwidth used by this job to this number of KiB/s.
341 .BI ratemin \fR=\fPint
342 Tell \fBfio\fR to do whatever it can to maintain at least the given bandwidth.
343 Failing to meet this requirement will cause the job to exit.
345 .BI rate_iops \fR=\fPint
346 Cap the bandwidth to this number of IOPS. If \fBblocksize\fR is a range, the
347 smallest block size is used as the metric.
349 .BI rate_iops_min \fR=\fPint
350 If this rate of I/O is not met, the job will exit.
352 .BI ratecycle \fR=\fPint
353 Average bandwidth for \fBrate\fR and \fBratemin\fR over this number of
354 milliseconds. Default: 1000ms.
356 .BI cpumask \fR=\fPint
357 Set CPU affinity for this job. \fIint\fR is a bitmask of allowed CPUs the job
358 may run on. See \fBsched_setaffinity\fR\|(2).
360 .BI cpus_allowed \fR=\fPstr
361 Same as \fBcpumask\fR, but allows a comma-delimited list of CPU numbers.
363 .BI startdelay \fR=\fPint
364 Delay start of job for the specified number of seconds.
366 .BI runtime \fR=\fPint
367 Terminate processing after the specified number of seconds.
370 If given, run for the specified \fBruntime\fR duration even if the files are
371 completely read or written. The same workload will be repeated as many times
372 as \fBruntime\fR allows.
374 .BI invalidate \fR=\fPbool
375 Invalidate buffer-cache for the file prior to starting I/O. Default: true.
378 Use synchronous I/O for buffered writes. For the majority of I/O engines,
379 this means using O_SYNC. Default: false.
381 .BI iomem \fR=\fPstr "\fR,\fP mem" \fR=\fPstr
382 Allocation method for I/O unit buffer. Allowed values are:
387 Allocate memory with \fImalloc\fR\|(3).
390 Use shared memory buffers allocated through \fIshmget\fR\|(2).
393 Same as \fBshm\fR, but use huge pages as backing.
396 Use \fImmap\fR\|(2) for allocation. Uses anonymous memory unless a filename
397 is given after the option in the format `:\fIfile\fR'.
400 Same as \fBmmap\fR, but use huge files as backing.
403 The amount of memory allocated is the maximum allowed \fBblocksize\fR for the
404 job multiplied by \fBiodepth\fR. For \fBshmhuge\fR or \fBmmaphuge\fR to work,
405 the system must have free huge pages allocated. \fBmmaphuge\fR also needs to
406 have hugetlbfs mounted, and \fIfile\fR must point there.
409 .BI hugepage\-size \fR=\fPsiint
410 Defines the size of a huge page. Must be at least equal to the system setting.
411 Should be a multiple of 1MiB. Default: 4MiB.
414 Terminate all jobs when one finishes. Default: wait for each job to finish.
416 .BI bwavgtime \fR=\fPint
417 Average bandwidth calculations over the given time in milliseconds. Default:
420 .BI create_serialize \fR=\fPbool
421 If true, serialize file creation for the jobs. Default: true.
423 .BI create_fsync \fR=\fPbool
424 \fIfsync\fR\|(2) data file after creation. Default: true.
426 .BI unlink \fR=\fPbool
427 Unlink job files when done. Default: false.
430 Specifies the number of iterations (runs of the same workload) of this job.
433 .BI do_verify \fR=\fPbool
434 Run the verify phase after a write phase. Only valid if \fBverify\fR is set.
437 .BI verify \fR=\fPstr
438 Method of verifying file contents after each iteration of the job. Allowed
443 .B md5 crc16 crc32 crc64 crc7 sha256 sha512
444 Store appropriate checksum in the header of each block.
447 Write extra information about each I/O (timestamp, block number, etc.). The
448 block number is verified.
451 Fill I/O buffers with a specific pattern that is used to verify. The pattern is
452 specified by appending `:\fIint\fR' to the parameter. \fIint\fR cannot be larger
456 Pretend to verify. Used for testing internals.
460 .BI verify_sort \fR=\fPbool
461 If true, written verify blocks are sorted if \fBfio\fR deems it to be faster to
462 read them back in a sorted manner. Default: true.
464 .BI verify_offset \fR=\fPsiint
465 Swap the verification header with data somewhere else in the block before
466 writing. It is swapped back before verifying.
468 .BI verify_interval \fR=\fPsiint
469 Write the verification header for this number of bytes, which should divide
470 \fBblocksize\fR. Default: \fBblocksize\fR.
472 .BI verify_fatal \fR=\fPbool
473 If true, exit the job on the first observed verification failure. Default:
477 Wait for preceeding jobs in the job file to exit before starting this one.
478 \fBstonewall\fR implies \fBnew_group\fR.
481 Start a new reporting group. If not given, all jobs in a file will be part
482 of the same reporting group, unless separated by a stonewall.
484 .BI numjobs \fR=\fPint
485 Number of clones (processes/threads performing the same workload) of this job.
489 If set, display per-group reports instead of per-job when \fBnumjobs\fR is
493 Use threads created with \fBpthread_create\fR\|(3) instead of processes created
494 with \fBfork\fR\|(2).
496 .BI zonesize \fR=\fPsiint
497 Divide file into zones of the specified size in bytes. See \fBzoneskip\fR.
499 .BI zoneskip \fR=\fPsiint
500 Skip the specified number of bytes when \fBzonesize\fR bytes of data have been
503 .BI write_iolog \fR=\fPstr
504 Write the issued I/O patterns to the specified file.
506 .BI read_iolog \fR=\fPstr
507 Replay the I/O patterns contained in the specified file generated by
508 \fBwrite_iolog\fR, or may be a \fBblktrace\fR binary file.
511 If given, write bandwidth logs of the jobs in this file.
514 Same as \fBwrite_bw_log\fR, but writes I/O completion latencies.
516 .BI lockmem \fR=\fPsiint
517 Pin the specified amount of memory with \fBmlock\fR\|(2). Can be used to
518 simulate a smaller amount of memory.
520 .BI exec_prerun \fR=\fPstr
521 Before running the job, execute the specified command with \fBsystem\fR\|(3).
523 .BI exec_postrun \fR=\fPstr
524 Same as \fBexec_prerun\fR, but the command is executed after the job completes.
526 .BI ioscheduler \fR=\fPstr
527 Attempt to switch the device hosting the file to the specified I/O scheduler.
529 .BI cpuload \fR=\fPint
530 If the job is a CPU cycle-eater, attempt to use the specified percentage of
533 .BI cpuchunks \fR=\fPint
534 If the job is a CPU cycle-eater, split the load into cycles of the
535 given time in milliseconds.
537 .BI disk_util \fR=\fPbool
538 Generate disk utilization statistics if the platform supports it. Default: true.
540 While running, \fBfio\fR will display the status of the created jobs. For
544 Threads: 1: [_r] [24.8% done] [ 13509/ 8334 kb/s] [eta 00h:01m:31s]
547 The characters in the first set of brackets denote the current status of each
548 threads. The possible values are:
554 Setup but not started.
560 Initialized, waiting.
563 Running, doing sequential reads.
566 Running, doing random reads.
569 Running, doing sequential writes.
572 Running, doing random writes.
575 Running, doing mixed sequential reads/writes.
578 Running, doing mixed random reads/writes.
581 Running, currently waiting for \fBfsync\fR\|(2).
584 Running, verifying written data.
587 Exited, not reaped by main thread.
590 Exited, thread reaped.
594 The second set of brackets shows the estimated completion percentage of
595 the current group. The third set shows the read and write I/O rate,
596 respectively. Finally, the estimated run time of the job is displayed.
598 When \fBfio\fR completes (or is interrupted by Ctrl-C), it will show data
599 for each thread, each group of threads, and each disk, in that order.
601 Per-thread statistics first show the threads client number, group-id, and
602 error code. The remaining figures are as follows:
606 Number of megabytes of I/O performed.
609 Average data rate (bandwidth).
615 Submission latency minimum, maximum, average and standard deviation. This is
616 the time it took to submit the I/O.
619 Completion latency minimum, maximum, average and standard deviation. This
620 is the time between submission and completion.
623 Bandwidth minimum, maximum, percentage of aggregate bandwidth received, average
624 and standard deviation.
627 CPU usage statistics. Includes user and system time, number of context switches
628 this thread went through and number of major and minor page faults.
631 Distribution of I/O depths. Each depth includes everything less than (or equal)
632 to it, but greater than the previous depth.
635 Number of read/write requests issued, and number of short read/write requests.
638 Distribution of I/O completion latencies. The numbers follow the same pattern
642 The group statistics show:
647 Number of megabytes I/O performed.
650 Aggregate bandwidth of threads in the group.
653 Minimum average bandwidth a thread saw.
656 Maximum average bandwidth a thread saw.
659 Shortest runtime of threads in the group.
662 Longest runtime of threads in the group.
666 Finally, disk statistics are printed with reads first:
671 Number of I/Os performed by all groups.
674 Number of merges in the I/O scheduler.
677 Number of ticks we kept the disk busy.
680 Total time spent in the disk queue.
687 If the \fB\-\-minimal\fR option is given, the results will be printed in a
688 semicolon-delimited format suitable for scripted use. The fields are:
691 .B jobname, groupid, error
695 .B KiB I/O, bandwidth \fR(KiB/s)\fP, runtime \fR(ms)\fP
699 .B min, max, mean, standard deviation
703 .B min, max, mean, standard deviation
707 .B min, max, aggregate percentage of total, mean, standard deviation
713 .B KiB I/O, bandwidth \fR(KiB/s)\fP, runtime \fR(ms)\fP
717 .B min, max, mean, standard deviation
721 .B min, max, mean, standard deviation
725 .B min, max, aggregate percentage of total, mean, standard deviation
731 .B user, system, context switches
734 IO depth distribution:
736 .B <=1, 2, 4, 8, 16, 32, >=64
739 IO latency distribution (ms):
741 .B <=2, 4, 10, 20, 50, 100, 250, 500, 750, 1000, >=2000
748 was written by Jens Axboe <jens.axboe@oracle.com>.
750 This man page was written by Aaron Carroll <aaronc@cse.unsw.edu.au> based
751 on documentation by Jens Axboe.
753 Report bugs to the \fBfio\fR mailing list <fio-devel@kernel.dk>.
756 For further documentation see \fBHOWTO\fR and \fBREADME\fR.
758 Sample jobfiles are available in the \fBexamples\fR directory.
projects / fio.git / blob