This section will describe some details and/or differences about the performance adjustment on HWP enabled systems. It's important to mention that the behaviour described on this page is not relevant to every system with enabled HWP. However, for some platforms with Intel CPU code name Skylake or greater adjusting application settings such as Frequency Scaling and Turbo Boost on the main form might not deliver expected results.The reason for such behaviour is enabled by default HWP (Hardware controlled performance) settings.
Imagine you have a CPU with the base frequency of 2.6GHz and the max possible turbo frequency of 4.3 GHz. By setting Frequency Scaling and Turbo Boost setting to a 100% mark on the main form you would expect your CPU clock speed to be close to the max turbo values of about ~4.15 GHz (depending on the heat, active cores etc..) at all times. Instead you'll notice that CPU clock is nowhere near Turbo frequencies and still fluctuates from low to high values depending on the CPU load and other factors.
One obvious solution to this problem for HWP (hardware controlled performance) enabled systems would be to max out HWP limits, by setting both minimum and maximum performance indicators to their maximum values in the available range. However, in some cases you might discover that HWP settings are being reset to their base (default) values immediately after being set to maximum. I didn't have a chance to research whether it was done on a software level by Windows OS or on the hardware level. The good news is that there’s a way to fix this.
Even though manually applied HWP changes are getting reset to their default values, it is possible to solve this problem by setting both Turbo Boost and Frequency Scaling setting on the main form to the 100% value (and apply changes). After it's done you can finally adjust HWP setting in any way you like without worrying about them being reset to system default. That being said by doing this you can control your CPU clock ranges from the very minimum to the maximum ranges, despite the fact that Frequency Scaling and Turbo Boost values are set to 100% (see picture #2), since HWP is taking over the control.
As I mentioned before, the behavior described above was not discovered on every system with Skylake + CPU and HWP enabled. To be specific it was seen on 2 test machines with Skylake and Kaby Lake CPUs, and few cases reported by the users. Another test machine with Kaby Lake CPU and HWP enabled was acting in a normal way . All tested systems have Win 10 x64 installed.
About Our Software
Enhance and monitor system performance, customize favorite settings and more…