Shared session

By @kleiN

Minecraft (Java)

Sep 19, 2026, 05:33 PM · 5h 40min · 99 min gameplay

AMD Ryzen 7 9800X3D 8-Core Processor · NVIDIA GeForce RTX 4080 · 46 GB RAM · 2560x1440 · driver 616.64Windowed

Detected by: process scan · End: the game closed

Key takeaways

Smooth session

The time lost to stutters stays below the threshold.

51 stutters (69 slow frames including 15 freezes) · 5.6 s lost

Main cause: Not enough RAM (37 occurrences). The worst stretch cost 781 ms of lost frames.

Pace set by the processor

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

Performance

FPS, lows and stutter breakdown

Frame timing

99 min active / 340 min total

Average FPS

153

Session average

1% low

78

Average of the worst 1% of frames

0.1% low

63

Average of the worst 0.1% of frames

Frame p99

12.3 ms

Time per frame, in the slowest 1%

16.7ms · 60 FPS33.3ms · 30 FPS0 s106 min212 min

Worst frame of each slice (ms) over the session: on this older session, the line traces each slice’s maximum, not the usual pace. Red dots = frames that clearly break from the session’s pace.

Slow frames (69)

5.6 s lost
Not enough RAM37(3.1 s)
Game computation28(2.3 s)
Drive loading4(0.2 s)

System state

CPU, GPU, VRAM averages and temperatures

Game CPU

?

5%

GPU

?

22%

CPU temp max

?

71°

52° on average

GPU temp max

?

69°

57° on average

hot threshold · 90 °C CPUhot threshold · 83 °C GPU30 °C63 °C95 °C0 s170 min339 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)

VRM max 52 °CCPU fan max 4,067 RPMGPU fan max 1,623 RPMCPU power avg. 60 WGPU power avg. 52 W
Pace set by the processor

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

VRAM peak

?

6.7 GB

Input lag p99

?

27.2 ms