You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 135cb20
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/QUALITY_SNAPSHOTS.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,16 +17,20 @@ A metric blocks when it exceeds both its absolute and relative budget:
17
17
| Server startup P50 | 5 ms / 100% | 10 ms / 50% | 100 ms / 50% |
18
18
| Server startup P95 | 50 ms / 200% | 50 ms / 100% | 750 ms / 100% |
19
19
| Full refresh P50 | 25 ms / 30% | 50 ms / 30% | 100 ms / 50% |
20
-
| Full refresh P95 |1,000 ms / 100% |5,000 ms / 100% |1,000 ms / 50% |
20
+
| Full refresh P95 |50 ms / 50% |250 ms / 100% |300 ms / 100% |
21
21
| Time to first environment P50 | 20 ms / 100% | 25 ms / 50% | 150 ms / 50% |
22
-
| Time to first environment P95 |250 ms / 100% |500 ms / 100% |750 ms / 100% |
22
+
| Time to first environment P95 |25 ms / 100% |100 ms / 100% |250 ms / 100% |
23
23
| Cold refresh P50 | 100 ms / 50% | 150 ms / 50% | 250 ms / 50% |
24
24
25
-
Each cell is `absolute / relative`. The Linux and Windows budgets plus the macOS P50 budgets reflect observed GitHub-hosted runner variance from 11 consecutive main-branch baselines. Tighten them when a noisy path is fixed rather than normalizing a known regression into the baseline.
25
+
Each cell is `absolute / relative`. The warm P50 and server-startup budgets reflect observed GitHub-hosted runner variance from 11 consecutive main-branch baselines. Tighten them when a noisy path is fixed rather than normalizing a known regression into the baseline.
26
26
27
-
The macOS P95 budget recalibration is tracked by issue #507 and follows PR #506's fix for issue #504. It uses three unchanged-content pull-request runs and the exact merged baseline at `f0c62d9`; the resulting absolute headroom is four to six times the observed post-fix run-to-run range.
27
+
The macOS server-startup P95 budget recalibration is tracked by issue #507 and follows PR #506's fix for issue #504. It uses three unchanged-content pull-request runs and the exact merged baseline at `f0c62d9`; the resulting absolute headroom is four to six times the observed post-fix run-to-run range.
28
28
29
-
Schema v2 records `full_refresh` and `time_to_first_env` from the warm member of each pair and adds cold refresh/time-to-first distributions. While the exact base still uses schema v1, cold P50 is checked against explicit absolute ceilings of 500ms on Linux, 750ms on Windows, and 1,000ms on macOS. Once both snapshots use schema v2, the table's dual budgets apply.
29
+
The warm refresh and warm time-to-first P95 budgets were recalibrated in issue #511 after PR #510 separated cold and warm samples. Three unchanged-code PR runs plus the exact schema-v2 baseline at `ad7ca14` retain at least 2.5 times the observed absolute run-to-run range.
30
+
31
+
Schema v2 records `full_refresh` and `time_to_first_env` from the warm member of each pair and adds cold refresh/time-to-first distributions. During its one-time rollout, comparisons against a schema-v1 base checked cold P50 against explicit absolute ceilings of 500ms on Linux, 750ms on Windows, and 1,000ms on macOS. Schema-v2-to-v2 comparisons use the table's dual budgets.
32
+
33
+
The cold P50 budgets were calibrated in issue #509 using two unchanged-head all-platform runs and the final pull-request validation.
30
34
31
35
The dual budget avoids failing on tiny percentage changes while still blocking material latency regressions. Warm tail metrics remain mandatory; cold P95 remains diagnostic because a single host event can dominate it, while cold P50 blocks delays that affect the independent cold iterations consistently.
0 commit comments