Join the Discord! →

Join hundreds of racers just like you! We love to help answer questions and race together.


How to Benchmark Iracing Performance

Answering how to benchmark iRacing performance for drivers. Use repeatable replays, free overlays, and key iRacing settings to fix FPS and stutters fast today.

If you’re stuck on how to benchmark iracing performance, here’s the short answer: use a repeatable replay, log FPS and frame time, then change one setting at a time. You’re in the right place—this guide shows a quick, reliable way to test and improve performance without guesswork.

Quick Answer: how to benchmark iracing performance

Use a saved race-start replay as a fixed test, run an FPS/frame-time overlay (Windows Game Bar or CapFrameX), record results for 1–2 minutes, then adjust key iRacing settings—starting with Number of Cars—one by one and re-test until FPS and frame times are stable.

What’s Really Going On

iRacing performance is mostly about two things:

  • FPS (frames per second): higher is smoother.
  • Frame time (milliseconds per frame): consistent timing prevents stutters.

You’ll be limited either by your GPU (graphics) or CPU (car count, shadows, mirrors). Crowded starts and mirrors hit the CPU. Resolution, anti-aliasing, and shadows hit the GPU. A proper benchmark uses the same scene every time so you can see what actually helps.

Step-by-Step Fix

  1. Make a repeatable test
    Save a replay of a busy race start (cockpit view). Use the same car, track, weather, and time of day. This locks the scene so runs are comparable.

  2. Turn on a performance overlay

  • Quick: Windows Game Bar (Win+G) > Performance > pin FPS/Frame time.
  • Better logging: CapFrameX (free) to capture average, 1% lows, and spikes.

  1. Set a target
    Match your monitor. For 144 Hz, aim for a steady 144 FPS (≈6.9 ms frame time). For 60 Hz, aim for 60 FPS (≈16.7 ms). Stability matters more than peaks.

  2. Run the replay and record
    Play 1–2 minutes from the grid through Turn 1. Note average FPS, 1% lows, and any big frame-time spikes.

  3. Change one setting at a time and re-test
    In iRacing settings, adjust in this order (biggest wins first):

  • Number of Cars (most impactful for CPU)
  • Shadows (Quality and Shadow map)
  • Mirrors (number/quality) and Reflections
  • Anti-aliasing method/level
  • Crowds, Pit objects, Particles, Soft particles
  1. Lock in with a sensible FPS cap
    Cap FPS a few frames below your refresh (e.g., 141 for 144 Hz) using driver or RTSS (RivaTuner Statistics Server) to reduce input lag and spikes.

Extra Tips / Checklist

  • Identify the bottleneck: If GPU usage sits near 95–100%, reduce GPU-heavy settings (resolution, AA, shadows). If GPU is low during stutter but CPU cores spike, reduce Number of Cars, Shadows, and Mirrors.
  • Keep the test identical: Same camera (cockpit), FOV, mirrors, and weather. Don’t compare a solo lap to a race start.
  • Close background apps: Browsers, RGB suites, and overlays can cause stutters.
  • Use Fullscreen mode and up-to-date GPU drivers. Avoid stacking multiple overlays.
  • VR: Watch frame time in your VR overlay and target your headset’s refresh (90/80/72). Lower Number of Cars, Mirrors, and Shadows first.

FAQs

Q: Does iRacing have a built-in benchmark?
A: No. The most reliable method is a saved replay of a heavy race start, played back the same way each test.

Q: What FPS should I aim for in iRacing?
A: Match your display. 144 Hz → ~144 FPS, 120 Hz → ~120 FPS, 60 Hz → ~60 FPS. Prioritize stable frame time over peak FPS.

Q: How do I tell if I’m CPU or GPU limited?
A: Check usage. High GPU usage with stable CPU = GPU bound. Low GPU with CPU spikes or big car packs = CPU bound. Then tune the appropriate settings.

Q: What single setting gives the biggest FPS gain?
A: Number of Cars. After that, Shadows and Mirrors. These hit the CPU hardest in traffic.

Short Wrap-Up

Benchmark iRacing by testing the same replay, measuring FPS and frame time, and changing one iRacing setting at a time. Start with Number of Cars, then Shadows and Mirrors. Aim for a stable target FPS and smooth frame times for the biggest on-track improvement.