A player reports lag. Start with that exact window.
Enter the reported local time and duration in Lag Analyzer, or inspect the last ten seconds. The incident pressure timeline shows whether the window contains a brief spike or sustained load, while the contributor views rank the recorded PBO and function activity.
Follow the candidate into its function and available source location. Use the timeline and measured contributors to decide what to investigate next instead of guessing which mod caused the report.
From an expensive PBO to the function doing the work.
Live Performance ranks the physical PBO packages and mapped runtime functions. Compare own VM time, total time, call count and worst call duration, then drill down into the functions and source locations behind a package. A broad mod-folder label is only the starting point.
Switch to VM Spikes to inspect individual slow calls and their recorded call paths. Own, total and nested time help distinguish work inside a function from work beneath it. Attribution depends on the capture and available source mapping; the overview and diagnostics expose that status.
Keep startup work visible after the server is running.
Configuration loading, mission bootstrap, trader spawning and other startup scripts can disappear from a rolling live view. Startup Capture preserves a dedicated startup window so you can return to that one-time workload later.
Inspect startup PBO activity and drill into the recorded functions, timings and calls. The capture status shows whether the window is frozen and whether attachment began late, so you can judge how much of the startup was actually observed.
Check whether the pressure is in scripts or the host.
Network & I/O puts process network throughput, file reads and writes, memory growth, handles and thread activity alongside the investigation. Hot-thread details help you distinguish a busy main thread from load spread across the process.
Transport telemetry is scoped to the selected DayZ process. Packet payloads are not captured. Correlate these measurements with PBO and VM activity before deciding whether the next check belongs in a script, a mod or the host configuration.
Come back to incidents you were not watching live.
Automatic Incidents keeps meaningful lag and freeze windows with their recorded severity, trigger and script or PBO context. The incident list gives you a place to start when a player reports a problem after it happened.
Select an incident to inspect the available function, call chain and nearby server events. Open the candidate PBO, copy a summary or save a report to continue the investigation with your team or a mod developer.
Give a crash a useful starting point.
Performance Debugger injects a native DLL into the DayZ server process. For an access violation, Crash Analyzer attempts to reconstruct the memory context associated with the pointer reported in the exception, alongside the recorded script context, PBO breadcrumbs and recent VM activity.
The report brings that evidence together to help trace the fault to a candidate package, function or source location. What can be reconstructed depends on the available memory and crash data; the report shows its findings and confidence for further investigation.
Keep the capture status and files close at hand.
Diagnostics brings together bridge state, source mapping, VM activity, process resources and startup capture status. Open the data folder, profiles or session report when you need the underlying files for follow-up.
Performance Debugger is a separate Windows product with its own license, authorization and download flow. Use it for performance investigations; the Server Sentry community platform provides player telemetry and Ask AI under a separate license. Check the product page for current installation and compatibility requirements.