Flexible I/O Tester development
 help / color / mirror / Atom feed
* [PATCH] HOWTO: emphasize units in --minimal mode: latency in usec, bw in KB/s
@ 2012-04-03  0:02 Lucian Adrian Grijincu
  2012-04-03 20:40 ` Jens Axboe
  0 siblings, 1 reply; 2+ messages in thread
From: Lucian Adrian Grijincu @ 2012-04-03  0:02 UTC (permalink / raw)
  To: fio; +Cc: Lucian Adrian Grijincu

It wasn't clear what unit were used in --minimal mode.

Signed-off-by: Lucian Adrian Grijincu <lucian@fb.com>
---
 HOWTO |   19 ++++++++++---------
 1 file changed, 10 insertions(+), 9 deletions(-)

diff --git a/HOWTO b/HOWTO
index 662689e..c47997f 100644
--- a/HOWTO
+++ b/HOWTO
@@ -1382,7 +1382,8 @@ runt=		The runtime of that thread
 		latency, since queue/complete is one operation there. This
 		value can be in milliseconds or microseconds, fio will choose
 		the most appropriate base and print that. In the example
-		above, milliseconds is the best scale.
+		above, milliseconds is the best scale. Note: in --minimal mode
+		latencies are always expressed in microseconds.
 	clat=	Completion latency. Same names as slat, this denotes the
 		time from submission to completion of the io pieces. For
 		sync io, clat will usually be equal (or very close) to 0,
@@ -1470,18 +1471,18 @@ Split up, the format is as follows:
 	terse version, fio version, jobname, groupid, error
 	READ status:
 		Total IO (KB), bandwidth (KB/sec), IOPS, runtime (msec)
-		Submission latency: min, max, mean, deviation (usec)
-		Completion latency: min, max, mean, deviation (usec)
+		Submission latency (usec): min, max, mean, deviation (usec)
+		Completion latency (usec): min, max, mean, deviation (usec)
 		Completion latency percentiles: 20 fields (see below)
-		Total latency: min, max, mean, deviation (usec)
-		Bw: min, max, aggregate percentage of total, mean, deviation
+		Total latency (usec): min, max, mean, deviation (usec)
+		Bw (KB/s): min, max, aggregate percentage of total, mean, deviation
 	WRITE status:
 		Total IO (KB), bandwidth (KB/sec), IOPS, runtime (msec)
-		Submission latency: min, max, mean, deviation (usec)
-		Completion latency: min, max, mean, deviation (usec)
+		Submission latency (usec): min, max, mean, deviation (usec)
+		Completion latency (usec): min, max, mean, deviation (usec)
 		Completion latency percentiles: 20 fields (see below)
-		Total latency: min, max, mean, deviation (usec)
-		Bw: min, max, aggregate percentage of total, mean, deviation
+		Total latency (usec): min, max, mean, deviation (usec)
+		Bw (KB/s): min, max, aggregate percentage of total, mean, deviation
 	CPU usage: user, system, context switches, major faults, minor faults
 	IO depths: <=1, 2, 4, 8, 16, 32, >=64
 	IO latencies microseconds: <=2, 4, 10, 20, 50, 100, 250, 500, 750, 1000
-- 
1.7.9.5


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] HOWTO: emphasize units in --minimal mode: latency in usec, bw in KB/s
  2012-04-03  0:02 [PATCH] HOWTO: emphasize units in --minimal mode: latency in usec, bw in KB/s Lucian Adrian Grijincu
@ 2012-04-03 20:40 ` Jens Axboe
  0 siblings, 0 replies; 2+ messages in thread
From: Jens Axboe @ 2012-04-03 20:40 UTC (permalink / raw)
  To: Lucian Adrian Grijincu; +Cc: fio

On 2012-04-02 18:02, Lucian Adrian Grijincu wrote:
> It wasn't clear what unit were used in --minimal mode.

Thanks, applied the bit that was missing.

-- 
Jens Axboe


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-04-03 20:40 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-04-03  0:02 [PATCH] HOWTO: emphasize units in --minimal mode: latency in usec, bw in KB/s Lucian Adrian Grijincu
2012-04-03 20:40 ` Jens Axboe

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox