From: "John Fremlin" <vii@penguinpowered.com>
To: <scole@lanl.gov>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: UP 2.2.18 makes kernels 3% faster than UP 2.4.0-test12
Date: 11 Dec 2000 18:16:43 +0000 [thread overview]
Message-ID: <m2k896rfg4.fsf@localhost.yi.org.> (raw)
In-Reply-To: <00121013363704.01067@spc.esa.lanl.gov>
In-Reply-To: Steven Cole's message of "Sun, 10 Dec 2000 13:36:37 -0700"
Steven Cole <scole@lanl.gov> writes:
[...]
> In each case, the task and the tools used are the same. The only
> difference was the kernel used. In both cases, 2.2.18 won by 3%.
> Its comparing apples to apples and oranges to oranges. Granted 3%
> isn't very much, but I would have guessed that 2.4.0 would have been
> the winner. It wasn't, at least for this single processor machine.
Two points: (1) gcc 2.95 makes slightly slower code than egcs-1.1
(according to benchmarks on gcc.gnu.org) so compile 2.4 kernel with
egcs for a fairer comparison. (2) The new VM was a performance
regression for throughput.
I think that it is important that the extent of the indisputable
performance decreases be quantified and traced. For me there was a
subjective performance peak around 2.3.48 IIRC, though it might have
been before. Andrea Archangeli has a VM patch that seems to
help in some cases.
It would be interesting to run a series of (automated) tests on a lot
of kernel versions, and to see how far performance is behind FreeBSD
(or even NetBSD).
[...]
--
http://www.penguinpowered.com/~vii
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-11 18:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-10 20:36 UP 2.2.18 makes kernels 3% faster than UP 2.4.0-test12 Steven Cole
2000-12-11 18:16 ` John Fremlin [this message]
2000-12-11 18:38 ` Rik van Riel
2000-12-11 18:46 ` Alan Cox
2000-12-11 19:50 ` Zdenek Kabelac
2000-12-11 20:15 ` Arjan van de Ven
2000-12-11 20:23 ` Rik van Riel
2000-12-11 22:03 ` Gerhard Mack
2000-12-11 22:06 ` Alan Cox
2000-12-13 9:44 ` Rogier Wolff
2000-12-14 13:08 ` Russell King
2000-12-16 0:40 ` george anzinger
2000-12-12 14:49 ` Steven Cole
2000-12-12 18:18 ` Steven Cole
2000-12-12 18:40 ` Linus Torvalds
2000-12-12 20:19 ` Steven Cole
2000-12-12 20:38 ` Linus Torvalds
2000-12-12 22:09 ` Steven Cole
2000-12-11 22:12 ` Gabor Lenart
-- strict thread matches above, loose matches on Subject: below --
2000-12-10 15:31 Steven Cole
2000-12-10 19:52 ` Aaron Tiensivu
2000-12-11 23:02 ` Steven Cole
2000-12-12 4:40 ` Mike Galbraith
2000-12-12 5:17 ` Steven Cole
2000-12-12 5:20 ` Mike Galbraith
2000-12-12 11:01 ` Helge Hafting
2000-12-12 10:27 ` Rik van Riel
2000-12-12 14:15 ` Mike Galbraith
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=m2k896rfg4.fsf@localhost.yi.org. \
--to=vii@penguinpowered.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scole@lanl.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.