Performance and Efficiency Awareness

Intent

• Treat budgets (frame time, network round-trips, server CPU, on-chain gas) as first-class requirements.
• Prevent regressions by profiling early, not after user complaints.

Inputs

1. Existing SLAs/budgets per platform (FPS, TTI, API latency, contract gas caps).
2. Representative workloads, datasets, replays, or load scripts.
3. Tooling: profilers, flamegraphs, shader analyzers, gas estimators, Lighthouse, etc.