What’s the issue?
Windows Server’s default power plan is “Balanced,” which dynamically throttles CPU clock speed down during lower utilization to conserve energy and ramps it back up when demand increases. A processor rated at 3.0 GHz may run at 1.2 GHz or lower when the system appears idle, with the CPU only ramping up after load is sustained.
Why is this a problem?
The CPU ramp-up is not instantaneous, and SQL Server’s typical OLTP workload with short, bursty queries often completes at throttled clock speeds before the processor ever reaches full speed. This causes measurable performance loss, commonly 20-25%, and shows up in wait statistics as elevated SOS_SCHEDULER_YIELD and high signal waits that look like CPU pressure but are actually a configuration problem. Queries take longer, throughput suffers, and troubleshooting efforts often get misdirected toward query tuning when the real fix is at the host level.
What should you do about this?
Verify the current plan with powercfg /getactivescheme from an elevated command prompt. Set the plan to High Performance via Control Panel > Power Options, or with powercfg /setactive SCHEME_MIN. Also check the server’s BIOS/UEFI power management settings — if these are configured for OS control or power saving, they can override the Windows setting, so set them to maximum performance or “OS Control” as appropriate. If your environment enforces Balanced power via Group Policy, request a GPO exception for SQL Server hosts.
Read more…
SQL Server Health Check Worst Offenders – SQL Server Consulting – Straight Path Solutions
