First of all, thanks for thinking with me! Yes, thanks I know that. Ryzen 5 2600 has 3 P-States: with max set at 100% it uses the max available state (<=3.4GHz), and by setting it to 99% it's forced to use the state below (<=2.8GHz, and it's enough for me); the next (and last) percentage value is 81% (~ <=1.6GHz). Thanks, I didn't know that. Although I noticed that Ryzen-balanced plan turns off core parking. Hmm, I'll play with it then. OK, but only for "performance increase policy" not "performance decrease policy" (the latter works the other way around). That's what I thought, thanks for the confirmation. Hmm, although I don't think this works this way. Increase threshold: "Specify the upper busy threshold that must be met before increasing the processor's performance state (in percentage)." Decrease threshold: "Specify the lower busy threshold that must be met before decreasing the processor's performance state (in percentage)." The defaults for these 2 in % are (e.g. diff between HighPerf plan is only 20): - increase: Saver: 90, Balanced: 60, High: 30, Ryzen: 25, mine: 80 - decrease: Saver: 60, Balanced: 20, High+Ryzen: 10, mine: 40 This is how it works (at least how I understand it): - increase: a given state has to reach the specified utilisation to be allowed to enter a higher state - decrease: a given state has to drop down to the specified utilisation to be allowed to enter a lower state Thanks for mentioning, I left out this one for whatever reason. That is I wanted to achieve with my settings (apart from the idle check), I used: - 30ms for "performance time check interval" - 2 perf checks for "performance increase time": meaning 2*30 = 60ms - 1 perf checks for "performance decrease time": meaning 1*30 = 30ms At least this is how I understand how it works (I can be wrong with this one).