Measure your FPS
How the automated TinyBoost benchmark and the Manual Benchmark work, and how to read the results.
On this page
Where: open the CS2 tab. There are two benchmarks:
| Benchmark | What it answers | Who changes the settings |
|---|---|---|
| CS2 Automated Tweaked FPS Benchmark | "How much faster is CS2 with TinyBoost?" | TinyBoost, automatically |
| Manual Benchmark | "Did my change make CS2 faster?" | You, by hand |
Both record the real game running on the same Dust 2 map and compare a BEFORE result with an AFTER result.
Before you start#
- Save your work and close CS2.
- Be signed in to Steam.
- Finish any active optimization session, stress test, or Reset All.
- Plan to leave the PC alone for about 10–15 minutes. Don't touch the mouse or keyboard, don't Alt+Tab.
The first time, TinyBoost asks you to subscribe to the benchmark map. It opens the Steam Workshop page for you: click Subscribe, wait for the download, then click I've Subscribed, Start Benchmark.
CS2 Automated Tweaked FPS Benchmark#
This is a hands-off before-and-after test of TinyBoost itself.
What happens#
Do this
- BEFORE run. TinyBoost makes sure its optimizations are off, launches CS2 on the Dust 2 benchmark map, and records every frame for about 100 seconds. This is your normal, un-tweaked performance.
- Check-in. A window titled Initial Benchmark Complete shows your BEFORE numbers. Click Continue (or Cancel Benchmark).
- TinyBoost applies its optimizations. The screen may go black briefly and CS2 relaunches. This is normal.
- AFTER runs. CS2 runs the same map three times with TinyBoost active.
- Cleanup. TinyBoost turns everything back off and restores your settings. Your PC ends up exactly as it was before the test.
Your video settings are not touched
TinyBoost does not change your CS2 video settings during the tweaked run. BEFORE and AFTER use exactly the same in-game graphics settings, so the difference you see comes from TinyBoost's optimizations alone.
Nothing stays changed
The benchmark is a demonstration. Once it finishes, all tweaks are reverted. To use them while you play, press START as usual.
The TinyBoost column in the results is the final AFTER run, compared against BEFORE.
Manual Benchmark (your own changes)#
Use this to test anything yourself: new graphics settings, a driver, a BIOS change, a different launch option. TinyBoost changes nothing in this mode.
Do this
- Open CS2 → Manual Benchmark.
- Set BEFORE runs and AFTER runs (1–5 each). More runs give a more reliable average.
- Set Duration per run (20–104 seconds).
- Name both sides, for example "Old driver" and "New driver".
- Click Start Manual Benchmark and leave the PC alone.
- When BEFORE runs complete appears, make your change now.
- Click Start the AFTER benchmarks and leave the PC alone until they finish.
If you ran several BEFORE runs, their average is used as the baseline.
Tip
Change one thing between BEFORE and AFTER. If you change three things, you won't know which one helped.
Reading the results#
| Reading | Plain-English meaning | Better is |
|---|---|---|
| Average FPS | Frames per second on average | Higher |
| 1% Low Average | The average of your worst 1% of frames: how bad the dips get | Higher |
| P1 FPS | The FPS your game stays above 99% of the time | Higher |
| 0.1% Low Average | Your very worst frames: the rare big stutters | Higher |
| Stuttering | Share of time spent on frames much slower than normal | Lower |
| PC Latency | Delay between your input and the frame on screen (when supported) | Lower |
The lows matter most for how smooth the game feels. A higher average with worse lows can feel choppier.
Small differences (a few percent) can be normal run-to-run variation. Repeat the test if the result surprises you.
Past results#
Click Results History to see every run. Open Report shows the full report with frame-time charts for each run; Open Folder shows the saved files.
If a run fails#
Read the on-screen message before retrying. Check that Steam is signed in, the map is subscribed, CS2 stayed in the foreground, and no other TinyBoost job is running.
Use Cancel if you need to stop, then wait for cleanup. If your PC crashes or restarts mid-test, reopen TinyBoost: it finishes restoring your settings automatically.
If it fails again, send support the exact message and whether it happened during BEFORE or AFTER. See what to send.