profiler.retro

Read the ring buffer's recent history RETROACTIVELY — the latency-immune profiler. Because the ring is always recording (once enabled with ring on), it does not matter that this call lands seconds after the spike: the data is historical. The report is a DISTRIBUTION — every spike frame grouped by its dominant hotspot — so one call shows the whole picture, not a single anecdotal worst frame that might be a random hiccup. All times are EFFECTIVE (the agent's own execute cost is excluded, so your profiling calls never masquerade as game hitches). The snapshot is stored under a label, so you can drill into any cluster afterward with frame <label> or hotspots <label>.