Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Lucian Grijincu <lucian@fb.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Usage of group reporting
Date: Thu, 05 Apr 2012 16:01:05 -0600	[thread overview]
Message-ID: <4F7E1621.3070009@kernel.dk> (raw)
In-Reply-To: <CBA33231.13A4%lucian@fb.com>

On 2012-04-05 12:29, Lucian Grijincu wrote:
> 
> On 4/5/12 7:42 AM, "Jens Axboe" <axboe@kernel.dk> wrote:
>> Most people don't use the group reporting
> 
> 
> Why do you say that?
> 
> For example I'm trying to find those parameters (direct-io, fadvise,
> number of threads, libaio/mmap/sync, etc.) that give an overall "best
> performance" (whatever that means) on a simulated workload.
> 
> I'm using group reporting, because I want numbers for the entire system,
> not for an individual thread.
> 
> Am I using "fio" wrong or is "fio" mostly used for other kinds of
> benchmarking?

I think there's a confusion of termininology here, it's my fault. So
when I said group reporting, I meant the group status reporting. The
part that shows up at the end of the reporting:

Run status group 0 (all jobs):
   READ: io=2369KB, aggrb=1024KB/s, minb=1024KB/s, maxb=1024KB/s, mint=2313msec, maxt=2313msec

This is what you control with the new_group, forcing fio to group
multiple jobs together for reporting.

You are probably referring to group_reporting, which is used quite
extensively. That is not the one I meant :-)

-- 
Jens Axboe


      reply	other threads:[~2012-04-05 22:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04  6:39 fio problems Danny Kukawka
2012-04-04 19:50 ` Jens Axboe
2012-04-04 20:15   ` Jens Axboe
2012-04-05  9:24     ` Danny Kukawka
2012-04-05 14:45       ` Jens Axboe
2012-04-05  8:51   ` Danny Kukawka
2012-04-05 14:42     ` Jens Axboe
2012-04-05 15:30       ` Danny Kukawka
2012-04-05 15:41         ` Jens Axboe
2012-04-05 18:29       ` Usage of group reporting Lucian Grijincu
2012-04-05 22:01         ` 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=4F7E1621.3070009@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=lucian@fb.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