In some cases you may experience degraded overall performance on a Windows Server 2008 R2 or later machine when running with the default (Balanced) power plan. The issue may occur irrespective of platform and may be exhibited on both native and virtual environments. The degraded performance may increase the average response time for some tasks and cause performance issues with CPU-intensive applications.
Please note that you may not notice performance issues while performing simple operations. However, applications or scripts that intensively use resources (primarily processor and memory) may exhibit the problem. See More Information section for details.
This issue may occur if the Power Options settings are set to Balanced. By default, Windows Server 2008 R2 or later sets the Balanced (recommended) power plan, which enables energy conservation by scaling the processor performance based on current CPU utilization.
Option 1: Recommended
This issue is tied to interaction between the processors and the operating system not adjusting P-States and turning off Core Parking as needed. To address this it requires both hardware and operating system updates.
To work around the performance degradation issue, you can switch to the High Performance power plan. However, this will disable dynamic performance scaling on the platform. Depending on the environment, if the platform is always under a heavy load, then this is a viable solution. In most cases, however, the workload varies throughout the day and thus it is recommended to leave the power plan set to Balanced and evaluate the proper settings within the Balanced power plan for processor power management as described in the Processor Power Management in Windows 7 and Windows Server 2008 R2 paper located here:
Important: Today’s modern processors enable scaling of performance and power based on the current activity on the system. The different performance states are dynamically managed by Windows in conjunction with hardware and platform firmware to respond to varying workload requirements. The 3 default power plans exposed by Windows provide varying tradeoffs of performance vs. power consumption. For example, if the High Performance power plan is selected, Windows places the system in the highest performance state and disables the dynamic scaling of performance in response to varying workload levels. Therefore, special care should be taken before setting the power plan to High Performance as this can increase power consumption unnecessarily when the system is underutilized.
If the choice is made to change the default power plan, Windows Server 2008 R2 or later provides three power plans to maximize performance and conserve energy: Balanced (recommended), High Performance and Power Saver.
To change a power plan:
1. Click on Start and then Control Panel.
2. From the list of displayed item under Control Panel click on Power Options, which takes you to Select a power plan page. If you do not see Power Options, type the word 'power' in the Search Control Panel box and then select Choose a power plan.
3. By default, the option to change power plans is disabled. To enable this, click the Change settings that are currently unavailable link.
4. Choose the High Performance option
5. Close the Power Option window.
Processors change between performance states (“P-states”) very quickly to match supply to demand, delivering performance where necessary and saving power when possible. If your server has specific high-performance or minimum-power-consumption requirements, you might consider configuring the Minimum or Maximum Processor Performance State parameter. The values for both the Minimum and Maximum Processor Performance State parameters are expressed as a percentage of maximum processor frequency, with a value in the range 0 – 100. If your server requires low latency, invariant frequency, or high performance, you might not want the processors switching to lower-performance states.
For general guidelines on performance, consult the Performance Tuning Guidelines for Windows Server 2008 R2 paper located here:
Article ID: 2207548 - Last Review: 05/09/2016 15:42:00 - Revision: 8.0
var varAutoFirePV = 1; var varClickTracking = 1; var varCustomerTracking = 1; var Route = "76500"; var Ctrl = ""; document.write("