Quote from: Jeremy Collake on Yesterday at 06:29:27 AMWe'd really have to dig into this to give you a certain answer. It is strange that you can't achieve close to the same results that you had when disabling E-cores at the BIOS level, but as you mentioned, Windows thread scheduling on these platforms is a mess.
What power plan (or mode) are you in? If not already, switch to a high performance plan to help dissuade Windows from making use of the E-cores. You can use ParkControl to check the heterogenous scheduling settings for the power plan.
Quote from: Jeremy Collake on May 17, 2024, 03:00:07 PMWhat analysis software is this?
QuoteFirst, let's ensure you've checked menu item 'Options / Forced Mode (continuously reapply settings)', in case that software is managing its own affinity.
QuoteWith the E-cores removed by affinity, the total CPU % is going to be limited since only the P-cores can be used. In contrast, when you disabled the E-cores in the BIOS, the CPU consumption could reach 100% since the E-cores were not included in the total available capacity.
QuoteYou should also check for any thread count setting in the analysis software and set it to the total number of P-cores threads you have available (2x the P-cores). Otherwise, it may launch too many threads for the constrained CPU affinity to cope with.
How is the analysis time after the rules you set with Process Lasso?