Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Gavin Martin <gavin_martin@xyratex.com>
Cc: fio@vger.kernel.org
Subject: Re: Output logs and keep command line display
Date: Thu, 31 Jan 2013 15:02:23 +0100	[thread overview]
Message-ID: <20130131140223.GI8800@kernel.dk> (raw)
In-Reply-To: <CANUChTxynLg7p5kK1vex9965qvYxyFagzk8QAtbh-2-=_Mdxhg@mail.gmail.com>

On Thu, Jan 31 2013, Gavin Martin wrote:
> Hi,
> 
> Not sure if I am missing a special argument somewhere, but I like the
> command line display we get from Fio when it runs showing the type of
> workload and job descriptions and percentage complete, etc.  Is it
> possible to get the outputs that you get when using the --minimal
> argument (in JSON, CSV formats) whilst still keeping the command line
> display.
> 
> Having this would make it similar to Iometer, not in a graphical
> sense, but in a way that you can see exactly what is occurring (and if
> it has halted or crashed) whilst still having logs that could be
> charted or plotted into reports.  Especially useful for extended test
> runs (over several hours!)

--eta=always

should do the trick for you, if I understand your request correctly. I
suppose for that to be useful, you want to redirect the csv/json output
to a file as well?

Might be useful to have the behaviour of:

--output-format=type [file]

where if 'file' is given, then output goes to that file in the specified
format, and fio still uses stdout for the ETA output.

-- 
Jens Axboe


  reply	other threads:[~2013-01-31 14:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 13:44 Output logs and keep command line display Gavin Martin
2013-01-31 14:02 ` Jens Axboe [this message]
2013-01-31 14:08   ` Jens Axboe
2013-01-31 14:12     ` Gavin Martin
2013-01-31 14:24       ` Jens Axboe
2013-02-12 10:41         ` Gavin Martin
2013-02-22 12:07           ` Jens Axboe
2013-02-22 19:11             ` Carl Zwanzig
2013-02-22 19:32               ` 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=20130131140223.GI8800@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=gavin_martin@xyratex.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