From: rwhron@earthlink.net
To: piggin@cyberone.com.au, venom@sns.it
Cc: linux-kernel@vger.kernel.org, dmo@osdl.org, akpm@osdl.org
Subject: Re: [BENCHMARK] I/O regression after 2.6.0-test5
Date: Tue, 21 Oct 2003 09:05:01 -0400 [thread overview]
Message-ID: <20031021130501.GA4409@rushmore> (raw)
> If you have time, would you please try testing as-iosched.c from
> test5 in a later kernel (it won't go into test8-mm1 though).
copying drivers/block/as-iosched.c from 2.6.0-test5 to test8
looks like it fixes the regression. Here are the results so far.
In the AIM7 database benchmark, jobs/minute using test5 as-iosched.c
doubled. At 32 tasks, jobs/min went from 300 to 601.
At 256 tasks, jobs/min went from 552 to 1010.
test5 as-iosched.c:
cat suite7-dbase-2.6.0-test8-as
Benchmark Version Machine Run Date
AIM Multiuser Benchmark - Suite VII "1.1" dev4-003
Tasks Jobs/Min Real CPU
32 601.0 316.3 134.0
64 782.6 485.8 259.2
96 869.1 656.1 387.6
128 919.3 827.0 522.8
160 955.0 995.2 650.3
192 981.9 1161.5 790.9
224 1002.3 1327.5 910.2
256 1009.9 1505.7 1027.7
Unmodififed test8.
cat suite7-dbase-2.6.0-test8
Benchmark Version Machine Run Date
AIM Multiuser Benchmark - Suite VII "1.1" dev4-003
Tasks Jobs/Min Real CPU
32 299.8 634.0 128.6
64 450.5 843.9 246.5
96 549.7 1037.4 366.0
128 558.7 1360.8 497.6
160 522.1 1820.2 612.2
192 515.5 2212.4 742.7
224 529.9 2510.8 859.5
256 552.4 2753.0 980.4
The AIM7 fileserver benchmark is back up to previous
levels when test8 uses the test5 as-iosched.c:
test5 as-iosched.c with test8.
cat suite7-fserver-2.6.0-test8-as
Benchmark Version Machine Run Date
AIM Multiuser Benchmark - Suite VII "1.1" dev4-003
Tasks Jobs/Min Real CPU
4 80.5 301.0 37.0
8 133.0 364.6 64.0
12 166.7 436.3 93.4
16 175.9 551.2 111.5
20 186.3 650.7 133.8
24 202.8 717.3 161.2
28 207.1 819.3 200.0
32 210.6 920.7 226.5
Unmodified test8.
cat suite7-fserver-2.6.0-test8
Benchmark Version Machine Run Date
AIM Multiuser Benchmark - Suite VII "1.1" dev4-003
Tasks Jobs/Min Real CPU
4 42.3 573.6 40.9
8 63.3 765.7 71.6
12 83.2 874.2 95.0
16 87.5 1108.4 102.5
20 105.0 1154.6 136.7
24 111.2 1308.1 162.2
28 130.7 1297.9 185.8
32 134.2 1444.5 212.9
My tiobench test hasn't completed yet, but test8 with test5's
as-iosched.c is making good progress. I think Nick nailed the
changeset.
--
Randy Hron
http://home.earthlink.net/~rwhron/kernel/bigbox.html
next reply other threads:[~2003-10-21 13:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 13:05 rwhron [this message]
2003-10-21 15:57 ` [BENCHMARK] I/O regression after 2.6.0-test5 Nick Piggin
2003-10-21 21:07 ` venom
2003-10-22 9:54 ` Nick Piggin
2003-10-22 18:30 ` Dave Olien
2003-10-22 19:08 ` Dave Olien
2003-10-23 2:24 ` Nick Piggin
2003-10-23 3:48 ` Nick Piggin
2003-10-23 20:35 ` Dave Olien
2003-10-23 23:07 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2003-10-29 0:38 rwhron
2003-10-27 23:33 John Hawkes
2003-10-26 10:38 rwhron
2003-10-27 23:49 ` Dave Olien
2003-10-24 23:43 rwhron
2003-10-24 12:46 rwhron
2003-10-24 0:10 rwhron
2003-10-20 0:37 rwhron
2003-10-20 1:35 ` Nick Piggin
2003-10-20 4:52 ` Andrew Morton
2003-10-20 8:12 ` Nick Piggin
2003-10-20 4:51 ` Dave Olien
2003-10-20 7:55 ` venom
2003-10-21 4:49 ` Nick Piggin
2003-10-24 13:52 ` Magnus Andersson
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=20031021130501.GA4409@rushmore \
--to=rwhron@earthlink.net \
--cc=akpm@osdl.org \
--cc=dmo@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=venom@sns.it \
/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;
as well as URLs for NNTP newsgroup(s).