Note: This article is more than one year old.

  • Interpretation of console statistics such as stat unit depends on the rendering path, including Deferred and Lumen. Check the explanation for your version.
  • What counts as a good threshold depends on project scale and target FPS. This article gives introductory guidelines.
  • Use a profiler such as Unreal Insights alongside these statistics when identifying bottlenecks.

When UE5 stutters, first investigate what is causing the load

This article explains the stat unit fields, basic bottleneck identification from those statistics, and how to display them automatically each time. Statistics such as stat unit are the first step in investigating performance. You can type stat unit into the console, or use the viewport menu: 1. Click the upper-left menu; 2. choose Stats; 3. Engine; 4. enable FPS; and 5. enable Unit and UnitGraph. Use whichever method is easier. Detailed numbers appear on the right, including Frame, Game, Draw, RHIT, GPU time, DynRes, Draws, and Prims. These help identify whether performance is limited by the game thread, which handles logic and player input; the rendering thread, which handles rendering preparation, textures, shaders, and lights; or the GPU. Official explanation:

Epic Games — stat unit command referencehttps://dev.epicgames.com/documentation/en-us/unreal-engine/stat-commands-in-unreal-engine#unit

Frame

Frame time is the total time needed to produce one frame. Because the game and rendering threads synchronize before a frame finishes, it is often close to one of those thread timings.

Game

If Frame is close to Game, performance is probably bottlenecked by the game thread.

Draw

If Frame is close to Draw, performance is probably limited by the rendering thread.

GPU time

Measures how long the graphics card takes to render the scene. GPU time is synchronized with the frame and can therefore be similar to Frame.

RHIT

RHI thread time is synchronized with the frame and may also be similar to Frame.

DynRes

When supported and enabled, dynamic resolution displays the primary screen percentage together with the secondary screen percentage.

The top number in the following image is this project's actual FPS. It should reach 60FPS, but a bottleneck is holding it to 48FPS. What is limiting it?

First, compare Frame and the game thread

When Frame is close to Game, the game thread is likely to be the bottleneck. This thread handles game logic, AI calculations, physics, and similar work. If it accounts for much of the frame time, that work needs optimization. In the example below, Frame and Game are not close, so I concluded that the game thread was not the bottleneck.

Compare Frame and the rendering thread

When Frame is close to Draw, the rendering thread is indicated as the bottleneck. It performs the work needed to prepare models, texture mapping, shaders, and other elements for display. If that time is a large share of Frame, rendering-related optimization is needed. In the image below, Frame and Draw are very close, suggesting that the rendering thread is the bottleneck.

Check GPU time

GPU time measures how long the graphics card takes to render the scene. If it is close to Frame, GPU processing may be the bottleneck.

RHI thread time, RHIT

The RHI (Render Hardware Interface) thread communicates with the low-level APIs controlling rendering. A value close to Frame can suggest an issue involving rendering API calls. In the example below, it is not close, so this did not appear to be the problem.

Monitoring dynamic resolution, DynRes

It is disabled here. When enabled, dynamic resolution changes rendering resolution to maintain performance. Whether it is enabled and how it affects the scene are also relevant to performance analysis.

Keeping statistics visible when the editor restarts

The display disappears when the editor restarts. To retain it, open Editor Preferences → Viewports → Look and Feel and enable saving engine statistics. The statistics then return after restarting the editor.

Checking statistics in an exported, running app

Sometimes you want statistics in the actual exported app, rather than only a simple preview.

Behavior can differ once the application is running.

Set up a Blueprint to execute stat unit.

Add Execute Console Command and enter a statistics command such as stat unit.

Riragon's own article ends here. The following section is the result of a deep-search AI query. It may cover points not found above. One benefit of AI search is discovering information you did not know to look for.

Exploring further

The following research examines the detailed interpretation of stat unit, bottleneck identification, and related statistics in UE5. It also covers measurement in packaged apps, VR optimization, hardware effects, and optimization techniques.

Performance measurement and bottleneck analysis in UE5

1. Understanding stat unit fields and identifying bottlenecks

