![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Technical Instruction Sure Solution 1003411.1 : Hyper-threading and the Sun Fire[TM] V60x and V65x
PreviouslyPublishedAs 204785 Applies to:Sun Fire V60x Server - Version Not Applicable and laterSun Fire V65x Server - Version Not Applicable and later All Platforms ***Checked for relevance on 14-May-2012*** GoalAllow customers to best choose the Hyper-Threading configuration for their operating environment and applications. FixEnter the Main Content
Hyper-threading is a recent technology that Intel has incorporated into the latest ATOM, Pentium 4, Core i and Xeon Server CPUs. Hyper-threading allows the scheduler to hand a CPU 2 separate program instructions simultaneously. Hyper-Threading, sometimes also referred to as simultaneous multithreading (SMT), allows different threads to run simultaneously on different execution units within one physical processor. Hyper-threading is not the same as having a multi-core CPU. Multi-core CPUs are many true CPUs mounted in the same casing, allowing much higher CPU densities. Both Sun and Intel have other CPU products with multi-core support. Hyper-threading is an enhancement to the scheduler that allows the CPU to pretend to be multiple CPUs to optimize how instructions are processed. This technology has its roots in development done by engineers who were working on incorporating it into future versions of the Alpha processor.
Sun legacy Intel x86-based servers, the Sun Fire V60x and V65x, use Intel Xeon processors that are Hyper-threading capable. However Hyper-threading is not enabled by default. Should the customer wish to enable Hyper-threading, the process to do so is simple:
When can Hyper-threading improve application performance Hyper-threading improves performance primarily for single applications that are multi-threaded or systems that run multiple services. The improvement is quoted as being anywhere between 30% and 90% for heavily threaded applications, especially if they have been optimized to run on a Hyper-threading enabled CPU. In some cases it may be more beneficial to have Hyper-threading disabled as most x86 applications today are typically not threaded or hyper-threading optimized. This is usually done through turning off Hyper-threading in the BIOS (this is done by default on the Sun Fire V60x and V65x). A couple of examples where this may be desirable:
Older operating systems may falsely interpret the Hyper-threading CPU as 2 physical CPUs. Even with a modern operating environment that properly recognizes it as 2 logical CPUs, applications need to be updated to understand the concept of logical processors. Otherwise applications that are licensed based on the number of physical CPUs may improperly assume that the operator has violated the license. In some cases the software may cease to function. Which major x86 OSs make use of Hyper-threading today
Attachments This solution has no attachment |
||||||||||||
|