From: Steve Wise <swise@opengridcomputing.com>
To: Jens Axboe <axboe@kernel.dk>, 'Vasily Tarasov' <tarasov@vasily.name>
Cc: fio@vger.kernel.org
Subject: Re: fio terse output for WRITE not working.
Date: Fri, 22 Aug 2014 18:23:53 -0500 [thread overview]
Message-ID: <53F7D109.8070503@opengridcomputing.com> (raw)
In-Reply-To: <53F7C3BE.8070204@kernel.dk>
On 8/22/2014 5:27 PM, Jens Axboe wrote:
> On 2014-08-15 10:31, Steve Wise wrote:
>>
>>
>>> -----Original Message-----
>>> From: fio-owner@vger.kernel.org [mailto:fio-owner@vger.kernel.org]
>>> On Behalf Of Vasily
>>> Tarasov
>>> Sent: Friday, August 15, 2014 10:29 AM
>>> To: Steve Wise
>>> Cc: fio@vger.kernel.org
>>> Subject: Re: fio terse output for WRITE not working.
>>>
>>> Hi Steve,
>>>
>>> I found terse/minimal output to be quite unstable and inconsistent in
>>> fio. So, as suggested by Jens, I switched to json output
>>> (--output-format=json). It seems to be more stable and is also quite
>>> easy to parse.
>>>
>>> Perhaps that's an option for you.
>>>
>>> Vasily
>>
>> I'll check out json. Thanks Vasily.
>
> json is vastly superior - easy to parse by both humans and computers.
> That said, the terse format should of course work. I ran a quick test
> just now, and I don't see anything wrong?
>
See my original posting on this. The write terse output only has zeros
for the over bandwidth in the first few fields of the record. read works
fine for me though.
next prev parent reply other threads:[~2014-08-22 23:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 18:49 fio terse output for WRITE not working Steve Wise
2014-08-15 14:35 ` Steve Wise
2014-08-15 15:28 ` Vasily Tarasov
2014-08-15 15:31 ` Steve Wise
2014-08-22 22:27 ` Jens Axboe
2014-08-22 23:23 ` Steve Wise [this message]
2014-08-22 23:34 ` Jens Axboe
2014-08-22 23:46 ` Steve Wise
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=53F7D109.8070503@opengridcomputing.com \
--to=swise@opengridcomputing.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=tarasov@vasily.name \
/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