Live data from Hacker News

Intel's Lion Cove P-Core and Gaming Workloads

chipsandcheese.com

81–90 of 126 posts

Re: Intel's Lion Cove P-Core and Gaming Workloads

#81
post #77

Earlier quoted context omitted.

I am still waiting on evidence that memory architecture helps anyone.

I'm pretty sure memory is still the main bottleneck in the vast majority of operations, and why the X3D is such a monster with so much L3 cache. There's almost nothing that doesn't benefit from having twice the memory bandwidth.

Did you read the article?

Re: Intel's Lion Cove P-Core and Gaming Workloads

#82
post #59

Earlier quoted context omitted.

It’s arguing desktop gaming is dying not PC gaming. Q4 2024 shipped 13.6 million desktops (down 1.8%) vs 53.2 million laptops up (6.8%). That trend of declining Desktops vs increasing laptops has been steady since 2010. There’s still plenty of desktops to justify major investments by gaming companies, but that’s not guaranteed long term.

That's just overall desktop and laptop sales though, right? So home multimedia desktop PCs could be falling off a cliff, business desktop PCs could be dropping, and gaming PCs could be growing a bit and the overall market of desktops could still be net down, right? The overall market doesn't give us enough resolution to determine the health of gaming PC sales IMO. There's too many other possible ways we get to that s…

You see a similar trend in gaming desktops vs gaming laptops, but that’s just a sideshow. People game on the hardware they have, gaming specific PC’s are a subset of the overall player base.

It used to be much easier to justify adding a dedicated GPU to the desktop's people where already getting, but when everyone is buying laptops that’s dying. As shown by end of generation mid range cards like the 4060 (2 years old, nothing newer) being relatively less common than they used to be on Steam.

#1 Laptop 4060 4.99%, #3 desktop 4060 4.41%. Overall gaming desktop PC’s are still more common than gaming laptops, but the trend is very much down. #2 is the 4 year old 3060.

Re: Intel's Lion Cove P-Core and Gaming Workloads

#83

Earlier quoted context omitted.

I don't fully follow this, so what has been gained with the new models? I seem to remember you'd need dedicated industrial cooling for the 14700k. Does the new model at least pump much less power?

> I seem to remember you'd need dedicated industrial cooling for the 14700k. Those CPUs run hot, but it got exaggerated a lot online. It’s not hard to handle their heat with a good air cooler (even some of the $50 units like the Peerless Assassin) or a run of the mill closed loop water cooler. There are a lot of old notions in the gaming community that you need to keep CPUs under arbitrary temperature thresholds or t…

Hm, to keep in mind though that what the gaming community always claimed actually did happen with those processors - they disintegrated because of too much voltage (and probably heat). https://www.pcgamer.com/hardware/processors/intel-cpu-crashe.... So the "run themselves deep into the performance curves" part of these Intel processors was a disaster.

Re: Intel's Lion Cove P-Core and Gaming Workloads

#84

Earlier quoted context omitted.

At some point you have to blame the driver model on Windows. People have been saying "it's the drivers" for 30 years. Also most of this is intentional first party behavior from Microsoft. Windows intentionally periodically wakes from sleep to do communication (for notifications etc.) Microsoft's advice last I checked is to not store sleeping laptops running windows in laptop bags. There's a ton of other decisions the…

> At some point you have to blame the driver model on Windows. Serious question, specifically what is wrong with the driver model in terms of this situation? What change would you propose to solve this? Why isn't it a matter of the device manufacturers churning out crappy and poorly tested devices and solely Microsoft's fault? I do agree, Microsoft should probably make it easier to point out "hey this device is causi…

S1 S2 S3 S4 sleep modes and what happened to the most useful of them ;)

Re: Intel's Lion Cove P-Core and Gaming Workloads

#85

Earlier quoted context omitted.

> At some point you have to blame the driver model on Windows. Serious question, specifically what is wrong with the driver model in terms of this situation? What change would you propose to solve this? Why isn't it a matter of the device manufacturers churning out crappy and poorly tested devices and solely Microsoft's fault? I do agree, Microsoft should probably make it easier to point out "hey this device is causi…

S1 S2 S3 S4 sleep modes and what happened to the most useful of them ;)

[deleted]

Re: Intel's Lion Cove P-Core and Gaming Workloads

#86
post #63
post #59

Earlier quoted context omitted.

It’s arguing desktop gaming is dying not PC gaming. Q4 2024 shipped 13.6 million desktops (down 1.8%) vs 53.2 million laptops up (6.8%). That trend of declining Desktops vs increasing laptops has been steady since 2010. There’s still plenty of desktops to justify major investments by gaming companies, but that’s not guaranteed long term.

That's a strange movement of a goal post, not to mention that using percentages conveniently hides whether PC Gaming as a whole is growing or shrinking. Hows your post related to anything here?

What moving the goalposts? They specifically talked about gaming desktops as a form factor which needs developer support.

“Games requiring desktop cases looking like a rainbow aquarium with top everything will become a niche, in today's mobile computing world”

Re: Intel's Lion Cove P-Core and Gaming Workloads

#87
post #81

Earlier quoted context omitted.

I'm pretty sure memory is still the main bottleneck in the vast majority of operations, and why the X3D is such a monster with so much L3 cache. There's almost nothing that doesn't benefit from having twice the memory bandwidth.

Did you read the article?

The article literally says this very thing?

> Lion Cove suffers harder with backend memory latency, but far less from frontend latency. Part of this can be explained by Zen 4’s stronger data-side memory subsystem. The AMD Ryzen 9 7950X3D I previously tested on has 96 MB of L3 cache on the first die, and has lower L3 latency than Lion Cove in Intel’s Arrow Lake platform. Beyond L3, AMD achieves better load-to-use latency even with slower DDR5-5600 36-36-36-89 memory. Intel’s interconnect became more complex when they shifted to a chiplet setup, and there’s clearly some work to be done.

They only compared three games of roughly the same genre in terms of mechanics which is not exactly a representative benchmark either, even for games. The average shooter with a fixed map and say, Minecraft, have vastly different memory access demands.

Re: Intel's Lion Cove P-Core and Gaming Workloads

#88
Seeing that the Lion Cove L3 cache takes ~83 cycles while the previous generation was only ~68 cycles explains why Lion Cove is an utter dud of a CPU for gaming and why it loses to the Raptor Cove in so many gaming benchmarks.

Meanwhile, the Zen 5 is only 47 cycles, and if you get the X3D variant, you get a TON of that L3 cache, which just turbo-charges games.

How did Intel allow such a major performance regression in their L3 cache?

Re: Intel's Lion Cove P-Core and Gaming Workloads

#89
post #8

> E-Cores are turned off in the BIOS, because setting affinity to P-Cores caused massive stuttering in Call of Duty. I understand doing this for the purpose of specifically analyzing the P-core microarchitecture in isolation. However this does make the test less interesting for potential customers. I don't think many people would disable E-cores in BIOS if they bought this CPU, so for the purpose of deciding which CP…

Pretty sure the mainstream gaming advice is to turn off E-Cores so the vast majority of actual gamers would be doing just that.

Re: Intel's Lion Cove P-Core and Gaming Workloads

#90

Earlier quoted context omitted.

> Which is why AMD seems to be showing everyone a better path by simply using process optimizations and execution time optimization choices with the same zen cores. Funny you would say that, because AMD X3D CPUs have cores with 3D Cache, and cores without, and massive scheduling problems because of this.

Which is just caching/locality asymmetries, knowledge of which has been at least partially integrated into schedulers for a couple decades now. It just goes to show how hard scheduling actually is. But also, you call it a 'massive' problem and its actually somewhat small in comparison to what can happen with vastly different core types in the same machine. Many of those cores also have quite large cache differences t…

I think part of the problem is that from where I stand, there's no way to tell my programming language (java) "Hey, this thing doesn't need horsepower so prefer to schedule it on little cores." Or conversely "Hey, this thing is CPU sensitive, don't put it on a LITTLE core."

I don't think (but could be wrong) that C++ has a platform independent way of doing this either. I'm not even sure if such an API is exposed from the Windows or linux kernel (though I'd imagine it is).

That to me is the bigger issue here. I can specify which core a thread should run on, but I can't specify what type of core it should run on.

Post reply on HN