All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: John Williams <jwilliams4200@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: log_avg_msec does not work for BW or IOPS logs
Date: Fri, 17 Aug 2012 08:22:26 +0200	[thread overview]
Message-ID: <502DE322.6040708@kernel.dk> (raw)
In-Reply-To: <CAJBj3vfcQYnAEtJkh7FKYGAaePtpGbkgVKDOJeBwQcz8WsgNRQ@mail.gmail.com>

On 08/15/2012 05:55 AM, John Williams wrote:
> I'm calling fio v2.0.8 from the command line in linux, and I wanted to
> set the averaging time for the log data to 200msec. Here is the
> command line I used:
> 
> fio --name=SeqWrite --readwrite=write --bs=128K --iodepth=1
> --ioengine=libaio --direct=1 --invalidate=1 --output=/tmp/fio_output
> --write_bw_log=bw_seq128K --write_lat_log=lat_seq128K
> --write_iops_log=iops_seq128K --log_avg_msec=200 --randrepeat=0
> --norandommap --offset=0 --size=128035676160 --filename=/dev/sdaa
> 
> But when I examined the logs that fio produced, the BW and the IOPS
> logs had the default 500msec resolution. But the latency logs had my
> requested 200msec resolution.
> 
> Is this an fio bug, or did I misunderstand something?

This is a bit confusing. Basically there are two time settings. One is
for the statistics averaging, the other is when to make an entry in a
log (if that is set). The default for IOPS and BW is to average over
500msec, regardless of logging times. So you would need to add
--iopsavgtime=200 --bwavgtime=200 as well to get the desired behaviour.

-- 
Jens Axboe


  reply	other threads:[~2012-08-17  6:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15  3:55 log_avg_msec does not work for BW or IOPS logs John Williams
2012-08-17  6:22 ` Jens Axboe [this message]
2012-08-17  7:24   ` John Williams

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=502DE322.6040708@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=jwilliams4200@gmail.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 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.