From: Andrew Burgess <aab@cichlid.com>
To: linux-kernel@vger.kernel.org
Subject: Re: HT Benchmarks (was: /proc/cpuinfo and hyperthreading)
Date: Wed, 18 Dec 2002 09:56:56 -0800 [thread overview]
Message-ID: <200212181756.gBIHuud27855@athlon.cichlid.com> (raw)
In-Reply-To: <1_0212161441436926@cichlid.com>
>Number of threads Elapsed time User Time System Time
>1 53:216 53:220 00:000
>2 29:272 58:180 00:320
>3 27:162 1:21:450 00:540
>4 25:094 1:41:080 01:250
>Elapsed is measured by the parent thread, that is not doing anything
>but wait on a pthread_join. User and system times are the sum of
>times for all the children threads, that do real work.
>The jump from 1->2 threads is fine, the one from 2->4 is ridiculous...
>I have my cpus doubled but each one has half the pipelining for floating
>point...see the user cpu time increased due to 'worst' processors and
>cache pollution on each package.
>So, IMHO and for my apps, HyperThreading is just a bad joke.
Why do you care about user time? The elapsed time went down by
4 minutes (2->4 threads), if that's a joke I don't get it :-)
New Intel Ad: "What are you going to do with your 4 minutes today?"
next parent reply other threads:[~2002-12-18 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1_0212161441436926@cichlid.com>
2002-12-18 17:56 ` Andrew Burgess [this message]
2002-12-19 22:04 ` J.A. Magallon
2002-12-16 15:11 /proc/cpuinfo and hyperthreading Måns Rullgård
2002-12-16 15:44 ` HT Benchmarks (was: /proc/cpuinfo and hyperthreading) Scott Robert Ladd
2002-12-16 22:38 ` J.A. Magallon
2002-12-16 23:21 ` Scott Robert Ladd
2002-12-16 23:27 ` J.A. Magallon
2002-12-17 11:03 ` Denis Vlasenko
2002-12-17 20:44 ` H. Peter Anvin
2002-12-16 23:50 ` H. Peter Anvin
2002-12-17 19:27 ` 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=200212181756.gBIHuud27855@athlon.cichlid.com \
--to=aab@cichlid.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
all inboxes | Powered by JetHome®