Wednesday, March 7, 2012

hyperthreading disabled?

Hi, can anyone tell me if it's possible to see the current hyperthreading value without going into the bios? registry key perhaps?

We have a very crooked system here and I do not have full access to the system. Thank you all for you all your help in the past! and the future!!

You could use 'Task Manager', and look at the [Performace] tab. (On the [View] menu, select [CPU History] and make sure the [One Graph per CPU] is checked.

If Hyperthreading is enabled, there will be 2 CPU Usage History graphs per physical CPU in the box.

|||what if there were two physical chips in there? wouldn't that still show 2 graphs?|||

i'm trying to determine how many actual chips there are.. is this doable without rebooting?

|||

With Hyperthreading enabled, two physical chips will display four CPU History graphs.

The [CPU History] graph displays for 'logical' chips. Hyperthreading makes two 'logical' chips from one physical chip.

|||

Which version of SQL Server are you using? If you are using SQL Server 2005 then you can query sys.dm_os_sys_info to find if you have a hyperthreaded or multi-code CPU. See the blog article below for the details:

http://blogs.msdn.com/sqltips/archive/2005/09/14/466387.aspx

Or download and install Process Explorer from the link below. You can then go to System information dialog, hover over the CPU usage graphs on top and they will show you if the processor is in the same core or not. See the utility for more details.

http://www.microsoft.com/technet/sysinternals/SystemInformation/ProcessExplorer.mspx

These are the easy methods. You can also type SYSTEMINFO in the command-line and use the processor description from their to figure it out. But this will require looking at Intel/AMD documentation for example to figure out the family of processors etc.

|||

Umachandar,

As I recall, the method descibed can't discern between Hyperthreading and Multi-core.

|||Yes, I mentioned it is for multi-core or hyperthreaded CPUs. Best is to install Process Explorer.

No comments:

Post a Comment