PoE2 How to Read F1 Performance Graphs (0.5.0)

Press F1 in PoE2 to open the performance overlay. Most players glance at the FPS number and close it. But the overlay contains four critical graphs that tell you exactly what is causing your performance issues — and whether the fix is a graphics setting, a network change, or a hardware upgrade. Here is how to read each one.

Graph 1: Frame Time (The Most Important One)

FPS is an average — it hides spikes. Frame time (measured in milliseconds) shows the actual time each frame takes to render. A flat line = smooth. Spikes = stutter.

• Ideal: Flat line at 6.9 ms (for 144 FPS) or 16.7 ms (for 60 FPS), with occasional micro-spikes under 2 ms variance.
• Regular spikes every 1-2 seconds: Background process interrupting rendering (antivirus, Discord hardware acceleration, Windows Defender scan). Check background apps.
• Spikes only when entering new zones/areas: Shader compilation stutter. Set Nvidia Shader Cache to 100 GB in NVCP, clear old cache files.
• Spikes only when near monster packs: Could be CPU bottleneck (too many draw calls) or network stutter. Check Graph 4 (Network).
• Gradually increasing frame times over a session: Memory leak or VRAM filling up. Restart the game every 2-3 hours. Consider using ISLC (Intelligent Standby List Cleaner).

Graph 2: CPU & GPU Timing

This graph overlays CPU frame time (orange) and GPU frame time (blue). The taller bar tells you who is the bottleneck.

• CPU higher than GPU → CPU bottleneck. PoE2's endgame is heavily CPU-bound. Fixes: reduce sound channels (FMOD), disable Dynamic Culling, set engine_multithreading=false on 6-core CPUs, disable background apps.
• GPU higher than CPU → GPU bottleneck. Lower Graphics settings: GI to Low, Shadows to Low, reduce render scaling. Use DLSS/FSR.
• Both high and equal → balanced but slow. Your hardware is at its limit. Lower both graphics and CPU-intensive (sound, effects) settings.
• Both low but stutter persists → Problem is network or I/O, not rendering.

Graph 3: Memory (RAM + VRAM)

Shows system RAM and GPU VRAM usage. If VRAM is near 100% (e.g., 7.8 GB / 8 GB on an RTX 3070), the game is swapping textures to system memory, causing hard stutter. Fix: reduce streaming_cache_pool_size in production_Config.ini, lower texture quality to Medium, or drop render resolution.

Graph 4: Network Latency

Shows ping, variance (jitter), and packet loss. This is the graph to watch if your FPS looks fine but the game "feels" stuttery.

• Ping spikes above 100 ms: Gateway congestion. Switch to a different gateway in the launcher. The 0.5.0 launch saw 400K+ concurrent players — gateway switching helps.
• High jitter (variance >20 ms): WiFi interference. Use Ethernet. If Ethernet isn't possible, use 5 GHz WiFi with dedicated router.
• Packet loss >0%: Network congestion or ISP routing issues. Use the Network Throttling registry fix (see our Windows 11 Guide).
• Latency spikes when near monsters (FPS looks fine, character stutter-walks): This is the 0.5.0 network-spike bug. Switch to Lockstep mode in Settings → Gameplay → Networking. See our Stuttering Fix Guide for full details.

How to Benchmark Properly

• Stand in hideout for baseline FPS.
• Run one juiced T16 map with the same scarab setup for comparison.
• Record both average FPS and 1% lows — 1% lows tell you about stutter, average tells you about throughput.
• Always benchmark with the same content. Comparing a Breach map to a Ritual map is meaningless.

For the complete settings guide to fix what you find in the graphs, see our Ultimate 0.5.0 Performance Guide.