RE: Hyperthreading

James Bourne (jbourne@MtRoyal.AB.CA)
Wed, 17 Apr 2002 19:21:55 -0600 (MDT)


On Wed, 17 Apr 2002, Martin J. Bligh wrote:

> > I've seen some Intel bench's and they are specing an increase of 0% to 30%
>
> I think I'd be less cynical about benchmark results that didn't come from the
> people trying to sell the product ;-)
>
[...]
> Real world benchmarks from people other than Intel should make interesting
> reading .... I think we need some more smarts in the OS to take real advantage
> of this (eg using the NUMA scheduling mods to create cpu pools of 2 "procs"
> for each pair, etc) ... will be fun ;-)

Well, here I have some.

The tests involved kernel compiled (2.4.18) from a make mrproper, single
nbench, and unixbench (likely the most useful).

The output from tests can be found at http://www.hardrock.org/HT-results/

Results consist of (all with hyperthreading on and off):
o timed make bzImage and make modules using -j2 -j4 and -j6.
o BYTEmark output (single run)
o BYTE UNIX Benchmarks (Version 4.1.0) log, report, and times
o output from /proc/cpu
o output from /proc/interrupts
o output from dmesg (sorry, one of them has the top clipped).
o output from lspci -v

many concurrent tasks then hyperthreading makes sense. Many
concurrent systems (the -j4 and -j6 kernel compiles for example)
do see improvements. Although this is not a very analytical test, I don't
have time for 10 iterations of each to get a better set of numbers.

Thanks to all and regards,
James Bourne

>
> M.
>

-- 
James Bourne, Supervisor Data Centre Operations
Mount Royal College, Calgary, AB, CA
www.mtroyal.ab.ca

****************************************************************************** This communication is intended for the use of the recipient to which it is addressed, and may contain confidential, personal, and or privileged information. Please contact the sender immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communication received in error, or subsequent reply, should be deleted or destroyed. ******************************************************************************

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/