Comments on: A SQL Server Hardware Tidbit a Day – Day 27

By: Wayne Sheffield

Wayne Sheffield — Fri, 10 May 2013 15:36:37 +0000

You can check for CPU throttling with WMIC:
WMIC CPU GET Name, CurrentClockSpeed, MaxClockSpeed
If you want it to check every 3 seconds, just add /every:3 to it:
WMIC CPU GET Name, CurrentClockSpeed, MaxClockSpeed /every:3

On Windows 7 / Windows Server 2008R2 and newer, you can check the power plan setting (again with WMIC):
WMIC /NAMESPACE:\rootcimv2power PATH WIN32_PowerPlan WHERE “IsActive=True” GET ElementName

By: Paul Egan

Paul Egan — Tue, 30 Apr 2013 07:51:33 +0000

Hi Glenn,
I had to troubleshoot a problem recently were an agent job was running over an hour slower all of a sudden. After much searching I found that the server had been switched back into balanced performance mode. Switching back to high performance reduced run times by about an hour.

The process was inserting quite a bit of data nightly into some page and row compressed tables. It really does make quite a difference to performance.
thanks
Paul.

By: Glenn Berry

Glenn Berry — Mon, 29 Apr 2013 21:12:36 +0000

In reply to Chris F. CPU-Z shows what the VM sees of the world. The power management settings need to be set at the host level, and the VM will eventually inherit that.

By: Chris F

Chris F — Mon, 29 Apr 2013 20:36:42 +0000

How does running in a VM affect this? Is the CPU-Z information even accurate if you’re running inside a virtual machine?