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).
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.
There's also plenty of time where the system has low intensity use or is idle. The efficiency cores let things like receiving notifications or checking e-mail happen for very little power draw. Fans only need to run during intense use and the system can be quiet the rest of the time.
This is a bigger deal than it might seem. Fans running means that dust is accumulating in the machine at an accelerated rate, even if you have filters in place. The less the fans have to run, the less dust accumulates, and the longer cooling functions near-peak. A tower that sees sporadic heavy usage especially stand to benefit from fan minimization.
Who knows, maybe the UI thread only needs access to the graphics card, and the background thread only access to network. It would save a lot of interrupt loops.
See, for example, this article from yesterday: https://eclecticlight.co/2021/05/17/how-m1-macs-feel-faster-...
Long story short, segregating background work from foreground work means that Spotlight indexing won't cause the UI to become sluggish. I'm guessing it also tends to be more cache-friendly.
At the end of the day you will still need HE Core, they just aren't as important comparing to a Battery devices.
Not to mention Marketing, Die Size cost consideration.
The design challenge of high-performance CPUs today is heat. Too much heat induces throttling. Putting low-priority stuff onto efficiency cores reserves the power budget of the SoC for high-priority tasks.
https://arstechnica.com/gadgets/2021/05/apples-m1-is-a-fast-...
How many is optimum is an interesting question, I would assume the apple peeps have a good idea and are on the money with this design.
At some point it's more efficient to have a single performance core going than a number of efficiency ones.
They do up to 8 on the big CPU according to rumor, so there's obviously some room there.
Someone who doesn't need more performance cores is unlikely to invest in a Mac Pro.
There's a lot of software that won't scale to 108 cores, of course, but again I expect the amount of software that could usefully scale to 40 parallel threads but can't scale to 108 to be fairly small.
In a world where power and heat budgets don't matter at all you'd not have any efficiency cores, after all.
<math>S_\text{latency}(s) = \frac 1 {(1 - p) + \frac p s}</math>
Bad assumption. It's pretty difficult to write a multithreaded program that scales up to 32 cores. You have to carefully avoid all sources of process-wide contention. The only cases where it is easy to just keep adding cores are where the units of independent work are overwhelmingly large compared to everything else, like video compression.
- 20 total, 16 high performance, 4 efficiency
- 40 total, 32 high performance, 8 efficiency
Which is kind of interesting given that the 8 core M1 is split half/half at 4 high performance, 4 efficiency.
Sounds like perhaps MacOS doesn't typically have more than 4 cores worth of low-priority work, regardless of the system size/workload?