From: Jens Axboe <axboe@kernel.dk>
To: Peter Xu <xzpeter@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: How to get IOPS when using terse output
Date: Mon, 18 Feb 2013 09:08:29 +0100 [thread overview]
Message-ID: <20130218080829.GC6003@kernel.dk> (raw)
In-Reply-To: <511B6E9C.3000903@gmail.com>
On Wed, Feb 13 2013, Peter Xu wrote:
> Hi, all,
>
> I failed to find IOPS results for read/write under terse mode (with
> --minimal param when invoking fio program), while IOPS does exist in normal
> output without --minimal param.
>
> It seems that I even cannot calculate it out only with the tersed output
> (since I don't know the total number of IO). Then, how should I get IOPS
> results when using terse output?
As Carl mentions, the IOPS are there. But let me make a suggestion to
move over to the json format instead. It's easy to parse by computers
and humans, and new performance metrics can be added without causing
breakage in existing setups. The minimal/csv format is somewhat fragile
for that.
That said, IOPS is there in the minimal output :-)
--
Jens Axboe
next prev parent reply other threads:[~2013-02-18 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 10:44 How to get IOPS when using terse output Peter Xu
2013-02-13 16:36 ` Carl Zwanzig
2013-02-13 17:07 ` Carl Zwanzig
2013-02-18 8:08 ` Jens Axboe [this message]
2013-02-18 8:37 ` Georg Schönberger
2013-02-18 8:45 ` 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=20130218080829.GC6003@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=xzpeter@gmail.com \
/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