Running the stat unit console command in Unreal Engine 5 displays a breakdown of frame timing. Main fields include Frame, Game, Draw, GPU, RHIT, and Present.

The longest-running part is the bottleneck.

Actual Frame time is determined by the slowest of Game, Draw, and GPU.

Meaning of Frame, Game, Draw when using Stat UnitGraph — Epic forumshttps://forums.unrealengine.com/t/meaning-of-frame-game-draw-when-using-stat-unitgraph/317239#:~:text=%E2%80%9CThe%20actual%20frame%20time%20is,%E2%80%9D

Therefore, the field whose value is nearly equal to Frame identifies the limiting thread or device: CPU game processing, CPU rendering preparation, or the GPU. Optimize that part.

Profiling & Optimizing for the best performance in Unreal Enginehttps://vrealmatic.com/unreal-engine/profiling#:~:text=Frame%20The%20total%20amount%20of,bottlenecked%20by%20the%20Rendering%20Thread

For example, Game 25ms, Draw 5ms, GPU 4ms, and Frame 25ms indicate game logic is limiting the CPU. GPU 30ms, Game 10ms, and Frame 30ms indicate a GPU bottleneck.

2. Related statistics: stat fps, stat gpu, stat scene rendering, and more

Combine stat unit with other Unreal Engine statistics for a more detailed analysis.

Together, these commands first show whether the CPU or GPU is limiting performance through stat unit, then help investigate the details.

Understanding performance bottlenecks? — Epic forumshttps://forums.unrealengine.com/t/understanding-performance-bottlenecks/138195#:~:text=start%20by%20running%20%E2%80%98stat%20unit%E2%80%99,to%20understand%20if%20it%E2%80%99s%20your

For example, once a GPU bottleneck is identified, use stat gpu to find the expensive pass. If Game is heavy, use stat game or Unreal Insights to find costly functions in the game code.

Understanding performance bottlenecks? — Epic forumshttps://forums.unrealengine.com/t/understanding-performance-bottlenecks/138195#:~:text=start%20by%20running%20%E2%80%98stat%20unit%E2%80%99,to%20understand%20if%20it%E2%80%99s%20your

Draw-call and lighting information from stat sceneRendering also helps identify scene-design changes, such as reducing object counts or revising lights.

AMD's Unreal Engine 4-specific patch discussion — Outer Space forumhttps://forum.outerspace.com.br/index.php?threads/amd-lan%C3%A7a-hoje-patch-especifico-para-unreal-engine-4-seu-calcanhar-de-aquiles-ser%C3%A1-que-a-partir-de-agora-vai-w.560116/#:~:text=,cost%2C%20draw%20call%20count%2C%20etc

You can also record statistics with stat startfile / stat stopfile and inspect them in Session Frontend or Unreal Insights, as discussed below.

Profiling & Optimizing for the best performance in Unreal Enginehttps://vrealmatic.com/unreal-engine/profiling#:~:text=Recording%20performance%20metrics

Profiling & Optimizing for the best performance in Unreal Enginehttps://vrealmatic.com/unreal-engine/profiling#:~:text=Session%20Frontend%20Viewer

Recording a short period allows later graphing and detailed function-level analysis.

3. Measuring performance and identifying problems in packaged builds

Measuring the actual packaged executable is very important, not just the editor.

The editor has overhead and editor-only work, so execution performance and memory use may differ from a real build.

Memory use and streaming-related stutters can change considerably between editor and packaged execution.

Unreal Engine Game Optimization on a Budget — Tom Loomanhttps://www.tomlooman.com/unrealengine-optimization-talk/#:~:text=Ideally%2C%20when%20profiling%20with%20tools,%E2%80%98Realtime%E2%80%99%20disabled%20and%20is%20minimized

Perform final validation in a packaged build, and confirm that optimizations found in the editor also help there.

Unreal Engine Game Optimization on a Budget — Tom Loomanhttps://www.tomlooman.com/unrealengine-optimization-talk/#:~:text=Ideally%2C%20when%20profiling%20with%20tools,%E2%80%98Realtime%E2%80%99%20disabled%20and%20is%20minimized

