Using the performance tab
The Performance tab turns the last few seconds of frame work into a small dashboard. It is designed to show where a frame goes, not to replace a profiler.
What is sampled
The host samples while the Performance tab is visible, at most every 0.25 seconds. Each graph keeps up to 120 samples. The panel refreshes roughly once per second, so the numbers are recent but not instantaneous.
The summary cards
| Card | Meaning |
|---|---|
| FPS | Whole frames per second derived from the latest wall-clock frame time. The small line also shows the frame time in milliseconds. |
| CPU | Process-wide CPU usage percentage and the current thread count. The first sample has no baseline, so it reports zero. |
| Managed | Managed heap bytes. The secondary line shows the process working set. |
| GC | Gen 0, gen 1 and gen 2 collection counts. |
The graphs
Three bar graphs show the retained history. They use fixed vertical scales so different runs are comparable:
| Graph | Scale | Use it to spot |
|---|---|---|
| Frame time | 33 ms full height | Overall hitches and frames that missed the display budget. |
| Layout time | 16 ms full height | Layout rebuilds caused by state, styles or viewport changes. |
| Render time | 16 ms full height | Display-list submission and GPU-facing work. |
A tall frame bar with short layout and render bars points at work outside the measured passes, such as waiting on the platform or another thread. A tall layout bar points at geometry churn. A tall render bar points at display-list or submission cost.
Frame budgets
| Refresh rate | Budget per frame |
|---|---|
| 60 Hz | 16.7 ms |
| 120 Hz | 8.3 ms |
| 144 Hz | 6.9 ms |
The graph scales are diagnostic aids, not hard budgets. A 16 ms layout bar on a 144 Hz display is already too large for a smooth frame.
A practical workflow
- Open the Performance tab and leave it visible.
- Reproduce one interaction, then stop. Avoid a long sequence that mixes several causes.
- Compare the three graphs. Is the spike in layout, render, or only frame time?
- Switch to Elements and inspect the subtree involved. Check for unnecessary class changes, large text updates, or layout-affecting styles.
- Reduce the work: keep subtrees stable, key list items, memoise derived data, and avoid triggering full-tree changes for local state.
What it does not tell you
- It does not attribute time to a specific C# method; use a sampling profiler for that.
- It does not capture GPU timings on every driver.
- It does not sample while the tab is hidden.
- It is desktop/Android inspector tooling; use browser devtools for the WASM host.