I don't really use the terse output myself, but the terse labels from the HOWTO include separate values for read and writes. However, the json output will only include 'mixed' results when --unified_rw_reporting is set. Also, the terse reported clat percentiles seem to be different than what is indicated in --percentiles option in json. So with a script generating terse results from the json data, the results wouldn't be strictly identical, but with headers included using scripts could be flexible. For what it's worth, I couple of months ago, I created a python3 module and class which reads fio v3+ and can produce a normal "like" result and a 'terse' like result with headers, along with some methods to interrogate overall iops, mips, etc (for use in a scripts). I later discovered I could list all three (json,normal and terse) in the output option, and so mostly use that in scripts to have "human" readable and json script readable. So I haven't really completely tested all this code. I mostly use it to check the iops, mibs, latencies in scripts, and then strip out the "normal" output for display. However, it also include 'terse' like results. I've done some cursory testing. I've added arguments to the modules main section to turn into a script, and it may be a starting point. It would also need help test the corner cases, since there are so many options within Fio. I'm working on some other things which have priority at the moment, but anyone is welcome to run with it if you need something quickly. I put a starting proposal script call fioJasonInterpreter.py at https://github.com/shimrot/fio/tree/json_output_conversion_script/tools . I imagine a script for public consumption might want a different name. Thanks Kris Davis -----Original Message----- From: fio-owner@xxxxxxxxxxxxxxx [mailto:fio-owner@xxxxxxxxxxxxxxx] On Behalf Of Jens Axboe Sent: Wednesday, July 25, 2018 9:48 AM To: Friendy.Su@xxxxxxxx; elliott@xxxxxxx; haghdoost@xxxxxxxxx; sitsofe@xxxxxxxxx Cc: fio@xxxxxxxxxxxxxxx; No.Tanaka@xxxxxxxx; Hajime.Tomura@xxxxxxxx Subject: Re: [PATCH] idle-prof: append output cpu idleness data to terse log On 7/25/18 1:47 AM, Friendy.Su@xxxxxxxx wrote: > Many people are still used to process, plot data by excel. As a format which can be opened directly by excel, terse is welcome. > Exactly terse log has already trailing the normal/json log, improving it inside fio looks a redundant work. Instead, how about provide a script to convert json to terse under tools/?Meanwhile, in HOWTO doc, tell user to use that script to get a 'perfect' terse. Yeah, I was thinking the exact same thing while mulling over this yesterday. I think that'd be great, and would allow us to kill the terse code in fio proper. -- Jens Axboe ��.n��������+%������w��{.n�������^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
