Skip to content

Performance Diagnostics Panel ​

The Performance Diagnostics panel gives you live, at-a-glance insight into engine health — frame rate, CPU, RAM, VRAM, and per-media stream health — without any measurable impact on playback performance when the panel is closed.

Diagnostics panel open

Opening the Panel ​

Click the 📊 diagnostics icon in the header toolbar. The panel appears as a floating, draggable overlay. Click the icon again (or the × button on the panel) to close it.

Cost when closed: The panel polls only while it is open and un-minimised. Closing or minimising it stops the refresh timer, so it makes no diagnostics requests and does no measuring work until you open it again.

Panel States and Their Cost ​

StateHTTP requestsCPU overhead
Closed (default)NoneZero
MinimisedNoneZero — last values frozen
Open, active1 per second (~2 KB)< 0.1 %

What the Panel Shows ​

All system metrics (FPS, CPU, RAM, VRAM) are reported by the playback engine, not by the browser — the readings stay accurate even when the web UI runs on a different machine than the engine.

System Resources ​

Engine FPS ​

The current rendering framerate reported by the playback engine.

ColourRangeMeaning
🟢 Green≥ 57 fpsHealthy
🟡 Yellow48–57 fpsWarning — mild load
🔴 Red< 48 fpsCritical — visible stuttering likely

CPU Usage ​

Overall system CPU percentage as reported by the engine.

ColourRange
🟢 Green< 75 %
🟡 Yellow75–90 %
🔴 Red> 90 %

RAM ​

System memory. Shows used / total with a colour-coded bar.

ColourUsage
🟢 Green< 75 %
🟡 Yellow75–90 %
🔴 Red> 90 % — may cause stuttering

GPU VRAM ​

Available on NVIDIA GPUs with driver support. Shows used / total with the same colour coding as RAM. Only visible when VRAM data is available.

GPU Engine Utilization ​

New in 3.3. Per-engine-class GPU utilization, shown when the backend can report it (older engines/systems without the counter simply show nothing extra):

RowMeaning
Video DecodeThe GPU's hardware video-decode engine (NVDEC / QuickSync / DXVA). Above 0 % while a clip plays means hardware decode is genuinely running; near 0 % with high CPU usually means a software fallback is in effect.
Video EncodeThe GPU's hardware video-encode engine (NVENC / QuickSync) — used by export and preview encoders.
CopyThe GPU's copy engine (GPU↔CPU transfers). High usage while a clip plays means decoded frames are round-tripping through system RAM; it stays near zero when zero-copy GPU decode is active for that clip.

Media Status Summary ​

A quick count of currently active media items:

  • Videos — number of video clips being decoded
  • Images — number of still images loaded
  • Live Inputs — number of live sources (NDI, Spout, capture card) active

Per-Media Diagnostics ▸ ​

Expand this collapsible section to see detailed metrics for every playing clip:

ColumnDescription
Buffer HealthHow full the decode pre-buffer is (green ≥ 2 frames, red = 0)
Decode TimeTime to decode one frame (ms); > 33 ms on a 30 fps clip is a warning
Cycle FPSThe decode loop rate; < target FPS indicates CPU saturation
TimingHow closely actual frame delivery matches the target frame interval
ResolutionWidth × Height of the decoded stream

Automatic issue detection flags common problems with an amber or red indicator and a short explanation.

Common Issues and Remedies ​

Tracking Down Stuttering ​

When playback stutters, read the panel in this order — the first value that is amber or red is usually the cause:

  1. Engine FPS — amber or red means the rendering pipeline is overloaded.
  2. CPU Usage — red means the system CPU is saturated; reduce the media load.
  3. Cycle FPS (per-media) — amber or red means CPU overload, or a codec that is too demanding.
  4. Buffer Health (per-media) — amber or red means decoding is too slow, or the storage cannot keep up.
  5. RAM — red means the system is running out of memory.
  6. Decode Time (per-media) — above 33 ms on a 30 fps clip, switch to HAP or a hardware-accelerated codec.

Symptom Reference ​

SymptomLikely causeFix
Engine FPS redGPU overloadedReduce output resolution, switch to HAP codec
CPU > 90 %Too many software-decoded streamsSwitch H.264 to HAP or enable QuickSync
Buffer Health redStorage too slowUse NVMe SSD; avoid network drives
Decode Time > 33 msCodec too heavy for CPUSwitch to HAP Q or enable Intel QuickSync
VRAM criticalToo many full-res texturesReduce simultaneous media layer count

Panel Controls ​

ControlFunction
Minimise iconCollapses panel to title bar; stops auto-refresh
Refresh buttonManually fetches a fresh data snapshot
Close (×)Hides panel; all background activity stops
Drag title barReposition the panel anywhere on screen

Exaplay 3 User Documentation