Profiling with the SwiftUI Instrument

Performance work without measurement is guesswork. The SwiftUI Instrument in Instruments shows exactly which views update and how often.

In Xcode, choose Product > Profile (or Command-I) to launch Instruments, then pick the SwiftUI template. Run your app and exercise the slow screen.

The instrument reports how many times each view’s body was evaluated. Unexpectedly high counts point straight at over-eager recomputation.

Besides counts, look at how long bodies take. A body called rarely but taking 30ms is as bad as one called constantly but cheaply.

The instrument explains why a view updated—which state, binding, or observed property changed. This pinpoints the trigger you need to narrow.

If a view is created and destroyed repeatedly instead of updated, you will see new instances in the timeline. That usually signals an identity bug (index ids, branch flips).

Pair the SwiftUI Instrument with the Hangs and Animation Hitches instruments to connect a heavy body to a visible stutter on screen.

Read whether time is spent in a view’s own body or in its children. This tells you whether to optimize the view itself or push the fix down the tree.

Profile the actual user flow—scrolling a full list, typing in a field—not a static screen. Performance problems appear under interaction, not at rest.

Apply one change (narrow state, add Equatable, split a view), then profile again. Confirm body counts dropped before moving on; avoid stacking unverified "optimizations".

Profile a Release build. Debug builds disable optimizations and add overhead, giving misleading numbers that do not reflect shipping performance.

Test your understanding of the SwiftUI Instrument.

The SwiftUI Instrument shows body evaluation counts, durations, and the cause of each update, exposing over-recomputation and identity churn. Pair it with Hangs and Animation Hitches, distinguish self vs children time, and profile realistic flows in a Release build.

Optimize iteratively—measure, apply one fix, re-measure—so every change is verified by data.