Why is my FPS low when neither my CPU nor GPU looks maxed out?

November 19, 2026 5 answers
Asked by bossPhaseTactician

I'm getting around 50 FPS in Mafia: The Old Country at 1440p with FSR Quality, even after changing graphics settings. GPU usage is about 75%, and the CPU cores appear to stay below 70%.

I'm using a Ryzen 7 5700X, a Radeon RX 9070 and DDR4-3200 CL18 RAM on Linux with Proton Experimental and NTSync. What should I check before blaming the RAM or the game?

Answers

lootGoblin~OnBreak

Low reported CPU usage doesn't rule out a CPU-side limit. A game can be held up by one critical thread even when the rest of the processor has plenty of spare capacity. Usage readings are averaged over time, so a thread that moves between cores or waits frequently may not show up as a core sitting at 100%.

Compare CPU and GPU frame times in the same outdoor spot. If GPU frame time is comfortably below the roughly 16.7 ms budget for 60 FPS, but frames still take longer than that, look at the CPU side and other sources of waiting. A profiler can give more useful detail than utilization percentages alone.

ROMlabeler+Chalk:

Use the same scene and camera angle for each comparison. Movement and scene complexity can make quick FPS comparisons pretty noisy.

Reply to this answer
QCFdashByApron

Try a simple scaling test. Keep the scene and settings fixed, then change resolution or render scale by a substantial amount. If FPS barely changes while GPU usage drops, reducing GPU work isn't addressing the main limit there. If FPS rises noticeably, the GPU workload is still part of the picture.

FSR reduces render resolution, but it won't fix a CPU-side or game-engine bottleneck. Some settings also affect CPU work, so change one thing at a time rather than switching the whole preset.

Reply to this answer
kartSideways

Check for a frame cap, VSync or another synchronization setting before digging deeper. Then compare Proton Experimental with a stable Proton release using the same scene and settings. That won't prove the cause by itself, but it can help separate a compatibility regression from a limit that persists across versions.

Also check that the GPU driver and Mesa stack are current for the distribution. Note any changes rather than updating everything at once, otherwise it gets hard to tell what helped.

Reply to this answer
scrimCaller~Uncertain

RAM could matter in a CPU-limited scene, but those utilization numbers don't establish that it's the problem. First check that the memory is actually running at its intended speed and that the modules are configured for dual-channel operation. I'd avoid buying faster RAM based on this test alone.

P1antiAir~Late:

CPU and GPU clocks, temperatures and power limits are worth checking during the test too. Boost settings don't guarantee sustained clocks under load.

Reply to this answer
kartHairpin!LateApex

It may be specific to that area or to the game rather than a general hardware problem. Check a few repeatable scenes and another demanding game, and look at frame times as well as the FPS average. Brief stutters and a steady 50 FPS can point to different issues.

If the slowdown is confined to one scene, that gives you a useful reproduction case for checking game updates or reporting the issue.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions