Annotation Form v1 Performance Baseline¶
This benchmark records the v1 annotation-form baseline before AF2 and its Angular 22 comparison point after Track 0 and Phase 1. Phase 3 uses the Angular 22 measurement as its before/after reference.
Results¶
| Date | Commit | Machine | Initial render | Study navigation | Keystroke-to-paint p95 | Tab switch |
|---|---|---|---|---|---|---|
| 2026-08-04 | 72f38768c |
local dev | 4461 ms | — | 93 ms | 388 ms |
| 2026-08-06 | 4c1af0a20 |
GitHub Actions ubuntu-latest / Angular 22 |
8210 ms | 2665 ms | 111.3 ms | 3679 ms |
Seeded shape¶
The Playwright scenario creates one study and 100 textbox annotation questions: 60 Study questions and 40 Cohort questions. The cohort set has 20 root questions and 20 child questions whose Target.ParentId values each point to a root. It then creates 15 cohort units through the annotation UI before sampling keystroke-to-paint and tab-switch latency.
Invocation¶
From e2e/, with the local E2E infrastructure and .NET services running:
The test attaches the four metrics as perf JSON to the Playwright result and also prints them with console.table.
Angular 22 re-measure (2026-08-06)¶
The repository's isolated full-E2E workflow measured the Angular 22 platform on PR #2702, run 31059742925. The scenario passed on its second retry after two study-navigation timeouts; the successful attempt emitted the values above. Runner and retry variability mean these are a comparison baseline rather than a product service-level objective. Phase 3 must run the same isolated scenario and report its delta against this row.