From: Jens Axboe <jens.axboe@oracle.com>
To: Michael O'Sullivan <michael.osullivan@auckland.ac.nz>
Cc: fio@vger.kernel.org, DongJin Lee <dongjin.lee@auckland.ac.nz>
Subject: Re: Using offsets in fio
Date: Tue, 27 Apr 2010 08:42:24 +0200 [thread overview]
Message-ID: <20100427064224.GX27497@kernel.dk> (raw)
In-Reply-To: <4BD62D8A.5050109@auckland.ac.nz>
On Tue, Apr 27 2010, Michael O'Sullivan wrote:
> Hi everyone,
>
> We are using fio to emulate the SPC-1 benchmark (we hope to get this
> included as a --profile in fio in the not too distant future). However,
> we have noticed that when running our benchmark the disk we are testing
> does not seem to be overly busy seeking to different locations on the
> disk. When we run tests using Iometer we can hear the disk seeking to
> different sections of the disk pretty much the whole time. We are using
> io_u->offset to define the position in the file we wish to read/write
> at, but it is not clear to us whether this is having the desired effect.
> It doesn't seem so at this point... We have been using the sync and
> libaio engines.
io_u->offset is the byte offset that the engine will seek to before
performing IO, so whatever you put in there will be the real offset. If
the disk doesn't sound as busy as it should, perhaps it's because
iometer drives a higher queue depth as well?
> Can someone please give us some advice to help us troubleshoot this
> problem? Or point us to a tool that will let us see where fio is
> reading/writing on the disk? Any help is greatly appreciated.
For shorter samples, you could always just strace fio and see what it's
doing. For a better view, you could use blktrace.
--
Jens Axboe
next prev parent reply other threads:[~2010-04-27 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 0:19 Using offsets in fio Michael O'Sullivan
2010-04-27 6:42 ` Jens Axboe [this message]
2010-04-27 6:49 ` DongJin Lee
2010-04-27 6:54 ` Jens Axboe
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=20100427064224.GX27497@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=dongjin.lee@auckland.ac.nz \
--cc=fio@vger.kernel.org \
--cc=michael.osullivan@auckland.ac.nz \
/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