public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: arjan@fenrus.demon.nl (Arjan van de Ven)
To: alan@lxorguk.ukuu.org.uk (Alan Cox)
Cc: linux-kernel@vger.kernel.org
Subject: Re: UP 2.2.18 makes kernels 3% faster than UP 2.4.0-test12
Date: Mon, 11 Dec 2000 21:15:45 +0100 (CET)	[thread overview]
Message-ID: <m145ZMP-000OWyC@amadeus.home.nl> (raw)
In-Reply-To: <Pine.LNX.4.21.0012111636040.4808-100000@duckman.distro.conectiva> <E145Xy6-0008HA-00@the-village.bc.nu>

In article <E145Xy6-0008HA-00@the-village.bc.nu> you wrote:
>> Doing a 'make bzImage' is NOT VM-intensive. Using this as a test
>> for the VM doesn't make any sense since it doesn't really excercise
>> the VM in any way...

> Its an interesting demo that 2.4 has some performance problems since 2.2
> is slower than 2.0 although nowdays not much.

Seems to depend on the hardware used. On my test box, 2.4 is faster by
0.3s....

Greetings,
    Arjan van de Ven

Machine:
AMD Duron 700Mhz with 128Mb of 133Mhz Ram
2 IBM 15Gb ATA100 disks in RAID0 raid

tested kernels:
2.2.18 + raid patch + latest IDE patch
2.4.0-test12pre7

compiling 2.2.18 with gcc 2.95.2

				1st run		2nd		3rd
kernel 2.2.18/raid/ide		3:28.909	3:28.819	3:28.840
kernel 2.4.0test12pre7		3:28:520	3:28.534	3:28.546

-
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/

  parent reply	other threads:[~2000-12-11 20:46 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
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 [this message]
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=m145ZMP-000OWyC@amadeus.home.nl \
    --to=arjan@fenrus.demon.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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