From: Bill Davidsen <davidsen@tmr.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Benchmarks With P4+SMP+SMT?
Date: Wed, 29 Dec 2004 22:08:45 -0500 [thread overview]
Message-ID: <41D3713D.3010707@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0412281914380.11816@p500>
Justin Piszcz wrote:
> Has anyone performed any benchmarks with:
>
> No SMP w/HT?
> SMP w/HT?
> SMP + SMT w/HT?
>
> [ ] Symmetric multi-processing support
> [ ] SMT (Hyperthreading) scheduler support
>
> x SMT scheduler support improves the CPU scheduler's decision making
> x when dealing with Intel Pentium 4 chips with HyperThreading at a
> x cost of slightly increased overhead in some places. If unsure say
> x N here.
>
> I'm tempted to try SMT and benchmark these sometime but I am asking the
> list if anyone has already done this first.
>
> Question: "slightly increased overhead in some places."
>
> What type of workloads would exhibit such overhead?
>
> Would this option (SMT) be recommended for a desktop or server machine?
>
> Are there any white papers or documentation I can read about this option?
I run SMT on all my HT uni systems. Depending on what you do it can help
up to 30% (kernel build) or just enough to measure. This is one of those
"it depends" things, I bet there are loads which run better without, and
there is a tad of overhead in the SMP kernel locking.
If you run SMP, you have that overhead anyway, so I doubt it hurts.
YMMV
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2004-12-30 2:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-29 0:17 Kernel Benchmarks With P4+SMP+SMT? Justin Piszcz
2004-12-30 3:08 ` Bill Davidsen [this message]
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=41D3713D.3010707@tmr.com \
--to=davidsen@tmr.com \
--cc=jpiszcz@lucidpixels.com \
--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