Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Erwan Velu <erwan@seanodes.com>
To: fio@vger.kernel.org
Subject: Inconsency between cli output and gnuplot
Date: Wed, 19 Nov 2008 17:26:59 +0100	[thread overview]
Message-ID: <49243E53.10309@seanodes.com> (raw)

My 1.23 fio ouput display :

  read : io=32,003MiB, bw=131MiB/s, iops=1,362, runt=250326msec
    slat (usec): min=13, max=145, avg=16.69, stdev= 3.39
    clat (msec): min=31, max=129, avg=46.94, stdev= 7.24

clat output of gnuplot reports units in msec. The clat gnuplot output 
show a msec label on the y axis but trace some usec.

slat cli reports values that doesn't match at all what is viewable from 
gnuplot output. Averagage is said to be 16 on the cli whereas the 
gnuplot trace shows 20 at min.
Max is said to be 145 for slat but displayed at 60 on the gnuplot.
Slat is also said to be usec on the cli but shown as msec on the y axis 
of the gnuplot.

Complete archive showing that could be downloaded at 
http://konilope.linuxeries.org/tmp/localr.tar.bz2

It seems that units may vary from the cli output regarding the range of 
results. I have some case where clat is shown in usec instead of msec. 
Maybe that what confuse the gnuplot output.
Like in :
  write: io=32,003MiB, bw=124MiB/s, iops=1,294, runt=263681msec
    slat (usec): min=12, max=71, avg=15.43, stdev= 2.72
    clat (usec): min=663, max=1,537K, avg=49431.63, stdev=108787.82
    bw (KiB/s) : min=    0, max=171311, per=99.91%, avg=127152.93, 
stdev=21619.46

-- 
Erwan Velu
Pre-Sales Engineer
Seanodes
http://www.seanodes.com
+33 (0)1 41 22 13 83


             reply	other threads:[~2008-11-19 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 16:26 Erwan Velu [this message]
2008-11-27 16:24 ` Inconsency between cli output and gnuplot Erwan Velu
2008-12-09  7:46 ` Jens Axboe
2008-12-09  8:01   ` Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49243E53.10309@seanodes.com \
    --to=erwan@seanodes.com \
    --cc=fio@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox