6 ms·
It says the split for performance versus efficiency cores will be: - 20 total, 16 high performance, 4 efficiency - 40 total, 32 high performance, 8 efficiency
by tyingq 6y ago
It says the split for performance versus efficiency cores will be:
- 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?
- bombcar 6y agoIt seems obvious once you look at it - the "efficiency" mode is almost a quasi-sleep and so it makes sense to only dedicate a certain number of processors to it (as every efficiency core could in theory have been a performance core).
- cesaref 6y agoThe OS appears to partition the processors, like linux cpuset stuff, with low priority threads getting given to the efficiency cores, so you basically keep the low priority background stuff off the performant cores. 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.
- leetcrew 6y agoit's not clear to me why the optimal number of efficiency cores wouldn't be zero on a desktop. why not just use the die area for additional performance cores? one or two full cores shouldn't have much effect on the thermal/power budget if they're just working on background tasks.
- jwhitlark 6y agoI suspect heat is a bigger problem than you're assuming, but also, you would want a similar architecture to simplify the os code.
- tyingq 6y agoPerhaps. It wasn't obvious to me. I thought things like non-active browser tabs and various background daemons would easily occupy more than 4 efficiency cores. Though I suppose that has a lot to do with how they are implemented.
- bombcar 6y agoI assume they optimize Safari for this, and I'd think they'd be much more likely to quiesce a background tab (and let it swap out) than to keep it running at a slower speed. 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.
- deleted 6y ago[deleted]
- oneeach 6y agoConsider the use cases. The Mac Pro is a desktop, always plugged in and used for the power. The M1 is on a laptop running on a battery where efficiency is more important to improve the battery life.
- 988747 6y agoSo why put efficiency cores in the desktop processor at all?
- aequitas 6y agoIt still nice to reduce power consumption and heat production when running idle.
- giantrobot 6y agoA desktop runs a lot of low priority processes. The efficiency cores can be given all those processes. This means some low priority thread will get scheduled on a performance core and bust the cache. 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.
- laurent92 6y agoThe guys have split the traditional UI thread and the background thread down to the silicon. 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.
- kitsunesoba 6y ago> 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.
- deleted 6y ago[deleted]
- headmelted 6y agoThis is what I would have expected - I suggested when the M1 was first mentioned that it might make more sense for the Mac Pro to just have a side wall of separate independent SOC stacks with independent on-thread memory that GCD could manage behind the scenes. This seems like a much more straight-forward way to throw more performance into the higher-end machines without making long-tail disruptions to the architecture. 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).
- andrewmcwatters 6y ago> browsing the web, watching YouTube I know people say this all the time, but the reality is modern web browsers are incredibly expensive processors.
- acqq 6y agoYes, and it's also because a 2 KB text today comes inside of megabytes of code that has to be executed, and some code is additionally very expensive to execute, as it's doing shady stuff in trying to fulfill all the promises of all ad companies involved, sometimes really hundreds for a single page. 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.
- headmelted 6y agoThis right here. 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.
- philwelch 6y agoA performance-focused workstation would have more performance cores because it’s being used for more CPU-intensive work. If you don’t actually need that many performance cores, you’d buy a Mac Mini instead.
- Symmetry 6y agoThat seems a bit weird to me. Many programs are hard to multithread but I'd expect that if any given program can make effective use of 8 threads it can probably keep scaling to 16 and 32. The hard part is getting from 1 to 2 and 2 to 4. So I'd expect that in most cases having more than 8 high performance cores doesn't make that much sense.
- kungito 6y agoAmdahl's law can be formulated in the following way: <math>S_\text{latency}(s) = \frac 1 {(1 - p) + \frac p s}</math>
- Symmetry 6y agoThat's tautologically true but the question is what the distribution of p is over the 0-1 interval for real world programs.
- bombcar 6y agoA Mac Pro is likely to be dedicated to those workloads which ARE easy to thread - video editing and processing - or simply have multiple applications running simultaneously. Someone who doesn't need more performance cores is unlikely to invest in a Mac Pro.
- thinkingemote 6y agoMacs are primarily well designed consumer devices, status symbols and objects of brand loyalty. These factors will push sales beyond a basic functional need.
- Symmetry 6y agoI'm confused at this response. My thought is that instead of 32 high performance cores and 8 efficiency cores it might be better to have 8 high performance cores and ~100 efficiency ones which ought to be about the same area and power but provide a lot more throughput if software can utilize that level of parallelism. 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.