From: Steven Cole <scole@lanl.gov>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: UP 2.2.18 makes kernels 3% faster than UP 2.4.0-test12
Date: Tue, 12 Dec 2000 15:09:02 -0700 [thread overview]
Message-ID: <00121215090200.00928@spc.esa.lanl.gov> (raw)
In-Reply-To: <Pine.LNX.4.10.10012121236360.2553-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10012121236360.2553-100000@penguin.transmeta.com>
On Tuesday 12 December 2000 13:38, Linus Torvalds wrote:
> On Tue, 12 Dec 2000, Steven Cole wrote:
> > Task: make -j3 bzImage for 2.4.0-test12-pre7 kernel tree.
>
> Actually, do it with
>
> make -j3 'MAKE=make -j3' bzImage
>
> A single "-j3" won't do much. It will only build three directories at a
> time, and you'll never see much load. But doing it recursively means that
> you'll build three at a time all the way out to the leaf directories, and
> you should see loads up to 20+, and much more memory pressure too.
>
> Linus
Ok, repeated the tests with make -j3 'MAKE=make -j3' bzImage
I ran xosview to monitor the load.
The load values for 2.2.18 seemed to stay higher longer than
for 2.4.0-test12. I recorded the peak load observed.
For comparison, with make -j3 bzImage, the peak load was much
lower, about 2.7.
Task: make -j3 'MAKE=make -j3' bzImage for 2.4.0-test12-pre7 kernel tree.
Numbers are seconds to build.
New results:
1 2 3 ave.
143 143 143 143 Running 2.2.18 SMP
19.1 17.5 19.2 18.6 Max load observed with xosview
142 141 141 141.3 Running 2.4.0-test12-pre7 SMP
16.2 16.8 15.2 16.1 Max load observed with xosview
Steven
-
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-12 22:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-10 20:36 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
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 [this message]
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=00121215090200.00928@spc.esa.lanl.gov \
--to=scole@lanl.gov \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®