On the power schema stuff inclusive to windows. All of the following apply on Win 10.
On these CPU's e-cores never get parked by default, only p-cores. (but is adjustable on the hidden power schema setting)
Independent performance hint mechanism for p and e-cores.
E-cores (only applicable if using hardware p-states aka speedshift)
Subgroup / Setting GUIDs:
54533251-82be-4824-96c1-47b60b740d00 / 36687f9e-e3a5-4dbf-b1dc-15eb381c6863
Default value for schemes:
Balanced: AC=33
Power Saving PC: AC=60
High Performance PC: AC=0
Ultimate Performance PC: AC=0
P-cores (only applicable if using hardware p-states aka speedshift)
54533251-82be-4824-96c1-47b60b740d00 / 36687f9e-e3a5-4dbf-b1dc-15eb381c6864
Default value for schemes:
Balanced: AC=33
Power Saving PC: AC=60
High Performance PC: AC=0
Ultimate Performance PC: AC=0
Min and max performance based on %, its not a granular linear increase though, and turbo clocks is all put in one single %, (99% is max non turbo clocks, 100% is max turbo clocks).
E-cores for this is visible by default in power settings. (min/max processor state)
P-cores, min performance.
Subgroup / Setting GUIDs:
54533251-82be-4824-96c1-47b60b740d00 / 893dee8e-2bef-41e0-89c6-b55d0929964d
Default value for schemes:
Balanced: AC=5
Power Saving PC: AC=5
High Performance PC: AC=100
Ultimate Performance PC: AC=100
P-cores, max performance.
Subgroup / Setting GUIDs:
54533251-82be-4824-96c1-47b60b740d00 / bc5038f7-23e0-4960-96da-33abaf5935ed
Default value for schemes:
Balanced: AC=100
Power Saving PC: AC=75
High Performance PC: AC=100
Ultimate Performance PC: AC=100
A second min % performance setting for e-cores that applies when at least one p-core is unparked (so the default one only applies when they all parked). This means that by default windows 10, will be max turbo clocks for all e-cores if "any" p-core is unparked regardless of load on the system. However reducing max should override this as a maximum, so if e.g max is 99, then they will always be at max non turbo clocks if any p-core is unparked. This will allow them to downclock below max if reduced.
Subgroup / Setting GUIDs:
54533251-82be-4824-96c1-47b60b740d00 / fddc842b-8364-4edc-94cf-c17f60de1c80
Default value for schemes:
Balanced: AC=100
Power Saving PC: AC=100
High Performance PC: AC=100
Ultimate Performance PC: AC=100
Speculative clock boost setting (shared for both p-cores and e-cores), its not linear, 0,30,60,100 seem to be the only values that matter from my testing. Anything above zero makes clock's increase aggressively under the tiniest of loads. Only applies when using hardware p-states aka speedshift.
Subgroup / Setting GUIDs:
54533251-82be-4824-96c1-47b60b740d00 / 45bcc044-d885-43e2-8605-ee0ec6e96b59
Default value for schemes:
Balanced: AC=60
Power Saving PC: AC=0
High Performance PC: AC=100
Ultimate Performance PC: AC=100
To control min amount of unparked e-core's, 100 means not allowed to park any cores. Is percentage value.
Subgroup / Setting GUIDs:
54533251-82be-4824-96c1-47b60b740d00 / 0cc5b647-c1df-4637-891a-dec35c318583
Default value for schemes:
Balanced: AC=100
Power Saving PC: AC=100
High Performance PC: AC=100
Ultimate Performance PC: AC=100
All of these settings change on the fly, no reboot needed.
On a different forum someone told me Windows 11 apparently treats e-cores and p-cores as the same performance class in all the power schema stuff (which to me seems odd, but since I hate 11 I never bothered to verify if its true personally).
I can see on the net throttlestop is very popular, and I have been using it as recent as today and yesterday on an alder lake N100 on a NUC I have (no options at all in bios for anything).
Since the N100 only has one type of core that seems to behave as expected using throttlestop.