Let's hope Qualcomm's SoC can put pressure on Apple.
Let's hope Qualcomm's SoC can put pressure on Apple.
The gains from Gen3 to Gen4 are really tiny considering that Nuvia cores are completely custom, and they're using N3.Let's hope Qualcomm's SoC can put pressure on Apple.
Let's hope Qualcomm's SoC can put pressure on Apple.
What improvements does TSMC N3/N3E bring over TSMC N4P?The gains from Gen3 to Gen4 are really tiny considering that Nuvia cores are completely custom, and they're using N3
What improvements does TSMC N3/N3E bring over TSMC N4P?
Until we se the first real products, will be hard to judge..Does anyone know how big the Gen 4 dies will be? Compared to M2 Or what can be expected with an M3 die shrink?
That 3,472/13,676 seems reasonable compared to rumored A17 scores of 3.019/7,860.Out of curiosity, is there any way to transform GB5 scores into GB6 scores and vice versa?
Out of curiosity, is there any way to transform GB5 scores into GB6 scores and vice versa?
Yes.Does any of these figures have merit?
Does it make sense that M3 wins in single-core by such a margin to Qualcomm's SoC, but loses in multi-core?
What configuration could 8cx have to reach 1800 in single-core and 14000 in multi-core?
What configuration could M3 have to reach 2500 in single-core and 11000 in multi-core?
Would such a leap between M2 and M3 be possible?
I calculated to 2600. Just 100 of the tweet. But maybe the Pro or Max versions can reach 2600.I expect M3 to show a much bigger improvement over M2 than 15% because it should be using A17 and 3nm. Remember that the M2 is using A15, which would be 2 generations and 1 node behind M3.
I don't think doubling the power will yield 40%. It seems a bit too good to be true. Perhaps doubling the power will yield 25% more performance. That's still an extremely impressive 3200 GB5 score.
- M2 GB5 score is 1950.
- A16 improvement over A15 in ST is 11%. 1950 * 1.11 = 2165.
- Let's assume that A17 will have a 20% improvement over A16 because it will be using 3nm and we're hearing reports that A16 ran into engineering issues. 2165 * 1.2 = 2597. A score of 2600 GB5 seems reasonable for M3.
- If we go by your assumption that doubling the power can yield 40% more performance, then 2597 * 1.4 = 3635.
Anyways, I doubt Apple would double the power for M3 Ultra. Their own marketing is centered around efficiency.
Not every new rumour regarding a competitor means Apple could be in trouble lolIf he's referring to the Nuvia's IP-based SoC, could the M3 be in trouble?
Does any of these figures have merit?
Does it make sense that M3 wins in single-core by such a margin to Qualcomm's SoC, but loses in multi-core?
What configuration could 8cx have to reach 1800 in single-core and 14000 in multi-core?
What configuration could M3 have to reach 2500 in single-core and 11000 in multi-core?
Would such a leap between M2 and M3 be possible?
Does any of these figures have merit?
Does it make sense that M3 wins in single-core by such a margin to Qualcomm's SoC, but loses in multi-core?
What configuration could 8cx have to reach 1800 in single-core and 14000 in multi-core?
What configuration could M3 have to reach 2500 in single-core and 11000 in multi-core?
Would such a leap between M2 and M3 be possible?
30% is a tad optimistic but totally realistic. We have to remember that M2 is using A15 and A16 is 13% faster than A15 in ST already. A17 is two core generations ahead of A15 and one major node leap.To your other questions, sure, there can be a disparity in single core and multi-core ratio if one chip has more lower-performance cores (which would boost the multi-core score). And sure, a 30% performance improvement over M2 is probably realistic (if optimistic) for a new u-arch on 3NM node. But honestly, I don't trust any of these numbers.
One of the problems is that N3B only gives a very small shrink to SRAM and N3E gives none for all practical purpose. A large chunk of transistors is used for memory so don’t expect much die shrinkage if any.Does anyone know how big the Gen 4 dies will be? Compared to M2 Or what can be expected with an M3 die shrink?
One of the problems is that N3B only gives a very small shrink to SRAM and N3E gives none for all practical purpose. A large chunk of transistors is used for memory so don’t expect much die shrinkage if any.
One of the problems is that N3B only gives a very small shrink to SRAM and N3E gives none for all practical purpose. A large chunk of transistors is used for memory so don’t expect much die shrinkage if any.
Well, N3 probably allow Apple to clock their caches higher. As it is now, M2 running at 3.5GHz is still slower than what LPDDR4X-4266 can push, never mind LPDDR5. I suppose their cache sizes is big enough and likely no need to go much higher.
Well, N3 probably allow Apple to clock their caches higher. As it is now, M2 running at 3.5GHz is still slower than what LPDDR4X-4266 can push, never mind LPDDR5. I suppose their cache sizes is big enough and likely no need to go much higher.
My understanding is that cache and CPU clock has to match too, so that means CPU clock will also increase.Does it even work like that? I thought that cache and CPU frequency had to be somehow matched? My impression was that improvements to cache bandwidth usually come from wider cache path (e.g. M1/M2 can only fetch 48 bytes/cycle from L1 while Intel can do whopping 128 bytes/cycle with AVX-512.
I am genuinely asking, I really don't know.