|
|
|
|
|
|
by dijit
239 days ago
|
|
|
Yeah, it's specifically Windows 11 that has this issue. I'm not certain as to why, if I had to speculate it would be the new scheduler prefers the efficiency cores and then thrashes the L1/L2 cache as soon as there's any actual work to do in the operating system (IE; you clicked something) by putting it on a performance core. Windows 11 performance seems to be less terrible on devices that don't have big.LITTLE architectures. |
|
|