From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org
Cc: andrea@suse.de
Subject: changelogs for 2.4.17rc2aa2 and 2.2.20aa1
Date: Wed, 2 Jan 2002 09:05:47 -0500 [thread overview]
Message-ID: <20020102090547.A233@earthlink.net> (raw)
I put together these pages to help others understand
what is in Andrea's kernels a little better.
http://home.earthlink.net/~rwhron/kernel/2.4.17rc2aa2.html
http://home.earthlink.net/~rwhron/kernel/2.2.20aa1.html
The pages are created from his patch diff logs.
I've stress tested and benchmarked 2.4.17rc2aa2 a lot and
it's been very solid. For a workload that creates a lot
of processes 2.4.17rc2aa2 has a definite edge. This is
easiest to see in a couple unixbench tests:
2.4.17-mjc1 2.4.17rc2aa2 2.5.1-dj10
System Call Overhead 352361.7 362120.5 255809.4 lps
Process Creation 817.5 2037.7 1212.0 lps
Execl Throughput 265.8 458.4 316.5 lps
And lmbench; the highest and lowest results of 3 runs were dropped.
Processor, Processes - times in microseconds - smaller is better
----------------------------------------------------------------
OS fork exec sh
proc proc proc
------------ ---- ---- ----
2.4.17rc2aa2 745 2769 9583
2.5.1-dj10 810 3504 11.K
2.4.17-mjc1 1128 4244 12.K
Good stuff comes from a lot of sources, and I'm hoping some of
the tree maintainers will start cherry picking from Andrea's
tree too. :)
Note: mjc1 above was configured without preempt, rtsched
or lockbreak.
2.4.17rc2aa2 consistently does better at dbench too.
More results are at:
http://home.earthlink.net/~rwhron/kernel/repo.html
--
Randy Hron
next reply other threads:[~2002-01-02 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-02 14:05 rwhron [this message]
2002-01-03 3:54 ` changelogs for 2.4.17rc2aa2 and 2.2.20aa1 Dave Jones
2002-01-03 8:56 ` Jens Axboe
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=20020102090547.A233@earthlink.net \
--to=rwhron@earthlink.net \
--cc=andrea@suse.de \
--cc=linux-kernel@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