mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Fredrickson <8nrf@qlink.queensu.ca>
To: Adam Kropelin <akropel1@rochester.rr.com>
Cc: Con Kolivas <kernel@kolivas.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nick Piggin <piggin@cyberone.com.au>, Ingo Molnar <mingo@elte.hu>,
	sam@mars.ravnborg.org
Subject: Re: HT schedulers' performance on single HT processor
Date: Sun, 14 Dec 2003 16:15:40 -0500	[thread overview]
Message-ID: <1071436539.19124.6.camel@rocky> (raw)
In-Reply-To: <20031214153504.A6795@mail.kroptech.com>

On Sun, 2003-12-14 at 15:35, Adam Kropelin wrote:
> On Sun, Dec 14, 2003 at 02:49:24PM -0500, Nathan Fredrickson wrote:
> > Same table as above normalized to the j=1 uniproc case to make
> > comparisons easier.  Lower is still better.
> > 
> >              j =  1     2     3     4     8
> > 1phys (uniproc)  1.00  1.00  1.00  1.00  1.00
> > 1phys w/HT       1.02  1.02  0.87  0.87  0.87
> > 1phys w/HT (w26) 1.02  1.02  0.87  0.87  0.88
> > 1phys w/HT (C1)  1.03  1.02  0.88  0.88  0.88
> > 2phys            1.00  1.00  0.53  0.53  0.53
>   ^^^^^                  ^^^^
> 
> Ummm...
> 
> This is mighty suspicious. With -j2 did you check to see that there
> were indeed two parallel gcc's running? Since -test6 I've found that 
> -j2 only results in a single gcc instance. I've seen this on both an
> old hacked-up RH 7.3 installation and a brand new RH 9 + updates
> installation.

I just checked and you're right, the number of compilers that actually
run is j-1, for all j>1.  I assume this is a problem with the parallel
build process, but it does not invalidate these results for comparing
the scheduler performance with different patches.
> 
> > This suggests that j should be set to at least the number of logical
> > processors + 1.
> 
> Since -test6 I've found this to be the case for kernel builds, yes. But
> I don't think it has anything to do with the scheduler or HT vs SMP
> platforms.

The 1-3% performance loss when HT is enabled for -j1 is still very real.

Nathan




  reply	other threads:[~2003-12-14 21:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12 14:57 Con Kolivas
2003-12-14 19:49 ` Nathan Fredrickson
2003-12-14 20:35   ` Adam Kropelin
2003-12-14 21:15     ` Nathan Fredrickson [this message]
2003-12-15 10:11   ` Con Kolivas
2003-12-16  0:16     ` Nathan Fredrickson
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=1071436539.19124.6.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 \
    --cc=sam@mars.ravnborg.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

all inboxes | Powered by JetHome®