All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Shawn Lewis <shawnlewis@google.com>
Cc: Sebastian Kayser <sebastian@skayser.de>, fio@vger.kernel.org
Subject: Re: IOPS higher than expected on randwrite, direct=1 tests
Date: Sat, 13 Nov 2010 21:02:45 +0100	[thread overview]
Message-ID: <4CDEEEE5.5060305@fusionio.com> (raw)
In-Reply-To: <AANLkTik5=tSj9h-O8O5Bub8J86rRiyYrTx7mmX5asgqC@mail.gmail.com>

>> I wonder how many times I saw someone - including myself - fire up
>> bonnie++ or iozone with a rather small test file compared to the full
>> disk size ... Thanks very much everyone! This was an (overdue) eye
>> opener.
> In addition, testing with a file is dependent on the state of the file
> system. For example, if you're using a 100GB file and there's not enough
> contiguous free space to lay it out in one chunk you could have regions on
> different parts of the disk. Further, even there is enough space, that space
> could be near the inner or outer diameter which would also affect
> performance.
> 
> There is a way to get a file address to lba map (which would give you some
> insight into how a file is laid out). I think there's a syscall. Jens should
> know.

Yep, you can use FIBMAP/FIEMAP to walk the extents of the file and get a
full map of how it's laid out on disk. Not sure if there are tools
that'll do this for you, if not is pretty trivial to write.

-- 
Jens Axboe


  reply	other threads:[~2010-11-13 20:02 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
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 [this message]
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=4CDEEEE5.5060305@fusionio.com \
    --to=jaxboe@fusionio.com \
    --cc=fio@vger.kernel.org \
    --cc=sebastian@skayser.de \
    --cc=shawnlewis@google.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.