All of lore.kernel.org
 help / color / mirror / Atom feed
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 20:51:44 +0100	[thread overview]
Message-ID: <4CDAF7D0.4080709@fusionio.com> (raw)
In-Reply-To: <20101110185826.GJ28050@sebastiankayser.de>

On 2010-11-10 19:58, Sebastian Kayser wrote:
> * Sebastian Kayser <sebastian@skayser.de> wrote:
>> What I will do now is to export the whole 2TB of the disk (instead of
>> just 10GB) and increase size= to see whether that makes any difference
>> (hopefully). Other than that, further ideas?
> 
> Interim update. Exported the whole 2TB disk as a LUN, mkfs.ext3'd it and
> set size=100g in fio's configuration. Also set runtime=1800, re-started
> the test and could observe ~80 IOPS ... my dear heart was jumping with
> joy :)
> 
> However, a few minutes into the test, IOPS started to increase steadily
> and by now have again reached (non-bursty) regions that don't seem
> plausible for a single 7.2K SATA disk.
> 
> root@ubuntu-804-x64:~# ./fio --section=iscsi patterns.fio 
> iscsi: (g=0): rw=randwrite, bs=4K-4K/4K-4K, ioengine=sync, iodepth=1
> Starting 1 process
> iscsi: Laying out IO file(s) (1 file(s) / 102400MB)
> Jobs: 1 (f=1): [w] [48.4% done] [0K/986K /s] [0/240 iops] [eta 15m:28s] 

A 7200RPM drive will spin around 120 times per second, that yields an
average rotational latency of 8.3 msecs. For truly random IO, rotational
latency will dominate the seek and the average wait-for-platter-spin
will be half that, so 4.17 msecs. That gives us about 240 IOPS.

So your results don't seem all that out of whack. What are your reasons
for expecting ~80 IOPS?

-- 
Jens Axboe


  parent reply	other threads:[~2010-11-10 19:51 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 [this message]
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=4CDAF7D0.4080709@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.