summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJens Axboe <axboe@suse.de>2005-12-07 20:29:00 +0100
committerJens Axboe <axboe@suse.de>2005-12-07 20:29:00 +0100
commit409a8614a46da061e373963ae52d3a60a5b63a81 (patch)
treec97b8c4d681482da3016b3eb515e4f9de42a57f3
parente20d30479fd0ea6807b9636bc49dc49e36e5b29f (diff)
[PATCH] fio: expand latency numbers for sync io.
-rw-r--r--README.fio10
1 files changed, 8 insertions, 2 deletions
diff --git a/README.fio b/README.fio
index 66022aa..f3aad7d 100644
--- a/README.fio
+++ b/README.fio
@@ -118,6 +118,8 @@ Threads now running: 2 : [ww] [5.73% done]
The characters inside the square brackets denote the current status of
each thread. The possible values (in typical life cycle order) are:
+Idle Run
+---- ---
P Thread setup, but not started.
C Thread created and running, but not doing anything yet
R Running, doing sequential reads.
@@ -151,9 +153,13 @@ bw= Average bandwidth rate
runt= The runtime of that thread
slat= Submission latency (avg being the average, dev being the
standard deviation). This is the time it took to submit
- the io.
+ the io. For sync io, the slat is really the completion
+ latency, since queue/complete is one operation there.
clat= Completion latency. Same names as slat, this denotes the
- time from submission to completion of the io pieces.
+ time from submission to completion of the io pieces. For
+ sync io, clat will usually be equal (or very close) to 0,
+ as the time from submit to complete is basically just
+ CPU time (io has already been done, see slat explanation).
bw= Bandwidth. Same names as the xlat stats, but also includes
an approximate percentage of total aggregate bandwidth
this thread received in this group. This last value is