From: Jens Axboe <jaxboe@fusionio.com>
To: Sebastian Kayser <sebastian@skayser.de>
Cc: fio@vger.kernel.org
Subject: Re: IOPS higher than expected on randwrite, direct=1 tests
Date: Wed, 10 Nov 2010 15:09:07 +0100 [thread overview]
Message-ID: <4CDAA783.9050902@fusionio.com> (raw)
In-Reply-To: <20101110082223.GB14261@sebastiankayser.de>
On 2010-11-10 09:22, Sebastian Kayser wrote:
> Hi John,
>
> * John Cagle <jcagle@gmail.com> wrote:
>> Is your iSCSI target also in a virtual machine? If so, maybe the
>> hypervisor (vmware? kvm?) is caching the 10GB volume that is being
>> used by the iSCSI target?
>
> thanks for answering. No hypervisor involved on the iSCSI target, it's
> an oldish Infortrend storage [1] for which I am trying to determine the
> performance profile. Anything else along the stack that might skew the
> test results?
>
> Just to make sure my understanding is correct:
> - direct=1 should mitigate (disable?) OS caching effects
> - sync=1, iodepth=1 should make sure that an I/O has really made it to
> disk before the next on is issued, i.e. should de-facto disable
> I/O coalescing or device caching
>
> Are these sane/valid assumptions?
Yes, your assumptions are valid. I think the issue here is that you give
randwrite, but don't also specify that you want overwrites. So what
happens is that the file will be truncated and then randomly written,
allowing the file system to place randomly chosen file block together.
If you remove the test file and re-run with overwrite=1 added, then see
if those results are more in line with what you expect.
--
Jens Axboe
next prev parent reply other threads:[~2010-11-10 14:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 18:28 IOPS higher than expected on randwrite, direct=1 tests Sebastian Kayser
2010-11-10 6:57 ` John Cagle
2010-11-10 8:22 ` Sebastian Kayser
2010-11-10 14:09 ` Jens Axboe [this message]
2010-11-10 17:18 ` Sebastian Kayser
2010-11-10 18:58 ` Sebastian Kayser
2010-11-10 19:50 ` John Cagle
2010-11-10 19:52 ` Sebastian Kayser
2010-11-10 20:04 ` Jens Axboe
2010-11-12 14:38 ` Sebastian Kayser
2010-11-12 17:59 ` Shawn Lewis
2010-11-10 19:52 ` Jens Axboe
2010-11-10 19:51 ` Jens Axboe
2010-11-10 20:35 ` Sebastian Kayser
2010-11-10 19:48 ` Jens Axboe
2010-11-10 21:32 ` Udi.S.Karni
2010-11-11 17:43 ` Sebastian Kayser
2010-11-11 16:22 ` Sebastian Kayser
2010-11-11 21:25 ` Shawn Lewis
2010-11-12 13:43 ` Sebastian Kayser
2010-11-12 18:00 ` Shawn Lewis
2010-11-13 20:02 ` Jens Axboe
2010-11-15 13:36 ` Jeff Moyer
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=4CDAA783.9050902@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=fio@vger.kernel.org \
--cc=sebastian@skayser.de \
/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.