From 0d0df855e689a9e494c165a2f956f3ce88d07a9f Mon Sep 17 00:00:00 2001 From: Mohamad Chaarawi Date: Wed, 18 Sep 2019 19:50:43 +0000 Subject: [PATCH] update user guide with IOPS and latency numbers for each iteration. Signed-off-by: Mohamad Chaarawi --- doc/USER_GUIDE | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/doc/USER_GUIDE b/doc/USER_GUIDE index b8888b9..62a6802 100755 --- a/doc/USER_GUIDE +++ b/doc/USER_GUIDE @@ -550,6 +550,17 @@ HOW DOES IOR CALCULATE PERFORMANCE? operations (-g), the sum of the open, transfer, and close times may not equal the elapsed time from the first open to the last close. + After each iteration (-i) IOR reports performance for that iteration, and + those numbers include: + + - Bandwidth (described above) + + - IOPS: I/O rate (operations per second) achieved by all tasks given the total + time spent in reading and writing the data. + + - Latency: computed by taking the average latency of all I/O operations from a + single task. If ior is run with multiple tasks, then the latency reported is + the minimum that was computed between all tasks. HOW DO I ACCESS MULTIPLE FILE SYSTEMS IN IOR?