From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu
Subject: Performance of Ingo's O(1) scheduler on 8 way NUMA-Q
Date: Fri, 25 Jan 2002 15:07:13 -0800 [thread overview]
Message-ID: <23350000.1012000033@flay> (raw)
In-Reply-To: <119440000.1011836623@flay>
In-Reply-To: <Pine.LNX.4.33.0201211626030.12418-100000@localhost.localdomain> <119440000.1011836623@flay>
Measuring the performace of a parallelized kernel compile with warm caches
on a 8 way NUMA-Q box. Highmem support is turned OFF so I'm only using
the first 1Gb or so of RAM (it's much faster without HIGHMEM).
prepare:
make -j16 dep; make -j16 bzImage; make mrproper; make -j16 dep;
measured:
time make -j16 bzImage
2.4.18-pre7
330.06user 99.92system 1:00.35elapsed 712%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (411135major+486026minor)pagefaults 0swaps
2.4.18-pre7 with J6 scheduler
307.19user 88.54system 0:57.63elapsed 686%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (399255major+484472minor)pagefaults 0swaps
Seems to give a significant improvement, not only giving a shorter
elapsed time, but also lower CPU load.
Martin.
next prev parent reply other threads:[~2002-01-25 23:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 15:05 [patch] O(1) scheduler, -J4 Ingo Molnar
2002-01-21 15:32 ` [patch] O(1) scheduler, -J4, 2.4.18-pre4 Ingo Molnar
2002-01-24 1:43 ` Ingo's O(1) scheduler vs. wait_init_idle Martin J. Bligh
2002-01-24 9:21 ` Ingo Molnar
2002-01-24 17:47 ` Martin J. Bligh
2002-01-24 19:59 ` Ingo Molnar
2002-01-26 17:19 ` Jesse Barnes
2002-01-25 23:07 ` Martin J. Bligh [this message]
2002-02-07 13:08 ` Performance of Ingo's O(1) scheduler on NUMA-Q Martin J. Bligh
2002-02-07 23:23 ` Ingo Molnar
2002-02-08 15:15 ` Daniel Egger
2002-02-11 17:39 ` Martin J. Bligh
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=23350000.1012000033@flay \
--to=martin.bligh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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