public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Fredrickson <8nrf@qlink.queensu.ca>
To: Con Kolivas <kernel@kolivas.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nick Piggin <piggin@cyberone.com.au>, Ingo Molnar <mingo@elte.hu>,
	Adam Kropelin <akropel1@rochester.rr.com>
Subject: Re: HT schedulers' performance on single HT processor
Date: Mon, 15 Dec 2003 19:16:42 -0500	[thread overview]
Message-ID: <1071533802.24673.35.camel@rocky> (raw)
In-Reply-To: <200312152111.52949.kernel@kolivas.org>

On Mon, 2003-12-15 at 05:11, Con Kolivas wrote:
> On Mon, 15 Dec 2003 06:49, Nathan Fredrickson wrote:
> > I can also run the same on four physical processors if there is
> > interest.
> 
> The specific HT scheduler benefits only start appearing with more physical 
> cpus which is to be expected. Just for demonstration the four processor run 
> would be nice (and obviously take you less time to do ;). I think it will 
> demonstrate it even more. It would be nice to help the most common case of 
> one HT cpu, though, instead of hindering it.

Here are some results on four physical processors.  Unfortunately my
quad systems are a different speed than the dual systems used for the
previous tests so the results are not directly comparable.

Same test as before, a 2.6.0 kernel compile with make -jX vmlinux. 
Results are the best real time out of five runs.
Hardware: Xeon HT 1.4GHz

Test cases:
1phys UP      - UP test11 kernel with HT disabled in the BIOS
4phys SMP     - SMP test11 kernel on 4 physical procs with HT disabled
4phys HT      - SMP test11 kernel on 4 physical procs with HT enabled
4phys HT (w26)- same as above with Nick's w26 sched-rollup patch
4phys HT (C1) - same as above with Ingo's C1 patch

Here are the results normalized to the X=1 UP case to make comparisons
easier.  Lower is better.

          X =  1     2     3     4     5     6     7     8     9    16
1phys UP      1.00  1.00  1.00  1.00  1.00  1.00  1.00  1.00  1.00  1.00
4phys SMP     1.00  0.99  0.51  0.35  0.27  0.27  0.27  0.27  0.27  0.27
4phys HT      1.01  1.00  0.55  0.40  0.33  0.29  0.27  0.26  0.25  0.26
4phys HT(w26) 1.01  1.01  0.54  0.37  0.31  0.27  0.26  0.26  0.26  0.26
4phys HT(C1)  1.01  1.00  0.52  0.36  0.29  0.28  0.27  0.26  0.25  0.26

Interesting that the overhead due to HT in the X=1 column is only 1%
with 4 physical processors.  It was 1-3% before with 1 or 2 physical
processors.

In the partial load columns where there are less compiler processes than
logical CPUs (X=3,4,5,6,7), it appears that both patches are doing a
better job scheduling than the standard scheduler.  At full load (X=>8)
all three HT test cases perform about equally and beat standard SMP by
1-2%.

Hope these results are helpful.  I'd be happy to run more cases and/or
other patches.

Nathan


  reply	other threads:[~2003-12-16  0:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12 14:57 HT schedulers' performance on single HT processor Con Kolivas
2003-12-14 19:49 ` Nathan Fredrickson
2003-12-14 20:35   ` Adam Kropelin
2003-12-14 21:15     ` Nathan Fredrickson
2003-12-15 10:11   ` Con Kolivas
2003-12-16  0:16     ` Nathan Fredrickson [this message]
2003-12-16  0:55       ` Con Kolivas
2003-12-16  3:57         ` Nathan Fredrickson
2004-01-03 17:56 ` Bill Davidsen

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=1071533802.24673.35.camel@rocky \
    --to=8nrf@qlink.queensu.ca \
    --cc=akropel1@rochester.rr.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=piggin@cyberone.com.au \
    /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