From: Kyle Hailey <kyle.hailey@delphix.com>
To: Mike Ryan <mike.ryan@inktank.com>
Cc: Jens Axboe <axboe@kernel.dk>, fio@vger.kernel.org
Subject: Re: generating latency logs
Date: Tue, 7 Aug 2012 22:26:53 -0700 [thread overview]
Message-ID: <CACiQ3FBAo7PDL9hcZTWtJBAJA40BcdM9XKX87x=fv4PqODu0-g@mail.gmail.com> (raw)
In-Reply-To: <20120807144721.GF12248@splice>
very cool, so if I add the changes to init.c and run
fio --latency-log --output test.job
I get extra four files
-rw-r--r-- 1 me staff 14937 Aug 8 2012 fiotest_lat.log
-rw-r--r-- 1 me staff 0 Aug 8 2012 fiotest_slat.log
-rw-r--r-- 1 me staff 14932 Aug 8 2012 fiotest_clat.log
-rw-r--r-- 1 me staff 4194304 Aug 8 2012 fiotest.1.0
What's the format?
$ more fiotest_lat*
1, 19, 1, 4096
1, 18, 1, 4096
1, 8, 1, 4096
1, 7, 1, 4096
1, 7, 1, 4096
What's the format? OK, found http://www.spinics.net/lists/fio/msg01064.html
Format of entries is:
time, rate/latency, data direction, block size
Time: in milliseconds. Bandwidth logs are usually 500 or 1000ms apart; that
can be controlled by the config file with "bwavgtime=[x ms]".
Rate/latency: for bandwidth, this is in KB/sec. For latency, it's
microseconds.
Data direction: 0 is read, 1 is write.
Block size: block size of IOs in bytes.
what is the format of the file fiotest.1.0 ?
Is there a way to get the latency files without this file to avoid too
much output.
Thanks
- Kyle
On Tue, Aug 7, 2012 at 7:47 AM, Mike Ryan <mike.ryan@inktank.com> wrote:
>
> On Tue, Aug 07, 2012 at 03:43:06PM +0200, Jens Axboe wrote:
> > > fio --latency-log=/tmp/log --output=/tmp/log random_write.fio
> >
> > The latency/bw logs are named from the job name, so you can't actually
> > give it a specific name with the (global) command line option. You'd
> > need to use the job option to do that.
>
> The argument requires an option. It appears that option is discarded.
>
> > That said, it does look broken in that we don't inherit the global
> > setting. Does the below make it work?
>
> Yes! The files are named log_lat.log, log_slat.log, and log_clat.log.
> They are not named after the job.
> --
> To unsubscribe from this list: send the line "unsubscribe fio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
- Kyle
O: +1.415.341.3430
F: +1.650.494.1676
275 Middlefield Road, Suite 50
Menlo Park, CA 94025
http://www.delphix.com
prev parent reply other threads:[~2012-08-08 5:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 1:03 generating latency logs Mike Ryan
2012-08-07 13:43 ` Jens Axboe
2012-08-07 14:47 ` Mike Ryan
2012-08-08 5:23 ` Kyle Hailey
2012-08-08 5:26 ` Kyle Hailey [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='CACiQ3FBAo7PDL9hcZTWtJBAJA40BcdM9XKX87x=fv4PqODu0-g@mail.gmail.com' \
--to=kyle.hailey@delphix.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=mike.ryan@inktank.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.