Bevy 0.19 — diagnostics and profiling

When to use this skill

• A frame, render pass, worker pipeline, or upload path needs causal evidence.
• A queue/task system needs stable gauges, counters, latency, and high-water marks.
• Performance claims must pass native, Steam Deck, or browser acceptance budgets.
• Render GPU diagnostics are absent or disagree with CPU traces.

Diagnostics answer “what is happening over time?” Tracing answers “where did this execution spend time?” Render diagnostics expose pass-level renderer measurements. Use all three, but do not treat any one of them as proof of a bottleneck.

Canonical pattern