Ways to inspect statistics in a packaged build:

What to investigate in packaged execution: Pay attention to differences from editor play.

If FPS suddenly falls only after packaging, possible causes include fullscreen-specific load not present in the editor or features enabled by build settings, such as a different Lumen quality level.

Loading-related stutter also tends to become apparent after packaging.

Assets already loaded in the editor must be read from disk in the packaged environment, making streaming costs directly noticeable.

These storage- or memory-related bottlenecks can be investigated by recording statistics and examining LoadTime and File I/O events, or through logging such as log LogContentPolling and log LogStreaming.

Unreal Engine Game Optimization on a Budget — Tom Loomanhttps://www.tomlooman.com/unrealengine-optimization-talk/#:~:text=Ideally%2C%20when%20profiling%20with%20tools,%E2%80%98Realtime%E2%80%99%20disabled%20and%20is%20minimized

Unreal Engine Game Optimization on a Budget — Tom Loomanhttps://www.tomlooman.com/unrealengine-optimization-talk/#:~:text=,full%60%20%2A%20%60loadtimes.dumpreport

When Frame spikes at a particular moment, inspect nearby file reads and whether garbage collection, or GC, ran at that time.

4. VR bottlenecks and optimization

VR applications require very high frame rates, such as 90 or 120FPS, and low latency, making bottleneck diagnosis even more important than in ordinary games.

An HMD also requires rendering for both eyes, increasing the load.

The following covers VR-specific diagnosis and optimization.

Diagnosing CPU versus GPU limitation: Start as usual with stat unit, checking whether CPU or GPU time has no headroom.

Understanding performance bottlenecks? — Epic forumshttps://forums.unrealengine.com/t/understanding-performance-bottlenecks/138195#:~:text=start%20by%20running%20%E2%80%98stat%20unit%E2%80%99,to%20understand%20if%20it%E2%80%99s%20your

VR tends to be especially susceptible to GPU bottlenecks.

Rendering both eyes at high resolution can require processing a huge number of pixels.

The CPU also has VR-specific overhead, such as draw calls for both eyes and tracking-device updates, but it is less often the limiting factor than the GPU.

In either case, compare Game, Draw, and GPU to see which occupies the frame time.

If GPU is about equal to Frame, it is GPU-limited; a long Game or Draw time points to the CPU.

Main VR optimization points:

5. Hardware factors and their bottleneck symptoms

Bottlenecks can broadly originate in the CPU, GPU, memory, or storage. Typical symptoms and diagnostic methods follow.

6. Effective optimization techniques

Once the bottleneck is identified, optimize the relevant work. Broad categories are engine settings, assets/content, and code/algorithms.

This section has covered interpreting stat unit, combining related statistics, measuring packaged builds, VR considerations, hardware diagnosis, and optimization techniques.

Correctly identifying bottlenecks and choosing appropriate responses should improve and stabilize frame rates.

Choose techniques appropriate to your project's scale and target platform, working toward a comfortable user experience.

Tools such as Unreal Insights and the stat commands help analyze and address the limiting work, which is central to producing high-performance UE5 content.

References: Epic Games' official documentation and community forums; the Unreal Engine performance guide; community technical writing; and the Outer Space forum discussion of AMD's Unreal Engine 4-specific patch, among others.

AMD GPUOpen — Unreal Engine performance guidehttps://gpuopen.com/learn/unreal-engine-performance-guide/#:~:text=

Measuring Performance — Unreal Art Optimizationhttps://unrealartoptimization.github.io/book/process/measuring-performance/#:~:text=We%20can%20get%20more%20specific,is%20shown%20as%204%20numbers

Outer Space forum discussion of AMD's Unreal Engine 4-specific patchhttps://forum.outerspace.com.br/index.php?threads/amd-lan%C3%A7a-hoje-patch-especifico-para-unreal-engine-4-seu-calcanhar-de-aquiles-ser%C3%A1-que-a-partir-de-agora-vai-w.560116/#:~:text=,if%20dynamic%20resolution%20is%20enabled