From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: "Lamkin, Eric" <Eric.Lamkin@lsi.com>
Cc: David Nellans <david@nellans.org>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: fio replay
Date: Wed, 26 Feb 2014 16:15:01 +0000 [thread overview]
Message-ID: <20140226161451.GA26792@sucs.org> (raw)
In-Reply-To: <e7ef163bab6c4f72a53926e0ef9f5ffd@BN1PR07MB437.namprd07.prod.outlook.com>
On Wed, Feb 26, 2014 at 03:48:54PM +0000, Lamkin, Eric wrote:
>
> Were you replaying on the same host where the blktrace was recorded?
Yes I was.
> I am not.
So long as the target block device is big enough I would hope it would
not make a difference so long as you were using replay_redirect . It
definitely works for me using different devices.
> I'll try with no --iodepth command. That is all I see different
> between your methodology and mine.
That should not make a difference other than making things slower. The
real command I'm using is
fio --read_iolog=sdd.dump --ioengine=libaio --iodepth=10 --direct=1 --thinktime=15000 --thinktime_blocks=16 --replay_no_stall=1 --replay_redirect=/dev/sdf --name=replay
> What is btreplay? Does it allow device mapping if the traced devices
> have different names on the replay host? Will btreplay run
> unconstrained by the original timings?
This is a bit off topic but I'll take stab at answering anyway.
btreplay "recreate[s] IO loads recorded by blktrace"
(http://linux.die.net/man/8/btreplay ). Usage is as follows:
blktrace -d /dev/sdd
btrecord sdd
btreplay sdd
Device mappings are supported using the -M/--map-devs option. It can be
made to go as fast as possible by using the -N/--no-stalls option.
You may also want to look at blkreplay by Thomas Schoebel-Theuer of 1&1.
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2014-02-26 16:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 13:44 fio replay Lamkin, Eric
2014-02-26 14:13 ` David Nellans
2014-02-26 14:23 ` Lamkin, Eric
2014-02-26 15:30 ` Sitsofe Wheeler
2014-02-26 15:48 ` Lamkin, Eric
2014-02-26 16:15 ` Sitsofe Wheeler [this message]
2014-02-26 17:49 ` Jens Axboe
2014-02-26 21:44 ` Jens Axboe
2014-02-26 21:55 ` Lamkin, Eric
2014-02-27 18:48 ` Jens Axboe
2014-02-27 20:12 ` Lamkin, Eric
2014-03-03 13:25 ` Lamkin, Eric
2014-03-04 3:12 ` Alireza Haghdoost
2014-03-04 13:37 ` Lamkin, Eric
2014-03-06 15:55 ` Jens Axboe
2014-03-06 16:12 ` Lamkin, Eric
2014-03-28 13:52 ` Lamkin, Eric
2014-04-10 15:37 ` Lamkin, Eric
-- strict thread matches above, loose matches on Subject: below --
2014-02-20 16:39 Lamkin, Eric
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=20140226161451.GA26792@sucs.org \
--to=sitsofe@yahoo.com \
--cc=Eric.Lamkin@lsi.com \
--cc=david@nellans.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox