On Thu, Aug 16, 2012 at 11:22 PM, Jens Axboe <axboe@xxxxxxxxx> wrote:
> 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.
Okay, thanks, that did the trick.
I suggest adding a sentence about that under the "log_avg_msec" entry
in the documentation. Currently it reads:
log_avg_msec=int
By default, fio will log an entry in the iops, latency, or bw
log for every IO that completes. When writing to the disk log,
that can quickly grow to a very large size. Setting this option
makes fio average the each log entry over the specified period
of time, reducing the resolution of the log. Defaults to 0.
I suggest adding something like:
In order to log bw and IOPS with other than the default 500msec
averaging time,
it will also be necessary to set bwavgtime and iopsavgtime.
--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
