Intel has been saying this for years, like almost 8 years. But this is just what non-innovator say. It is an excuse for mediocrity and failure and stagnation.
There is tons of uArch improvements in Apple's chips. That is why they consistently beat even the other ARMs chips on the same process nodes.
AMD also has been significantly innovating with uArch.
I love the innovation we are seeing these days. We are definitely not in an TDP era (where only TDP matters! but of course TDP is important), we are in another golden age of CPU/GPU innovation and it is beautiful. Reminds me of the 1990s and early 2000s.
Intel is basically running a super legacy design and they are doing surprisingly well with it, but they are losing on all fronts at this time. What they have for them right now is momentum and enterprise deals.
That will hold up for a while yet, so it gives them time to get their act together.
The A13, Qualcomm Snapdragon 865, and Mediatek Dimensity 1000L were all on DUV N7P (Hisilicon Kirin 990 5G was actually on the more advanced EUV N7+). For more information on chips and their processes: https://www.eetimes.com/apple-huawei-use-tsmc-but-their-7nm-...
Here are some benchmarks of how the A13 and 865 (and the 2020 updates) stack up: https://www.phonearena.com/news/apple-a14-vs-a13-vs-snapdrag...
From the charts, it looks like particularly for single-core and browser/JS performance, the Apple designs are very strong, and beat out the Qualcomm competition even on the same process node.
According to Wolfram Alpha, 5 nanometers is ~23 silicon atoms across (~2.2 Å each). But that’s also assuming they’re actually fabricating 5 nm gates - which they’re not.
The oxide/insulator thickness on modern process is pretty insane. For instance for the intel 14nm++ the silicon nitride and silicon oxide layers seem to 4 to 5nm thick.
-Edit- For instance here is 2 fins for from the intel 14nm++. The grains/spheres you see this image are the atoms. Some parts of the a modern transistors are even smaller than process number may let you know.
> We are back to TrashCan Mac Pro again... we would have reached the thermal ceiling again...
This is kind of drawing new lines to read between. :)
Apple almost certainly developed their current uber-expensive, trypophobia-triggering Mac Pro design knowing that they were also working on Apple Silicon processors. While it's possible they intend that whole case design to be a one-time thing, it doesn't seem likely to me -- and if that wasn't the intent, then it's also not likely they want to ship a teeny tiny Apple Silicon logic board in that huge case with the rest of the space going unused. I think they're going to do their best to make an Apple Silicon-based Mac Pro that can be upgraded and expanded. (With all respect to Mark Gurman, I think that "half-sized Mac Pro" is going to be a different product entirely if it ships, with a different branding. Mac Mini Pro?)
The ever illusive xMac, aka "the affordable Mac tower"
The iPad is at least an order of magnitude better than comparable netbooks (though chromebooks, depending on manufacturer, can be competitive thanks mainly to ChromeOS's reduced footprint). So even though the margins are high, the perceived quality, regardless of raw benchmarks, is still something. It's not just marketing to me to say the marriage of software and hardware is unique. (Gruber's observation about NSObject alloc's being a lot faster on Apple Silicon, for instance).
Now that I think about it, honestly Google is the only other company playing by these rules... ie pixelbook, pixel phone, etc. But they're much earlier in the evolution, and have less upstream control in software (especially since Fuchsia seems to be somewhat lower priority than before, though this is second hand knowledge).
As a technology enthusiast I'm excited to see what bonkers stuff they'll be announcing. But, since I am not doing climate models or rendering hollywood movies, I don't expect I will never work on any of them since I don't want to drop a new car's worth of money on one.
No, but unified memory does require starving the GPU of bandwidth. There's a reason high end GPUs use different types of memory than CPUs.
Either Apple will be content with Mac Pro not having the absolute graphics performance lead, or they will make a discrete GPU with dedicated memory. I'm not sure which they will choose but I suspect the latter.
There doesn't seem to be any reason why Apple couldn't integrate a 16 TFLOPS GPU on an SOC using a 5nm or better process. The M1 GPU is 2.6 TFLOPS, they can x6 or more it, and obviously change the memory subsystem (HBM?).
Also, Xbox uses GDDR which trades off CPU performance for GPU performance. Apple probably wouldn't do that for a Mac Pro. The high end needs separate memory so the GPU can have bandwidth and the CPU can have low latency.
Also, GDDR does not have appreciably higher latencies than DDR memory when measured in nanoseconds. It's just more expensive than DDR and much more limited in terms of capacity.
If Apple does go the "huge SoC" route I'd expect to see HBM2 memory with socketed DDR4 or DDR5. It'd provide the best of both worlds - extremely high bandwidth and low latency for a small portion (say 32-64GB) of the memory, and high capacity for the rest (say 1-2TB), all without compromising the unified memory concept.
This is not without precedent - recent Xeon Phis, for all their other shortcomings, have had a similar memory hierarchy.
I agree that a combination of HBM and DDR sounds pretty good for a unified memory architecture. Are you imagining it as just another layer in the cache hierarchy or something actively managed?
So you get a certain baseline level of specs, but also have the opportunity to tack on a beefier GPU (which may or may not use UMA), additional slower memory, additional slower storage, maybe even additional CPUs, etc.
I don't think so, with the asterisk that I don't know enough to say whether mixing higher-speed and lower-speed RAM is really feasible in that scenario. (IIRC, if you do that in computers now, all the RAM will operate at the lowest speed.)
That’s correct, but irrelevant in this context. In that scenario, the memory is all on the same memory controller, and the memory controller used wants to run a single speed, so it has to be the highest universally supported speed.
Apple could have multiple tiers of memory with different characteristics, but just because you can, doesn’t mean you should. I don’t have access to such a test bed, so I can’t speak to what the experience would be like.
The Radeon Vega II Due has 128 compute cores and 8192 stream processors, so that maxed out mac pro would have 256 compute cores and 16384 stream processors. I don't have any benchmarks to work off of, but I think it's safe to say that a new Mac Pro with the 32-core SoC would still be substantially far behind a current Mac Pro unless it also had a dedicated GPU.
[1] https://www.anandtech.com/show/15885/hpc-systems-special-off...
The advantage of GPU having it's own memory is you can use super high throughput ram that the GPU needs, while using higher capacity/lower energy/cheaper ram for the cpu.
The downside of using separate ram is that you have to shuttle data back and forth from one ram to the other quite a bit, as well you get less flexibility in how your total memory is used.
It's more likely that the future Mac Pro will use Lifuka which everyone in this thread is ignoring.
It would be interesting if Apple did make a discrete GPU, that would means they are making a separate GPU die for their Mac Pro and iMac with volume estimated to be no more than 1M unit per year. It makes sense from a technical perspective, it surely doesn't from a cost perspective. Although Apple could happily charge $1000 just for the GPU to make up for ROI.
That is unless Apple decide to use DRAM in additional to HMB or GDDR5 as 2nd layer of Memory.
Who do you think writes all the code for this stuff? It’s guys in tracksuits in Visual Studio C++ on Windows. The top games for iOS are also either written by a few guys in Unity or by an absolutely huge team of people porting an existing, low graphics quality PC game.
i.e UMA ( Unified Memory Architecture ), GPU, NPU stay intact. You are basically getting a M1XX, where M1X is the 16 CPU Core variants.
Consider the current M1, a 32 Core High Performance CPU Core and 128 GPU core would give you roughly 300W TDP Max, excluding all the memory controller and interconnect. A rough estimate is already at 500mm2+ Die Size, excluding NPU and all other bits and pieces, of course assuming the same processing node.
The Old ( Or the recent ) Mac Pro has a Maxed out system of ~910W, that is 28 Core CPU + 2 x Radeon Vega II Duo ( That is 4 GPU ).
We are back to TrashCan Mac Pro again, except it would be even faster than the 2019 Cheese Grater Mac Pro. We would have reached the thermal ceiling again, unless Apple does Water Cooling and push that TDP allowance to 400W.
Remember this M1XX is CPU + GPU TDP. For a PC system, or workstation power users are quite used to 300W CPU + 300W GPU. So I was sort of expecting Apple to be making CPU + GPU design, purely to create a monster as a successor to Cheese Grater Mac Pro. May be they have different Goal in mind, may be they think this is good enough for Mac Pro ( Which certainly is from many perspective ), and obviously iMac.
Same Design, scaling across iPhone, iPad, MacBook, And Mac Pro.
This brings me to the final point, we only have so much uArch improvement we could do, it is now all left to process node and heat dissipation of the system.
We are in the era of TDP Computing.