From: Neil Schemenauer <nas@python.ca>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][CFT] new IO scheduler for 2.4.20
Date: Sun, 20 Apr 2003 18:46:04 -0700 [thread overview]
Message-ID: <20030421014603.GA18971@glacier.arctrix.com> (raw)
In-Reply-To: <200304210006.23762.m.c.p@wolk-project.de>
Marc-Christian Petersen wrote:
> what about i/o throughput, bonnie or such?
bonnie++
Version 1.03 ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
2.4.20 1G 36236 18 13423 7 29948 11 210.1 0
2.4.20-nas1 1G 35998 18 12076 7 19056 9 206.7 0
2.4.20-nas2 1G 37450 18 12101 7 19363 9 210.7 0
Read throughput has definitely taken a hit. I don't know why. Perhaps
the elevator needs to have a little more relaxed definition of
contiguous requests. Right now it only puts requests together if they
are perfectly contiguous (the first sector in one request is the next
after the last sector of another). I'll try to test that.
Any other theories?
Neil
next prev parent reply other threads:[~2003-04-21 1:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 17:28 [PATCH][CFT] new IO scheduler for 2.4.20 Neil Schemenauer
2003-04-17 20:41 ` Andrew Morton
2003-04-20 18:26 ` Neil Schemenauer
2003-04-20 22:06 ` Marc-Christian Petersen
2003-04-21 1:46 ` Neil Schemenauer [this message]
2003-04-21 11:33 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2003-05-30 22:09 Neil Schemenauer
2003-05-30 23:40 ` Con Kolivas
2003-05-31 0:52 ` Neil Schemenauer
2003-05-30 17:58 ` Robert Love
2003-06-02 17:21 Andreas Dilger
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=20030421014603.GA18971@glacier.arctrix.com \
--to=nas@python.ca \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox