Performance Measurement

What problem does it solve?

Carmack's discipline: never optimize without measuring. Instruments, signposts, budgets, thermal management, profiling methodology. Trigger on: 'it feels slow', 'where is the bottleneck?', profiling, Instruments, 'CPU usage is high', 'memory leak', frame drops, 'battery drain', thermal throttling, performance budget, 'how do I measure?', Time Profiler, Allocations, os_signpost, MetricKit.

Core Features & Use Cases

• Establish performance budgets before optimizing: total budget derived from target FPS, decompose into subcomponents such as rendering, preprocessing, inference, and UI updates
• Provide instrumentation templates and measurement methodologies (Time Profiler, Allocations, os_signpost, MetricKit)
• Guidance on thermal management, warm-up, aggregation, and reporting (p50/p95) to support production-grade performance
• Real-world scenarios: ensuring features stay within budgets in both lab profiling and field use

Quick Start

Run a baseline profile on your target workflow using Time Profiler and review allocations to identify the top bottleneck