Profiling with Perfetto

The engine’s Perfetto integration emits track events through the system backend. Starting the editor alone does not create a finished trace file: an instrumented build and configured system recording session are required.

Procedure

1. Prepare a separate build with profiler=perfetto. Point profiler_path at a directory containing sdk/perfetto.cc, or perfetto.cc directly. Without a path, configuration checks its expected dependency directory and stops if unavailable.
2. Configure Perfetto system recording on the target platform with the track-events data source. Opening the browser viewer does not mean a system backend is collecting application events.
3. Run a short reproduction, finish recording and open the resulting trace in Perfetto UI.
4. Correlate engine zones with thread scheduling. Retain recording configuration, duration, device and exact build.

Limits

Configuration rejects profiler_sample_callstack and profiler_track_memory for this backend. It ignores profiler_record_on_demand and profiler_broadcast_address; do not transfer Tracy settings unchanged.

An empty track calls for checking the event source, process and instrumentation. It does not prove the application did no work. No system session, trace capture or track rendering was executed here; source review establishes the integration contract.