Shared session

By @TITOUNE9

Valorant

Oct 23, 2026, 06:28 PM · 24 min · 10 min gameplay

Detected by: system event · End: the game closed

Key takeaways

Smooth session

The time lost to stutters stays below the threshold.

13 stutters (16 slow frames including 7 freezes) · 2.7 s lost

Main cause: Game computation (12 occurrences). The worst stretch cost 662 ms of lost frames. 75% happened in the first ten minutes: the signature of shader compilation, which will not happen again on this game.

Pace set by the processor

The processor set the pace on 89% of the frames: it decides how many frames per second you get, not the graphics card.

Performance

FPS, lows and stutter breakdown

Frame timing

10 min active / 24 min total

Average FPS

1161

Session average

1% low

383

Average of the worst 1% of frames

0.1% low

108

Average of the worst 0.1% of frames

Frame p99

1.7 ms

Time per frame, in the slowest 1%

16.7ms · 60 FPS33.3ms · 30 FPS0 s12 min24 min

Median frame time of each slice (ms) over the session. Red dots = slowest frame of a slice, when it clearly breaks from the session’s pace.

Slow frames (16)

2.7 s lost
Game computation12(2.5 s)
Drive loading3(0.2 s)
Cause not identified1(0.0 s)

System state

CPU, GPU, VRAM averages and temperatures

Game CPU

?

22%

GPU

?

40%

CPU temp max

?

72°

54° on average

GPU temp max

?

52°

42° on average

hot threshold · 90 °C CPUhot threshold · 83 °C GPU20 °C58 °C95 °C0 s12 min24 min

Processor · Graphics card over the session, peak of each slice. The dashed lines are the thresholds of the thermal summary.

Advanced sensors (PawnIO driver)

GPU fan max 1,471 RPMCPU power avg. 71 WGPU power avg. 100 W

Measurement conditions

  • V-Sync: off
  • Loading hitches excluded: 7
  • Measurement cost: 0.7% of the processor
Pace set by the processor

The processor set the pace on 89% of the frames: it decides how many frames per second you get, not the graphics card.

VRAM peak

?

2.6 GB

Input lag p99

?

6.7 ms