From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org
Cc: marcelo@conectiva.com.br, akpm@zip.com.au
Subject: Linux 2.4.19-pre5
Date: Sat, 30 Mar 2002 13:53:33 -0500 [thread overview]
Message-ID: <20020330135333.A16794@rushmore> (raw)
> This release has -aa writeout scheduling changes, which should improve IO
> performance (and interactivity under heavy write loads).
> _Please_ test that extensively looking for any kind of problems
> (performance, interactivity, etc).
2.4.19-pre5 shows a lot of improvement in the tests
I run. dbench 128 throughput up over 50%
dbench 128 processes
2.4.19-pre4 8.4 ****************
2.4.19-pre5 13.2 **************************
Tiobench sequential writes:
10-20% more throughput and latency is lower.
Tiobench Sequential reads
Down 7-8%.
Andrew Morton's read_latency2 patch improves tiobench
sequential reads and writes by 10-35% in the tests I've
run. More importantly, read_latency2 drops max latency
with 32-128 tiobench threads from 300-600+ seconds
down to 2-8 seconds. (2.4.19-pre5 is still unfair
to some read requests when threads >= 32)
I'm happy with pre5 and hope more chunks of -aa show
up in pre6. Maybe Andrew will update read_latency2 for
inclusion in pre6. :) It helps tiobench seq writes too.
dbench goes down a little though.
Max latency is the metric that stands out as "needs
improvement" and "fix exists".
tiobench seq reads 128 threads
MB/s max latency
2.4.19-pre1aa1 6.98 661.3 seconds
2.4.19-pre1aa1rl 9.55 7.8 seconds
tiobench seq writes 32 threads
MB/s max latency
2.4.19-pre1aa1 15.46 26.1 seconds
2.4.19-pre1aa1rl 17.31 18.0 seconds
The read latency issue exists on a 4 way xeon
with 4GB ram too. Max latency jumps to 270 seconds
with 32 tiobench threads, and is over 500 seconds when
threads >= 128. (latency in milliseconds below)
Sequential Reads
Num Avg Maximum Lat% Lat%
Kernel Thr Rate (CPU%) Latency Latency >2s >10s
-------------- --- ------------------------------------------------------
2.4.19-pre5 1 38.46 23.94% 0.302 111.14 0.00000 0.00000
2.4.19-pre5 32 30.24 21.69% 9.883 270391.48 0.01106 0.00915
2.4.19-pre5 64 30.08 21.67% 17.868 357219.21 0.01965 0.01807
2.4.19-pre5 128 30.40 22.77% 30.460 520607.27 0.02714 0.02569
2.4.19-pre5 256 29.07 21.96% 56.444 539381.86 0.05378 0.05197
The behemoth benchmark page:
http://home.earthlink.net/~rwhron/kernel/k6-2-475.html
--
Randy Hron
next reply other threads:[~2002-03-30 18:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-30 18:53 rwhron [this message]
2002-03-30 19:49 ` Linux 2.4.19-pre5 Andrew Morton
2002-03-30 21:33 ` Randy Hron
2002-03-30 21:42 ` Ed Sweetman
2002-03-30 22:25 ` Randy Hron
2002-03-30 23:48 ` Ed Sweetman
2002-03-31 12:42 ` Randy Hron
2002-03-31 20:05 ` Ed Sweetman
2002-03-31 23:11 ` Randy Hron
2002-03-31 6:52 ` Andrew Morton
2002-04-01 0:36 ` Andrea Arcangeli
2002-04-01 1:24 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2002-04-04 9:08 Tom Holroyd
2002-04-04 19:28 ` Marcelo Tosatti
2002-04-05 4:13 ` Tom Holroyd
2002-04-16 14:49 ` Andrea Arcangeli
2002-04-17 1:22 ` Tom Holroyd
2002-03-29 21:47 Marcelo Tosatti
2002-03-30 20:40 ` Michal Jaegermann
2002-03-30 23:34 ` Keith Owens
2002-03-31 1:41 ` Michal Jaegermann
2002-04-04 19:50 ` Adrian Bunk
2002-04-04 21:41 ` Marcelo Tosatti
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=20020330135333.A16794@rushmore \
--to=rwhron@earthlink.net \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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