From: Con Kolivas <kernel@kolivas.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] SMT Nice 2.6.4-rc1-mm1
Date: Mon, 1 Mar 2004 22:25:59 +1100 [thread overview]
Message-ID: <200403012225.59538.kernel@kolivas.org> (raw)
In-Reply-To: <200403011752.56600.kernel@kolivas.org>
On Mon, 1 Mar 2004 05:52 pm, Con Kolivas wrote:
> This patch provides full per-package priority support for SMT processors
> (aka pentium4 hyperthreading) when combined with CONFIG_SCHED_SMT.
And here are some benchmarks to demonstrate what happens.
P4 3.06Ghz booted with bios HT off as UP (up), SMP with mm1(mm1), SMP with
mm1-smtnice(sn)
What would a benchmark from me be if not based on a kernel compile? These
numbers are coarse so the range is about +/- 2 seconds however the results
should be clear. Time is in seconds, rounded.
Straight kernel compile: make
Time
up 87
mm1 88
sn 88
Concurrent kernel compiles, one make, the other nice +19 make
Nice0 Nice19
up 183 235
mm1 208 211
sn 180 237
Kernel compile with an artifical cpu load running nice +19 (while true ; do
a=1 ; done)
Time
up 92
mm1 129
sn 104
Kernel compile with a true distributed computing cache burner running nice +19
(mprime www.mersenne.org)
Time
up 96
mm1 168
sn 94
Clearly the type of load running will influence the balance here depending on
how long the task actually runs and how cache intensive it is. Basically for
real world loads priority is very poorly preserved by default because of the
shared cpu resources, and the worst case is a very common one; running a
distributed computing client.
Note this patch has no demonstrable effect if tasks are run at the same nice
value.
Con
next prev parent reply other threads:[~2004-03-01 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 6:52 [PATCH] SMT Nice 2.6.4-rc1-mm1 Con Kolivas
2004-03-01 11:25 ` Con Kolivas [this message]
2004-03-01 11:37 ` Nick Piggin
2004-03-01 11:40 ` Con Kolivas
2004-03-01 11:46 ` Nick Piggin
2004-03-01 11:53 ` Con Kolivas
2004-03-01 11:45 ` Con Kolivas
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=200403012225.59538.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--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