Wow. Lots to unpack here.
Isn't this the 1st time that Intel is in serious monetary difficulties together with technical problems? They could buy their way out of trouble before, but I think not this time.
I agree. Not only did they "buy" their way out of trouble, they used their monopoly power and vertical integration with chipsets, mb's, etc to influence OEM's to keep in the game until their designs got out of the woods again. This time is different in that respect. You have a valid point.
If gaming performance was really a collapse why would Intel even release this. Why not cancel release or delay it.
Yes vanilla Zen 5 was disappointing and a flop, but thats because it did not improve gaming performance or did not regress it either compared to vanilla Zen 4.
Its one thing if Arrow Lake is no gaming improvement over Raptor Lake or maybe even a slight regression, but an outrght collapse?? How could intel release such a CPU. Or change marketing towards non gamers only lol if that is really the case.
... just out of curiosity, how much of the CPU market do you believe gamers comprise?
The desktop market is only 20-25% of the CPU market. High end desktops (where gamers purchase) is only 10-20% of that. Furthermore, the trend is decidedly down for these markets over the last decade and continues to trend down year over year.
In other words, in the grand scheme of things there is no reason for Intel to be concerned much at all about gaming (high end desktop). Missing gaming improvements in the first of the new processor generation is hardly catastrophic for Intel, but boy it sure sounds like it around this forum . I do get that gamers are disappointed, but I don't think this miss is going to have much impact on Intel financially.
It's not that dramatic. They botched the fabric for this gen and it's likely fixed by Nova lake or even Panther lake. This is almost nothing compared to their fabs seemingly having no customers. Going all in on fabs is basically why they are in this situation. Funny it's starting to look like cancelling Panther lake-S was a mistake. If the memory latency and LLC clocks are fixed it could've been a decent generation. Creating more 18A volume for IFS would've been a plus. Also the lga1851 platform wouldn't end up being retired after a single gen which is yet another blow to Intel mind share
I agree. It is likely that the 2025 server chip will include improvements in the bottlenecks seen in Arrow Lake. Clearwater Forest is a MUCH more important chip for Intel to get right. Arrow Lake and Lunar Lake are both just warm-ups for that event.
QC/Nvidia+MTK are in laptop Intel is not sitting Idle in Laptop it's the desktop that doesn't have competition till Zen6 as for server yes But GNR is not at bloodbath it will slow AMD quite a bit
GNR is generally behind by a geometric mean of about 40% I believe I read. The only measure that this is not a "blood bath" is in the context of it not being 200% like it has been. GNR is both more expensive, and less performant than Turin, and it requires a new platform while Turin is using the same socket as its 2 previous predecessors I believe. I would say that GNR is a good step in the right direction, but not enough to stop the momentum that AMD has going in the data center. AMD will continue to gain market share at or above the current rate of change from the last couple of years IMO.
Only Clearwater Forest can reverse the trend .... and even then, it is likely that Clearwater Forest will be challenged pretty quickly by EPYC Zen 6 (Venice) which will have 32 core CCD's. Still, Clearwater Forest looks like it could be a very impressive chip. Much higher efficiency, much more dense on 18A with BSPD .... it has all the makings of an impressive DC processor.
This is just a hypothesis, as Netbrust has never had a larger number of execution units or a wider decoder in any generation. How Netbrust would behave if the next generation had a decoder width of 2 instead of 1 is pure hypothesis.
Netbrust has never fought for a higher IPC. Netbrust is a completely different philosophy and has seen IPC drops in subsequent generations.
I wouldn't find any similarities between LionCove and Netbrust. LionCove has a higher IPC, but also loses due to lower clock speeds and suffers in the transition from monolith to tiles.
A complete picture of LionCove's IPC will become available after comprehensive analysis and testing of ArrowLake-S.
Exactly. Netburst spent all its time recovering from branch misses (flushing out that long pipeline). I also think that people forget that achieving higher clock speed involves having more stages. Having good performance across a wide variety of loads involves having lots of complex processing units that are specialized. Being able to do all this while bearing the chip to chip latency .... also more complicated.
Seems like people think that you can take Skymont and just tack on a trivial amount of additional logic and surpass Lion Cove across the board. If it were that easy, seems like everyone would be doing it.... but they aren't.
Lower clock speeds, densely packed Skymont core logic, smaller structures including buffers.
There is no great philosophy here. See on Zen4c compared to Zen4 while maintaining the same IPC, the surface area of Zen4c is much smaller(-34%). The same was done with Skymont, plus less extensive core logic, mainly buffers and no UOP cache.
Yes, but Zen5c is still quite a bit larger than Skymont I believe. My guess is that it is likely that Turin Dense with its Zen 5c cores will likely pound the crap out of an equal number of Skymont cores in data center applications. We won't know for sure until Clearwater Forest I think.
Not sure why everyone is so into PPA for CPU cores. Ultimately PPA efficiency of CPU cores are pretty negligible on the products that can be built for consumers.
Single digit mm^2 size for core means very little when everything else on die is required still. With the same amount of L3 and L2 cache, a CPU with just Lions Cove or Skymont would be not be a big difference in size if you target the same performance.
Because the cores must run within a thermal and power limit. When you get all those cores going at the same time, the trick is to get them all up to higher clocks without reaching a thermal or power limit. Otherwise you get a core that is designed to go 6Ghz that can't run over 2Ghz.