X-Git-Url: https://git.kernel.dk/?p=fio.git;a=blobdiff_plain;f=HOWTO;h=bc23052d61e568434b23488c150e525d0ee48407;hp=1390f386adca52a4c4ccdec3d60c6c730b9392e5;hb=7c353ceb3257b132f4c98326046b42201e070731;hpb=afad68f778a764cbe57d4a5d54cbea32444aaa45 diff --git a/HOWTO b/HOWTO index 1390f386..bc23052d 100644 --- a/HOWTO +++ b/HOWTO @@ -112,7 +112,7 @@ section residing above it. If the first character in a line is a ';' or a '#', the entire line is discarded as a comment. So let's look at a really simple job file that defines two processes, each -randomly reading from a 128MiB file. +randomly reading from a 128MB file. ; -- start job file -- [global] @@ -150,9 +150,9 @@ numjobs=4 Here we have no global section, as we only have one job defined anyway. We want to use async io here, with a depth of 4 for each file. We also -increased the buffer size used to 32KiB and define numjobs to 4 to +increased the buffer size used to 32KB and define numjobs to 4 to fork 4 identical jobs. The result is 4 processes each randomly writing -to their own 64MiB file. Instead of using the above job file, you could +to their own 64MB file. Instead of using the above job file, you could have given the parameters on the command line. For this case, you would specify: @@ -197,21 +197,21 @@ Some parameters take an option of a given type, such as an integer or a string. The following types are used: str String. This is a sequence of alpha characters. -time Integer with possible time postfix. In seconds unless otherwise +time Integer with possible time suffix. In seconds unless otherwise specified, use eg 10m for 10 minutes. Accepts s/m/h for seconds, minutes, and hours. -int SI integer. A whole number value, which may contain a postfix - describing the base of the number. Accepted postfixes are k/m/g, - meaning kilo, mega, and giga. So if you want to specify 4096, - you could either write out '4096' or just give 4k. The postfixes - signify base 2 values, so 1024 is 1k and 1024k is 1m and so on. - If the option accepts an upper and lower range, use a colon ':' - or minus '-' to separate such values. May also include a prefix - to indicate numbers base. If 0x is used, the number is assumed to - be hexadecimal. See irange. +int SI integer. A whole number value, which may contain a suffix + describing the base of the number. Accepted suffixes are k/m/g/t/p, + meaning kilo, mega, giga, tera, and peta. The suffix is not case + sensitive. So if you want to specify 4096, you could either write + out '4096' or just give 4k. The suffixes signify base 2 values, so + 1024 is 1k and 1024k is 1m and so on. If the option accepts an upper + and lower range, use a colon ':' or minus '-' to separate such values. + May also include a prefix to indicate numbers base. If 0x is used, + the number is assumed to be hexadecimal. See irange. bool Boolean. Usually parsed as an integer, however only defined for true and false (1 and 0). -irange Integer range with postfix. Allows value range to be given, such +irange Integer range with suffix. Allows value range to be given, such as 1024-4096. A colon may also be used as the separator, eg 1k:4k. If the option allows two sets of ranges, they can be specified with a ',' or '/' delimiter: 1k-4k/8k-32k. Also see @@ -243,8 +243,11 @@ filename=str Fio normally makes up a filename based on the job name, can specify a number of files by separating the names with a ':' colon. So if you wanted a job to open /dev/sda and /dev/sdb as the two working files, you would use - filename=/dev/sda:/dev/sdb. '-' is a reserved name, meaning - stdin or stdout. Which of the two depends on the read/write + filename=/dev/sda:/dev/sdb. If the wanted filename does need to + include a colon, then escape that with a '\' character. For + instance, if the filename is "/dev/dsk/foo@3,0:c", then you would + use filename="/dev/dsk/foo@3,0\:c". '-' is a reserved name, + meaning stdin or stdout. Which of the two depends on the read/write direction set. opendir=str Tell fio to recursively add any file it can find in this @@ -290,6 +293,11 @@ rw=str Type of io pattern. Accepted values are: IO's, instead of for every IO. Use rw=randread:8 to specify that. +kb_base=int The base unit for a kilobyte. The defacto base is 2^10, 1024. + Storage manufacturers like to use 10^3 or 1000 as a base + ten unit instead, for obvious reasons. Allow values are + 1024 or 1000, with 1024 being the default. + randrepeat=bool For random IO workloads, seed the generator in a predictable way so that results are repeatable across repetitions. @@ -314,7 +322,8 @@ filesize=int Individual file sizes. May be a range, in which case fio fill_device=bool Sets size to something really large and waits for ENOSPC (no space left on device) as the terminating condition. Only makes - sense with sequential write. + sense with sequential write. For a read workload, the mount + point will be filled first then IO started on the result. blocksize=int bs=int The block size used for the io units. Defaults to 4k. Values @@ -529,6 +538,9 @@ fsync=int If writing to a file, issue a sync of the dirty data not sync the file. The exception is the sg io engine, which synchronizes the disk cache anyway. +fsyncdata=int Like fsync= but uses fdatasync() to only sync data and not + metadata blocks. + overwrite=bool If true, writes to a file will always overwrite existing data. If the file doesn't already exist, it will be created before the write phase begins. If the file exists @@ -546,7 +558,9 @@ rwmixread=int How large a percentage of the mix should be reads. rwmixwrite=int How large a percentage of the mix should be writes. If both rwmixread and rwmixwrite is given and the values do not add up to 100%, the latter of the two will be used to override - the first. + the first. This may interfere with a given rate setting, + if fio is asked to limit reads or writes to a certain rate. + If that is the case, then the distribution may be skewed. norandommap Normally fio will cover every block of the file when doing random IO. If this option is given, fio will just get a @@ -588,19 +602,29 @@ thinktime_blocks defaults to 1 which will make fio wait 'thinktime' usecs after every block. -rate=int Cap the bandwidth used by this job to this number of KiB/sec. +rate=int Cap the bandwidth used by this job. The number is in bytes/sec, + the normal suffix rules apply. You can use rate=500k to limit + reads and writes to 500k each, or you can specify read and + writes separately. Using rate=1m,500k would limit reads to + 1MB/sec and writes to 500KB/sec. Capping only reads or + writes can be done with rate=,500k or rate=500k,. The former + will only limit writes (to 500KB/sec), the latter will only + limit reads. ratemin=int Tell fio to do whatever it can to maintain at least this bandwidth. Failing to meet this requirement, will cause - the job to exit. + the job to exit. The same format as rate is used for + read vs write separation. rate_iops=int Cap the bandwidth to this number of IOPS. Basically the same as rate, just specified independently of bandwidth. If the job is given a block size range instead of a fixed value, - the smallest block size is used as the metric. + the smallest block size is used as the metric. The same format + as rate is used for read vs write seperation. rate_iops_min=int If fio doesn't meet this rate of IO, it will cause - the job to exit. + the job to exit. The same format as rate is used for read vs + write seperation. ratecycle=int Average bandwidth for 'rate' and 'ratemin' over this number of milliseconds. @@ -675,7 +699,7 @@ mem=str Fio can use various types of memory as the io unit buffer. that for shmhuge and mmaphuge to work, the system must have free huge pages allocated. This can normally be checked and set by reading/writing /proc/sys/vm/nr_hugepages on a - Linux system. Fio assumes a huge page is 4MiB in size. So + Linux system. Fio assumes a huge page is 4MB in size. So to calculate the number of huge pages you need for a given job file, add up the io depth of all jobs (normally one unless iodepth= is used) and multiply by the maximum bs set. Then @@ -688,9 +712,18 @@ mem=str Fio can use various types of memory as the io unit buffer. location should point there. So if it's mounted in /huge, you would use mem=mmaphuge:/huge/somefile. +iomem_align=int This indiciates the memory alignment of the IO memory buffers. + Note that the given alignment is applied to the first IO unit + buffer, if using iodepth the alignment of the following buffers + are given by the bs used. In other words, if using a bs that is + a multiple of the page sized in the system, all buffers will + be aligned to this value. If using a bs that is not page + aligned, the alignment of subsequent IO memory buffers is the + sum of the iomem_align and bs used. + hugepage-size=int Defines the size of a huge page. Must at least be equal - to the system setting, see /proc/meminfo. Defaults to 4MiB. + to the system setting, see /proc/meminfo. Defaults to 4MB. Should probably always be a multiple of megabytes, so using hugepage-size=Xm is the preferred way to set this to avoid setting a non-pow-2 bad value. @@ -714,7 +747,12 @@ create_on_open=bool Don't pre-setup the files for IO, just create open() when it's time to do IO to that file. pre_read=bool If this is given, files will be pre-read into memory before - starting the given IO operation. + starting the given IO operation. This will also clear + the 'invalidate' flag, since it is pointless to pre-read + and then drop the cache. This will only work for IO engines + that are seekable, since they allow you to read the same data + multiple times. Thus it will not work on eg network or splice + IO. unlink=bool Unlink the job files when done. Not the default, as repeated runs of that job would then waste time recreating the file @@ -756,6 +794,8 @@ verify=str If writing to a file, fio can verify the file contents sha256 Use sha256 as the checksum function. + sha1 Use optimized sha1 as the checksum function. + meta Write extra information about each io (timestamp, block number etc.). The block number is verified. @@ -797,6 +837,19 @@ verify_fatal=bool Normally fio will keep checking the entire contents before quitting on a block verification failure. If this option is set, fio will exit the job on the first observed failure. + +verify_async=int Fio will normally verify IO inline from the submitting + thread. This option takes an integer describing how many + async offload threads to create for IO verification instead, + causing fio to offload the duty of verifying IO contents + to one or more separate threads. If using this offload + option, even sync IO engines can benefit from using an + iodepth setting higher than 1, as it allows them to have + IO in flight while verifies are running. + +verify_async_cpus=str Tell fio to set the given CPU affinity on the + async IO verification threads. See cpus_allowed for the + format used. stonewall Wait for preceeding jobs in the job file to exit, before starting this one. Can be used to insert serialization @@ -913,6 +966,14 @@ gtod_cpu=int Sometimes it's cheaper to dedicate a single thread of for doing these time calls will be excluded from other uses. Fio will manually clear it from the CPU mask of other jobs. +continue_on_error=bool Normally fio will exit the job on the first observed + failure. If this option is set, fio will continue the job when + there is a 'non-fatal error' (EIO or EILSEQ) until the runtime + is exceeded or the I/O size specified is completed. If this + option is used, there are two more stats that are appended, + the total error count and the first error. The error field + given in the stats is the first error that was hit during the + run. 6.0 Interpreting the output @@ -931,6 +992,7 @@ Idle Run P Thread setup, but not started. C Thread created. I Thread initialized, waiting. + p Thread running pre-reading file(s). R Running, doing sequential reads. r Running, doing random reads. W Running, doing sequential writes. @@ -953,10 +1015,10 @@ each thread, group of threads, and disks in that order. For each data direction, the output looks like: Client1 (g=0): err= 0: - write: io= 32MiB, bw= 666KiB/s, runt= 50320msec + write: io= 32MB, bw= 666KB/s, runt= 50320msec slat (msec): min= 0, max= 136, avg= 0.03, stdev= 1.92 clat (msec): min= 0, max= 631, avg=48.50, stdev=86.82 - bw (KiB/s) : min= 0, max= 1196, per=51.00%, avg=664.02, stdev=681.68 + bw (KB/s) : min= 0, max= 1196, per=51.00%, avg=664.02, stdev=681.68 cpu : usr=1.49%, sys=0.25%, ctx=7969, majf=0, minf=17 IO depths : 1=0.1%, 2=0.3%, 4=0.5%, 8=99.0%, 16=0.0%, 32=0.0%, >32=0.0% submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% @@ -1016,8 +1078,8 @@ After each client has been listed, the group statistics are printed. They will look like this: Run status group 0 (all jobs): - READ: io=64MiB, aggrb=22178, minb=11355, maxb=11814, mint=2840msec, maxt=2955msec - WRITE: io=64MiB, aggrb=1302, minb=666, maxb=669, mint=50093msec, maxt=50320msec + READ: io=64MB, aggrb=22178, minb=11355, maxb=11814, mint=2840msec, maxt=2955msec + WRITE: io=64MB, aggrb=1302, minb=666, maxb=669, mint=50093msec, maxt=50320msec For each data direction, it prints: @@ -1060,12 +1122,12 @@ Split up, the format is as follows: jobname, groupid, error READ status: - KiB IO, bandwidth (KiB/sec), runtime (msec) + KB IO, bandwidth (KB/sec), runtime (msec) Submission latency: min, max, mean, deviation Completion latency: min, max, mean, deviation Bw: min, max, aggregate percentage of total, mean, deviation WRITE status: - KiB IO, bandwidth (KiB/sec), runtime (msec) + KB IO, bandwidth (KB/sec), runtime (msec) Submission latency: min, max, mean, deviation Completion latency: min, max, mean, deviation Bw: min, max, aggregate percentage of total, mean, deviation