Like you said, no real-time effect when done via the registry, and other complications can arise.
Not completely right, at least it works for Power Plan setting, as it read the value after you launch it.
I has showing/hiding any PowerPlan setting on the fly via changing the registry many times.
And yes, it need to restart for any change to Software, Windows or Windows Kernel that is running and only read the registry when it is need to read(like boot up), not when the value is updated.
ParkControl does it right. Too bad it isn't more popular.
Also not completely wrong/right.
Based on Google, without any cookies and country limit.
- 'core parking' will getting at the second one, while the 'bad-tweak-core-parking' website will be on the tenth.
- 'disable core parking' will getting at the second one, and the coderbag will be third result.
If you put the 'disable' to back, the result will be a little difference too, the coderbag will be first one, while ParkControl on the third one.
- 'CPU parking' will be getting at the first one, as you has this word 'To disable CPU Parking completely' on that page, even Google will correct the keyword to core parking, Google will guess he remember that he read about 'CPU parking' this keyword on that page.
- 'unpark core' or 'unparked core' will be getting at the tenth or the fifth, and I don't know why, it can be the result that about parkcontrol result are having more same keyword.
Anyways, except for people that only open+trust the first Google result without even looking on the other result, I guess many smart guy that always dealing with Google will looking on the second+third result.
So it can be a good thing, which means that smart guy will not posting on the forum, asking about how to using ParkControl, even the guide showing how to use it.
And also less people will asking that, why 100% is disable core-parking, not enable core-parking, it is not bad to reducing the popularity for people that don't read/try to understand.
What is that NUMBER that is shown on the GUI? That is the % of cores that must remain *unparked*. So, if it's 25%, then 75% of the CPU's cores can be parked at once (3 of 4).
But, that example is a bad example too.
Because you will never getting 3 of 4 parked, you can only get 50% or half of the CPU get parked.
Except, you changed the setting of "Processor performance core parking core override" to disable, then it can park more than 50%.
And I also don't know why, as it is showing as
Specifies that at least one logical processor per processor core must always remain in the unparked state regardless of the values of the Processor Performance Core Parking Maximum Cores and Processor Performance Core Parking Minimum Cores settings.http://download.microsoft.com/download/3/0/2/3027D574-C433-412A-A8B6-5E0A75D5B237/ProcPowerMgmtWin7.docx
So I guess this setting get changed to 50% of CPU, not at least one logical processor, while disable this setting will make sure at least one logical processor remain unparked.
PS:Don't playing with this, unless you like to know more and know it might be causing strange issues.
Yes, it amazes me that people write programs that are so dumb. Doing a search and replace in the registry is absurd when there is a proper API. At the very least they could shell out to powercfg.exe to make the changes.
And yes, the side effect are still unknown, because many people report freezing, BSoD etc after using it, and it can be the wrong value of setting causing other setting that also controlling core-parking lost control, or the CPU, voltage, motherboard etc are having issues.