All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Xiaofei Du <xiaofei.du008@gmail.com>
Cc: fio <fio@vger.kernel.org>, aaronc <aaronc@cse.unsw.edu.au>
Subject: Re: Question about FIO sequential writes
Date: Tue, 15 Apr 2014 19:44:45 -0600	[thread overview]
Message-ID: <534DE08D.2070604@kernel.dk> (raw)
In-Reply-To: <CAND_vCbQHu4k5Q2RS5XeFYNTh5r1yC0ORYdv0JG-hHan4404kg@mail.gmail.com>

On 2014-04-15 17:04, Xiaofei Du wrote:
> [global]
> bs=4k
> size=100m
> direct=1
> filename=100mfile
>
> [seq-write]
> rw=write
> stonewall
>
> [rand-write]
> rw=randwrite
> stonewall
>
> ########################################################################
>
> This is the output. In this run the difference is 115 vs 123. On another
> disk, the number I got was 121 vs 141. Random writes are always faster
> than sequential writes.

Since the region is only 100M, it seems reasonable to expect random IO 
within that region to be faster than sequential ones. The sequential 
ones will always be subject to a full rotational penalty, limiting your 
IOPS to 120 if we disregard software overhead, DMA, etc. So 115 seems 
very in the ballpark. For random IO, we have to move the head a bit, but 
if the seek is less than half 1/RPM, then it's a win.

So I'd say things are looking as expected.

-- 
Jens Axboe



  reply	other threads:[~2014-04-16  1:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 22:14 Question about FIO sequential writes Xiaofei Du
2014-04-15 22:24 ` Jens Axboe
2014-04-15 23:04   ` Xiaofei Du
2014-04-16  1:44     ` Jens Axboe [this message]
2014-04-16  4:47       ` Elliott, Robert (Server Storage)
2014-04-16 14:41         ` Jens Axboe
2014-04-17  1:08         ` Xiaofei Du
2014-04-17 14:30           ` Elliott, Robert (Server Storage)
2014-04-17 18:29             ` Xiaofei Du
2014-04-21 16:38         ` Bruce Cran
2014-04-16  1:10   ` Xiaofei Du

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=534DE08D.2070604@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=aaronc@cse.unsw.edu.au \
    --cc=fio@vger.kernel.org \
    --cc=xiaofei.du008@gmail.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.