Shared session

By @TITOUNE9

Valorant

Oct 21, 2026, 11:11 PM · 2h · 49 min gameplay

Detected by: system event · End: the game closed

Key takeaways

Rough session

Stutters cost a noticeable share of the playtime.

265 stutters (982 slow frames including 644 freezes) · 116.6 s lost

Main cause: Game computation. The worst stretch cost 8.3 s of lost frames.

Pace set by the processor

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

Performance

FPS, lows and stutter breakdown

Frame timing

49 min active / 120 min total

Average FPS

679

Session average

1% low

197

Average of the worst 1% of frames

0.1% low

85

Average of the worst 0.1% of frames

Frame p99

3.9 ms

Time per frame, in the slowest 1%

16.7ms · 60 FPS33.3ms · 30 FPS0 s21 min41 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 (982)

116.6 s lost
Game computation480(67.6 s)
Drive loading12(0.8 s)
Cause not identified7(0.3 s)
Not enough RAM1(0.2 s)

Breakdown of the first 500 stutters.

System state

CPU, GPU, VRAM averages and temperatures

Game CPU

?

27%

GPU

?

47%

CPU temp max

?

75°

58° on average

GPU temp max

?

53°

42° on average

hot threshold · 90 °C CPUhot threshold · 83 °C GPU20 °C58 °C95 °C0 s60 min120 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,512 RPMCPU power avg. 80 WGPU power avg. 104 W

Measurement conditions

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

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

VRAM peak

?

3.8 GB

Input lag p99

?

8.1 ms