As I mentioned in my previous post, for me this is not preferable on Win 10, and actually not acceptable, because with E-cores enabled, all cores constantly run at max frequency and voltage, but at the same time core parking seems to be turned on with most P-cores getting parked and all E-cores being constantly active.
Clearly this system is confused about how to operate these CPUs.
Yeah, I did read more about that. Even though technically you can turn them all off in the BIOS, 1 always remains active.
It isnt confused it is by design, and these behaviours you specified are in the CPU scheduler settings.
By default cores are set to min 100% unparked (this is cores on normal CPUs like 9900k and AMD chips, and e-cores on hybrid CPUs), when using hybrid CPUs the default min unparked is set to 0% for p-cores.
Apps like games and benchmarks will unpark p-cores as well as various desktop apps. The preffered p-cores will always be the first to unpark, it isnt random. In addition logical cores can be parked independently, so e.g. cores stay HTT free until all p-cores are unparked and then the second logical core on each p-core will become available if the system needs it.
This is pretty cool as it leads to a lot of background processes and services utilising the e-cores freeing up p-core resources for CPU demanding interactive tasks.
This behaviour is configurable either via registry editing or using a tool like powersettingsexplorer (no spaces), I have e.g. set p-cores to min 10% unparked so the preferred p-cores are always unparked, you can choose to set it to 100% and it would have the behaviour you desired without disabling the e-cores, however I didnt personally do this because it increases vcore for lighter loads and as such reduces efficiency, and I noticed no interactive benefit.
These things that can be tinkered with are quite fascinating, but a very quick adjustment would be to simply adjust min p-core unparked %, set the heterogeneous scheduler to prefer p-cores and use something like process hacker (system informer) to save persistent affinity settings for things like browsers and svchost to e-cores.
If you like I can post a power policy with these two adjustments, based on high performance schema but with these two changes (min p-core unparked 100% and het* prefer p-cores).
--
Additional note, I have yet to examine the default behaviour on Windows 11, so I dont know specifically if any of the above things I stated had their defaults changed, obviously aware of the intel thread director addition as mentioned in TPU's reviews.
