From: Jens Axboe <axboe@suse.de>
To: Vishal Patil <vishpat@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: Re: CSCAN vs CFQ I/O scheduler benchmark results
Date: Tue, 13 Jun 2006 07:46:10 +0200 [thread overview]
Message-ID: <20060613054609.GR4420@suse.de> (raw)
In-Reply-To: <4745278c0606121038y7fcdab2q33a9065e9071938b@mail.gmail.com>
On Mon, Jun 12 2006, Vishal Patil wrote:
> Jens
>
> Could you let me know what tests would be fair to make comparsion
> between the I/O schedulers? Thanks.
Depends on what you want to test, of course! I can't give you an answer
on that.
The thing about IO schedulers is that it's easy to provide good
throughput or good latency, but hard to do both. The tests you did so
far have x processes doing the same thing. Try something that has eg an
async writer going full throttle, and then a/some sync readers.
--
Jens Axboe
prev parent reply other threads:[~2006-06-13 5:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 19:30 CSCAN vs CFQ I/O scheduler benchmark results Vishal Patil
2006-06-10 2:15 ` Vishal Patil
2006-06-11 10:09 ` Jan Engelhardt
2006-06-11 18:58 ` Jens Axboe
2006-06-11 23:47 ` Vishal Patil
2006-06-12 6:41 ` Jens Axboe
2006-06-12 17:38 ` Vishal Patil
2006-06-12 22:21 ` Nate Diller
2006-06-13 5:46 ` Jens Axboe [this message]
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=20060613054609.GR4420@suse.de \
--to=axboe@suse.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vishpat@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox