[PATCH] Add in-progress io rate

[fio.git] / HOWTO

diff --git a/HOWTO b/HOWTO
index ae19834f84fccd56f86feab0c2a9abf0b99c897f..c17d29e5652a864de9d3ffbf0763f68be6e4a4c1 100644 (file)
--- a/HOWTO
+++ b/HOWTO
@@ -220,10 +220,24 @@ size=siint        The total size of file io for this job. This may describe
 
 bs=siint       The block size used for the io units. Defaults to 4k.
 
+read_bs=siint
+write_bs=siint If the workload is a mixed read-write workload, you can use
+               these options to set seperate block sizes.
+
 bsrange=irange Instead of giving a single block size, specify a range
                and fio will mix the issued io block sizes. The issued
                io unit will always be a multiple of the minimum value
-               given.
+               given (also see bs_unaligned).
+
+read_bsrange=irange
+write_bsrange=irange
+               If the workload is a mixed read-write workload, you can use
+               one of these options to set separate block size ranges for
+               reads and writes.
+
+bs_unaligned   If this option is given, any byte size value within bsrange
+               may be used as a block range. This typically wont work with
+               direct IO, as that normally requires sector alignment.
 
 nrfiles=int    Number of files to use for this job. Defaults to 1.
 
@@ -284,6 +298,13 @@ rwmixwrite=int     How large a percentage of the mix should be writes. If both
                up to 100%, the latter of the two will be used to override
                the first.
 
+norandommap    Normally fio will cover every block of the file when doing
+               random IO. If this option is given, fio will just get a
+               new random offset without looking at past io history. This
+               means that some blocks may not be read or written, and that
+               some blocks may be read/written more than once. This option
+               is mutually exclusive with verify= for that reason.
+
 nice=int       Run the job with the given nice value. See man nice(2).
 
 prio=int       Set the io priority value of this job. Linux limits us to
@@ -433,7 +454,7 @@ cpuchunks=int       If the job is a CPU cycle eater, split the load into
 fio spits out a lot of output. While running, fio will display the
 status of the jobs created. An example of that would be:
 
-Threads running: 1: [_r] [24.79% done] [eta 00h:01m:31s]
+Threads running: 1: [_r] [24.79% done] [ 13509/  8334 kb/s] [eta 00h:01m:31s]
 
 The characters inside the square brackets denote the current status of
 each thread. The possible values (in typical life cycle order) are:
@@ -455,9 +476,9 @@ E           Thread exited, not reaped by main thread yet.
 _              Thread reaped.
 
 The other values are fairly self explanatory - number of threads
-currently running and doing io, and the estimated completion percentage
-and time for the running group. It's impossible to estimate runtime
-of the following groups (if any).
+currently running and doing io, rate of io since last check, and the estimated
+completion percentage and time for the running group. It's impossible to
+estimate runtime of the following groups (if any).
 
 When fio is done (or interrupted by ctrl-c), it will show the data for
 each thread, group of threads, and disks in that order. For each data