The E-core magic trick is that they are always running and also exist to prevent thread stoppers, tasks that force you to pause high-priority work such as network requests, push notifications, or memory management. This enables a machine where the performance cores can pound away at tasks uninterrupted and your cache can stay dedicated to the task at hand, preventing situations where you may have to dump branches mid-process, increasing performance consistency. Mathematically, it works out to where the P cores are ~5.2W each and then the E-cores are less than that combined, allowing the system to idle on just e-Cores and spin up and dedicate P-Cores to the UI and UX intensive tasks, keeping the thermals low and performance high. In a situation like the Mac Pro, I would expect much, much hotter P-Cores too as the thermals will allow.
https://eclecticlight.co/2021/05/17/how-m1-macs-feel-faster-...
<personal rant>
I'd swear that Spotlight indexing would prefer a freaking supercomputer when it runs.
My whole system just starts to feel sluggish, especially if I just moved a bunch (say 1-5GB) of files onto my system and not it wants to index them.
</rant>
I know people say this all the time, but the reality is modern web browsers are incredibly expensive processors.
There was a moment in web history when the same happened due to the flash-based ads which easily spent huge amounts of CPU for... nothing meaningful to the reader. Now the flash is gone, but the pattern repeated.
And even not counting all the ads, today's "hot" web development conventions are often making the CPU even hotter.
It's like there's this assumption that the web's simple serving of HTML was a compromise of the time rather than it's killer feature.
I don't want to sift through hundreds of images and outbound links from the ads you're trying to trick me into clicking, I just want the information I came for or I'm gone forever.
The efficiency cores are essentially for when the system is idling or for the 95% case (browsing the web, watching YouTube and checking e-mails). If a task is performance-bottlenecked then it makes sense to go straight to maximum performance rather than any in-between combination as you're essentially either waiting for the computer or not (i.e. it probably doesn't make much sense to try to strike an efficiency balance for tasks that are stressing a minimal set of low-power cores when they need to be completed either way - and in a machine where there's no battery life to worry about).