From: Erwan Velu <erwan@enovance.com>
To: David Nellans <david@nellans.org>
Cc: "Brian L." <brianclam@gmail.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: IO scheduler
Date: Thu, 10 Oct 2013 23:00:58 +0200 [thread overview]
Message-ID: <5257158A.2050707@enovance.com> (raw)
In-Reply-To: <52571453.4050101@nellans.org>
On 10/10/2013 22:55, David Nellans wrote:
> [...]
> 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.
On my side, I've been creating a specific ramfs that does the fio
testing I want. This way I'm sure that nothing else is running on my
system (like daemons or gui stuff).
That's a little bit extreme but it insures the same OS & environment to
be used over & over making all my tests much more comparable over time.
My 2 cents,
Erwan,
next prev parent reply other threads:[~2013-10-10 21:01 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
2013-10-10 21:00 ` Erwan Velu [this message]
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=5257158A.2050707@enovance.com \
--to=erwan@enovance.com \
--cc=brianclam@gmail.com \
--cc=david@nellans.org \
--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