All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Kurt Dorsey <Kurt_Dorsey@Dell.com>, fio@vger.kernel.org
Subject: Re: Feature Request, Job Info inserted into json output
Date: Tue, 15 Dec 2015 10:32:18 -0700	[thread overview]
Message-ID: <56704EA2.8000506@kernel.dk> (raw)
In-Reply-To: <5669B1A9.7000006@kernel.dk>

On 12/10/2015 10:08 AM, Jens Axboe wrote:
> On 12/09/2015 09:10 AM, Kurt Dorsey wrote:
>> Hi All,
>>
>> I have a feature request.   One of the things that is missing (in my
>> opinion) from the json output is the actual fio job configuration.
>>
>> In the current state it outputs a json file with all the output from the
>> jobs run.  One addition that would make it very helpful for parsing and
>> comparing data (especially historical data  or data run by another
>> engineer) is to have the actual job file as a key inside the json
>> output.  This could be something as simple as just putting the parsed
>> command line argument in
>>
>> fio --ioengine=libaio --buffered=0 --norandommap --log_avg_msec=10000 --
>> direct=1 --ba=4k --ramp_time=0 --runtime=1800 --time_based --
>> filename=/dev/sdg --name=8K_RR_QD1 --name=8K_RR_QD1 --bs=8k --
>> rw=randread --iodepth=1 --write_iops_log=./8K_RR_qd1_
>>
>> Or even better would be a dictionary inside the json with every
>> configuration parameter verbosely printed (like the below "jobinfo")
>>
>>
>>
>> {
>>    "fio version" : "fio-2.1.10",
>>    "jobs" : [
>>      {
>>        "jobname" : "8K_Random_Read",
>>        "jobinfo" :{
>>          "ioengine" : "libaio"
>>          "buffered" : 0
>>          "norandommap" : 1
>>          "log_avg_msec" : 10000
>>          "direct" : 1
>>          "ba" : 4k
>>          "ramp_time" : 0
>>          "runtime" :1800
>>          "time_based" : 1
>>          "filename" : "/dev/sdc"
>>          "name" : "8K_Random_Read"
>>          "bs" : "8K"
>>          "rw" : "randread"
>>          "iodepth" : 1
>>        }
>>        "groupid" : 0,
>>        "error" : 0,
>>        "read" : {
>>
>>
>> I understand it would add size to the output but I think it would really
>> help.
>
> That would be very useful, you're not the first to bring it up. I'll be
> happy to take patches to add this feature.

Can you try current -git? There's support for this now.

-- 
Jens Axboe



      reply	other threads:[~2015-12-15 17:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 16:10 Feature Request, Job Info inserted into json output Kurt Dorsey
2015-12-10 17:08 ` Jens Axboe
2015-12-15 17:32   ` Jens Axboe [this message]

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=56704EA2.8000506@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Kurt_Dorsey@Dell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.