VALORANT and CS2 Performance — Stability Over Peak Frame Rate
These games run on anything. The problem is never average FPS, it's the drop during the fight that matters.
The short answer
Tactical shooters are limited by CPU single-thread performance rather than graphics capability, so a powerful graphics card produces little benefit while a faster processor produces a lot. The metric that matters is one per cent low frame rate rather than average, because the drops occur during smoke, utility and multi-player engagements, which is precisely when consistency decides the round.
Verified and last updated August 12, 2026.
- Time needed
- 18 min
- Difficulty
- Intermediate
- Read time
- 3 min
Tactical shooters run at high frame rates on almost anything, which makes their performance problems confusing. Someone reports 300 frames per second average and also that the game stutters in fights. Both are true.
The average is measured while nothing is happening.
Measure the fight, not the walk
Your average frame rate is dominated by the two minutes of walking between engagements. The 1 per cent low is what happens during the fight — smokes, utility, four players on screen. That number decides how the game feels and it is not the one displayed by most overlays.
Step 1: Measure 1 per cent lows, not average
The second row is what you want and it has a lower average than the first. This is the whole point.
Step 2: These are CPU games
The usual advice inverts here.
Check GPU utilisation during a fight 10 min
It will almost certainly be well below one hundred per cent. That confirms the CPU is your limit and that a graphics upgrade would change nothing.
Close everything competing for cores 5 min
Browser tabs, launchers, voice clients, capture software. In a CPU-bound game these compete directly for the resource you need, and the effect appears exactly during busy moments.
Check memory pressure 5 min
Sixteen gigabytes is enough for the game and not necessarily enough for the game plus a browser plus everything else. Memory pressure produces intermittent hitching that looks like a graphics problem.
Confirm the CPU is not thermally limited 15 min
A frame rate that degrades over a session is thermal, not configuration. Check clock speeds under sustained load rather than at the menu.
Step 3: Configure for consistency
The cap is the important one and it feels counter-intuitive to people who have spent years chasing higher numbers. Capping removes the swing between 400 in an empty corridor and 120 in a smoke fight, and that swing is what you actually notice.
The overlay problem specifically
These games are latency-sensitive and overlays cost both frames and latency. Discord, Steam, the driver overlay, capture software — all off during competitive play.
Discord's overlay is the most common single offender and disabling it is a measurable improvement on many systems.
What works
What doesn't
Key takeaways
Frequently asked questions
Why do I get low FPS in VALORANT with a good GPU?
Because the game barely uses it. Tactical shooters are deliberately built to run on modest hardware, which means they are limited by CPU single-thread performance rather than graphics capability. A powerful graphics card sits mostly idle while a slower processor caps your frame rate, which is the opposite of the usual advice and why GPU upgrades disappoint here.
What are 1 percent lows and why do they matter?
They are the frame rate during the worst one per cent of frames, which is what you experience as a stutter or hitch. In tactical shooters the drops happen during smokes, utility and multi-player fights, which is exactly when the round is being decided. A game averaging 300 with 1 percent lows of 90 feels worse in fights than one averaging 200 with lows of 180.
Should I cap my frame rate in these games?
Yes, a few frames below your refresh rate, provided your hardware exceeds that comfortably. It produces more consistent frame pacing and lower input latency than running uncapped, and it stops the frame rate swinging wildly between quiet moments and fights. Consistency is worth more than peak in games where the peak occurs while nothing is happening.
Does CS2 stutter more than CS:GO did?
It uses a newer engine with different characteristics, and shader compilation plus higher CPU demands produce hitching that the older game did not have. Setting the shader cache to unlimited, capping the frame rate and closing overlays address most of it. Some of it is the engine and no configuration removes it entirely.
Do these games need a lot of RAM?
Sixteen gigabytes is comfortable and thirty-two makes little difference for the game itself. What does matter is what else is running, since a browser with many tabs plus a voice client plus a launcher consumes a meaningful share, and memory pressure produces exactly the intermittent hitching that hurts most in a fight.
About the author
Competitive & Settings Editor
Dan played CS:GO semi-professionally in a regional ESEA Main roster between 2017 and 2020, and has hit Radiant in VALORANT in three separate acts. He now spends most of his competitive energy on the unglamorous side of the game: input latency, sensitivity consistency and warm-up routines that actually transfer.
Found something wrong? Games patch and fixes go stale. If a step here no longer works, tell us at hello@spyld.com and we will retest it. Read how we test and our editorial policy.