Anonymous
6/14/2025, 5:57:29 PM
No.105592433
>>105592308
I'm not talking about random games or YouTube screenshots with you, as the others have noted, you are extremely uneducated on the matter. The fact of the matter is, if your GPU is waiting on your CPU on a new build, you fucked up. 80% util means you might as well have just bought a 7800XT last year, would have been a better pairing for such an old CPU.
>UE5 at higher resolutions becomes gpu bound way before it does cpu.
This is the misinformed normie's basic understanding of a bottleneck. Good enough to sound smart but doesn’t actually address or understand the issue.
Being “GPU-bound” at high res might be true in a vacuum, then sure, more pixels = more GPU load, but in real-world usage, especially with UE5’s architecture, you’re often dealing with way more than just resolution-based limitations. There are engine-level bottlenecks, IO throughput, CPU thread scheduling, asset streaming, GPU stalls waiting on CPU, etc. Any of these can become the limiter, and they can all introduce stutter, inconsistent frametimes, or poor scaling.
If your CPU isn’t strong enough to keep up with the demands of the scene, like feeding draw calls, handling physics, streaming Nanite data, or managing Lumen's global lighting updates, then congrats, you're not “GPU-bound,” you're just bottlenecked upstream. That leads to artificial GPU idling, dropped frames, and stutter, not because your GPU is weak, but because it’s waiting on the rest of your system to catch up.
I'm not talking about random games or YouTube screenshots with you, as the others have noted, you are extremely uneducated on the matter. The fact of the matter is, if your GPU is waiting on your CPU on a new build, you fucked up. 80% util means you might as well have just bought a 7800XT last year, would have been a better pairing for such an old CPU.
>UE5 at higher resolutions becomes gpu bound way before it does cpu.
This is the misinformed normie's basic understanding of a bottleneck. Good enough to sound smart but doesn’t actually address or understand the issue.
Being “GPU-bound” at high res might be true in a vacuum, then sure, more pixels = more GPU load, but in real-world usage, especially with UE5’s architecture, you’re often dealing with way more than just resolution-based limitations. There are engine-level bottlenecks, IO throughput, CPU thread scheduling, asset streaming, GPU stalls waiting on CPU, etc. Any of these can become the limiter, and they can all introduce stutter, inconsistent frametimes, or poor scaling.
If your CPU isn’t strong enough to keep up with the demands of the scene, like feeding draw calls, handling physics, streaming Nanite data, or managing Lumen's global lighting updates, then congrats, you're not “GPU-bound,” you're just bottlenecked upstream. That leads to artificial GPU idling, dropped frames, and stutter, not because your GPU is weak, but because it’s waiting on the rest of your system to catch up.