public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Andi Kleen <andi@firstfloor.org>
Cc: Chris Snook <csnook@redhat.com>,
	Andrew Buehler <abuehler.kernel@gmail.com>,
	Frederik Deweerdt <deweerdt@free.fr>,
	belcampo <belcampo@zonnet.nl>,
	linux-kernel@vger.kernel.org
Subject: Re: Hyperthreading performance oddities
Date: Sat, 8 Mar 2008 13:34:36 +0100	[thread overview]
Message-ID: <20080308123436.GA24982@1wt.eu> (raw)
In-Reply-To: <20080308114655.GB27074@one.firstfloor.org>

On Sat, Mar 08, 2008 at 12:46:55PM +0100, Andi Kleen wrote:
> > Well, in my experience, except for compiling, HT has always caused
> > massive slowdowns, especially on network-intensive applications.
> > Basically, network perf took a 20-30% hit, while compiling took
> 
> What network workload?

high session rate HTTP traffic. That means high packet rates, high
session lookup rates, etc...

> Networking tends to have a lot of cache misses
> and unless you're exceeding your memory bandwidth HT normally does 
> well on such workloads because it can do other things while the 
> CPU is waiting for loads.

On SMP, the load is generally divided with user-space on once CPU
and IRQs on the other one, but not well balanced though (less IRQ),
which means that SMP is rarely more than 50-60% faster than UP. On
HT, I normally observe lower performance than on UP.

> > 20-30% boost. But I must admit that I never tried HT on anything
> > more recent than a P4, maybe things have changed since.
> 
> There's nothing more recent out yet (unless you're talking non x86), 
> but there were many different P4 generations. In particular Prescott
> (90nm) was quite different from the earlier ones, but even before
> and after there were some improvements and changes.

OK. Amusingly, the HT flag is present on my C2D E8200 :

model name      : Intel(R) Core(TM)2 Duo CPU     E8200  @ 2.66GHz
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr lahf_lm

Cheers,
willy


  reply	other threads:[~2008-03-08 12:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22  9:36 Hyperthreading performance oddities belcampo
2008-02-22 10:06 ` Frederik Deweerdt
2008-03-07 13:37   ` Andrew Buehler
2008-03-07 19:08     ` Chris Snook
2008-03-07 19:20       ` Andi Kleen
2008-03-08  7:12         ` belcampo
2008-03-08  7:30         ` Willy Tarreau
2008-03-08 11:46           ` Andi Kleen
2008-03-08 12:34             ` Willy Tarreau [this message]
2008-03-08 12:43               ` Andi Kleen

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=20080308123436.GA24982@1wt.eu \
    --to=w@1wt.eu \
    --cc=abuehler.kernel@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=belcampo@zonnet.nl \
    --cc=csnook@redhat.com \
    --cc=deweerdt@free.fr \
    --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