From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <53F7C3BE.8070204@kernel.dk> Date: Fri, 22 Aug 2014 17:27:10 -0500 From: Jens Axboe MIME-Version: 1.0 Subject: Re: fio terse output for WRITE not working. References: <005e01cfb339$774e4640$65ead2c0$@opengridcomputing.com> <002d01cfb896$19657b40$4c3071c0$@opengridcomputing.com> <003501cfb89e$07474ad0$15d5e070$@opengridcomputing.com> In-Reply-To: <003501cfb89e$07474ad0$15d5e070$@opengridcomputing.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit To: Steve Wise , 'Vasily Tarasov' Cc: fio@vger.kernel.org List-ID: 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? -- Jens Axboe