4 ms·
On a modern PC games use a small fraction of the CPU and the GPU is the bottleneck. The only applications that really strain the CPU (i.e. all cores) are trivia
by barrkel 11y ago
On a modern PC games use a small fraction of the CPU and the GPU is the bottleneck. The only applications that really strain the CPU (i.e. all cores) are trivially parallelizable ones like transcoding, compilation, test suites, etc.
For games specifically I'd prefer more work done on CPU and free up the GPU, provided the communication overhead isn't too much and latency doesn't become a problem.
Low power is less of a problem than thermal limiting for compute intensive work. I see about 90% variation in test times on my laptop for unit tests, for example.
So overall I see more application for this in apps than games, and only then when the tradeoffs are right. It's not a simple call.
- corysama 11y agoGames graphics engine guy here. I'm very happy to move text rendering from the CPU to the GPU. Done well it moves milliseconds of CPU work to tenths (or less) of milliseconds of GPU work. Also, I care quite a bit about power draw because my customers on laptops and mobile are very sensitive to it. If my game is a battery hog, it doesn't get played as long or as often.
- pcwalton 11y agoSure, for games the tradeoffs may be different. For apps, though, we regularly see 1% GPU time, 99% CPU time. Even "GPU-accelerated" painting backends like Skia-GL can easily spend 90% of their time on the CPU--in the driver, issuing state changes, rasterizing fonts, building batches, creating display lists. It's not an exaggeration to say apps are desperate to find work that can be offloaded to the GPU.