From: Sitsofe Wheeler <sitsofe@gmail.com>
To: abhishek koundal <akoundal@gmail.com>
Cc: fio <fio@vger.kernel.org>
Subject: Re: log_offset parameter not logging offset
Date: Sat, 10 Mar 2018 05:48:17 +0000 [thread overview]
Message-ID: <CALjAwxgiQHEzTdwTtnzxiRgYFD37FX5UDig9gLW-mi+X08j8Vg@mail.gmail.com> (raw)
In-Reply-To: <CAKwzdDp=wpc1v0nCwyS_+UigAwY2Fw5SgNusVEk+Rngwz5fRuw@mail.gmail.com>
On 9 March 2018 at 22:59, abhishek koundal <akoundal@gmail.com> wrote:
>
> On 9 March 2018 at 20:11, abhishek koundal <akoundal@gmail.com> wrote:
>> All,
>> Can someone please confirm if my usage is correct as earlier the
>> offset used to be logged by using the log_offset=1 in the files.
>> I am using FIO3.5.
>
> fio --name=global --time_based --size=100% --filename=/dev/nvme0n1
> --runtime=10 --write_iops_log=wr.log --log_avg_msec=1000
> --log_offset=1
>
> Still seeing the issue.
log_avg_msec=1000 tries to average values seen every second which
means some values will become nonsense when it's enabled. There's a
warning at the end of the "Log File Formats" section of the HOWTO
(http://fio.readthedocs.io/en/latest/fio_doc.html#log-file-formats )
but perhaps it needs to be moved elsewhere - would it have been better
under the log_avg_msec section of the HOWTO
(http://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-log-avg-msec
)?
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2018-03-10 5:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 20:11 log_offset parameter not logging offset abhishek koundal
2018-03-09 21:52 ` Sitsofe Wheeler
2018-03-09 22:59 ` abhishek koundal
2018-03-10 5:48 ` Sitsofe Wheeler [this message]
[not found] ` <CAKwzdDoV7RR4FrUgtcpqU70Y8+OJsgeM80PC5mumVp=tB70=LA@mail.gmail.com>
2018-03-10 9:18 ` Sitsofe Wheeler
2018-03-10 10:29 ` abhishek koundal
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=CALjAwxgiQHEzTdwTtnzxiRgYFD37FX5UDig9gLW-mi+X08j8Vg@mail.gmail.com \
--to=sitsofe@gmail.com \
--cc=akoundal@gmail.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.