Q: My 40-core server is capable of hyper-threading, so should I use hyper-threading with Windows Server 2008 R2 Hyper-V?

A: Hyper-threading provides some additional processing power by splitting a single core into two logical processors. However, these two logical processors aren't each as powerful as a normal processor core.

Windows Server 2008 R2 Hyper-V supports up to 64 logical processors, so a 40-core server, which is fairly easy with four 10-core processors, would be seen as 80 logical processors with hyper-threading enabled.

This would mean the last 16 logical processors (those over the 64 supported count), wouldn't be initialized by the OS kernel and would basically be parked. That is eight physical cores of processing power unused, almost a whole processor's worth.

It isn't possible in Windows to turn on hyper-threading for some processors and not for others--today, hyper-threading is enabled or disabled at the BIOS level.

The best performance option would, therefore, be to not enable hyper-threading and let Hyper-V use all the cores on the system, which would be seen as 40 logical processors.

Basically, any time hyper-threading pushes a server over the supported number of logical processors, which is 64 for Windows Server 2008 R2, then turn off hyper-threading.

This guidance is backed up by vendors such as HP, in its best practices document

Get more help at John Savill's FAQs page.

Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• The Microsoft
Technology Roadmap
• Office 365 Implementation
• Hyper-V Optimizing
• Windows 8 Deployment
and much more!

Come See Paul Thurrott & Rod Trent in Person!

Early Registration Now Open

Upcoming Training

Mastering SharePoint 2013: Succeeding, Not Just Surviving

Building on the success of the “Mastering SharePoint 2010” seminars, the presenters have updated the content to cover the latest and greatest SharePoint product: SharePoint 2013. While SharePoint 2013 is relatively new on the marketplace, the presenters have been working with SharePoint 2013 for well over a year, and have implemented it with a number of clients in production environments.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.