Flexible I/O Tester development
 help / color / mirror / Atom feed
From: David Nellans <david@nellans.org>
To: "Brian L." <brianclam@gmail.com>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: IO scheduler
Date: Thu, 10 Oct 2013 15:55:47 -0500	[thread overview]
Message-ID: <52571453.4050101@nellans.org> (raw)
In-Reply-To: <CAAAK+WXw_-gAJL9u9Bibvz=4aHVH2YYvgQRi2sMvekY6xDRR4A@mail.gmail.com>

On 10/10/2013 12:08 PM, Brian L. wrote:
> Hi there,
>
> I was wondering if you guys use NOOP IO scheduler when you are running fio?
>
> I use the CFQ IO scheduler but I do put the OS into init 1 and run fio
> process one at a time so that I can get accurate readings.
>
> I was wondering what are people practice and experience in the real world.
>
> Thanks,
> Brian L.

Some flash device drivers specifically (Fusion-io does this) use the 
noop scheduler to reduce latency and variance that can be introduced 
when using other schedulers.  Using the no-op scheduler is a reasonable 
thing to do for all drives to make apples to apples, but if a driver 
specifically overrides it to something else, probably worth sticking 
with their settings.

init 1 is overkill.  In a previous life doing a lot of measuring of 
flash - I found that simply making sure the machine was "idle" you could 
get easily get repeatability within 1% for devices doing several hundred 
thousand IOPS, even those with on-load architectures that were sensitive 
to CPU usage.

  reply	other threads:[~2013-10-10 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10 17:08 IO scheduler Brian L.
2013-10-10 20:55 ` David Nellans [this message]
2013-10-10 21:00   ` Erwan Velu
2013-10-10 21:18     ` David Nellans

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=52571453.4050101@nellans.org \
    --to=david@nellans.org \
    --cc=brianclam@gmail.com \
    --cc=fio@vger.kernel.org \
    /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