X-Git-Url: https://git.kernel.dk/?p=fio.git;a=blobdiff_plain;f=HOWTO;h=eb2ed25403cb8dfe2ae96e8a93d5e99aa98c8b39;hp=2335a07ffc142366cbf652d8caffca542ea9f2ab;hb=4db089f5dd8a00eb4efdc8694735ef2cc3843998;hpb=6aca9b3d1042bef94958ebee0656755a91695f4b diff --git a/HOWTO b/HOWTO index 2335a07f..eb2ed254 100644 --- a/HOWTO +++ b/HOWTO @@ -709,6 +709,13 @@ offset_increment=int If this is provided, then the real offset becomes which are intended to operate on a file in parallel in disjoint segments, with even spacing between the starting points. +number_ios=int Fio will normally perform IOs until it has exhausted the size + of the region set by size=, or if it exhaust the allocated + time (or hits an error condition). With this setting, the + range/size can be set independently of the number of IOs to + perform. When fio reaches this number, it will exit normally + and report status. + fsync=int If writing to a file, issue a sync of the dirty data for every number of blocks given. For example, if you give 32 as a parameter, fio will sync the file for every 32 @@ -863,11 +870,11 @@ 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 same format - as rate is used for read vs write seperation. + as rate is used for read vs write separation. rate_iops_min=int If fio doesn't meet this rate of IO, it will cause the job to exit. The same format as rate is used for read vs - write seperation. + write separation. max_latency=int If set, fio will exit the job if it exceeds this maximum latency. It will exit with an ETIME error. @@ -1144,9 +1151,6 @@ verify_backlog=int Fio will normally verify the written contents of a holding this meta data. If this option is enabled, fio will write only N blocks before verifying these blocks. - will verify the previously written blocks before continuing - to write new ones. - verify_backlog_batch=int Control how many blocks fio will verify if verify_backlog is set. If not set, will default to the value of verify_backlog (meaning the entire queue @@ -1156,7 +1160,7 @@ verify_backlog_batch=int Control how many blocks fio will verify blocks will be verified more than once. stonewall -wait_for_previous Wait for preceeding jobs in the job file to exit, before +wait_for_previous Wait for preceding jobs in the job file to exit, before starting this one. Can be used to insert serialization points in the job file. A stone wall also implies starting a new reporting group. @@ -1212,7 +1216,7 @@ replay_no_stall=int When replaying I/O with read_iolog the default behavior replay_redirect=str While replaying I/O patterns using read_iolog the default behavior is to replay the IOPS onto the major/minor device that each IOP was recorded from. This is sometimes - undesireable because on a different machine those major/minor + undesirable because on a different machine those major/minor numbers can map to a different device. Changing hardware on the same system can also result in a different major/minor mapping. Replay_redirect causes all IOPS to be replayed onto @@ -1245,9 +1249,6 @@ write_lat_log=str Same as write_bw_log, except that this option stores io and foo_lat.log. This helps fio_generate_plot fine the logs automatically. -write_bw_log=str If given, write an IOPS log of the jobs in this job - file. See write_bw_log. - write_iops_log=str Same as write_bw_log, but writes IOPS. If no filename is given with this option, the default filename of "jobname_type.log" is used. Even if the filename is given, @@ -1683,9 +1684,9 @@ Split up, the format is as follows: Read merges, write merges, Read ticks, write ticks, Time spent in queue, disk utilization percentage - Additional Info (dependant on continue_on_error, default off): total # errors, first error code + Additional Info (dependent on continue_on_error, default off): total # errors, first error code - Additional Info (dependant on description being set): Text description + Additional Info (dependent on description being set): Text description Completion latency percentiles can be a grouping of up to 20 sets, so for the terse output fio writes all of them. Each field will look like this: