Document after-phase0 benchmark comparison and hidden timer validation
This commit is contained in:
@@ -130,3 +130,14 @@ To verify performance gains and detect regressions in later phases:
|
||||
node perf/baseline.mjs --compare perf/results/baseline-2026-10-07.json
|
||||
```
|
||||
Prints an ASCII/Markdown delta comparison table highlighting percentage changes across wire bytes, boot duration, and update overhead.
|
||||
|
||||
---
|
||||
|
||||
## 6. Hidden Timers Verification (`perf/hidden-timers.mjs`)
|
||||
|
||||
Verifies that non-playback UI intervals (`chips`, `reanchor`, `rotateChips`, `flush`, `checkBuildTag`) suspend while the document is hidden and restore upon visibility, while essential background intervals (`maybeCheck`, 120s resume check) remain active:
|
||||
```bash
|
||||
node perf/hidden-timers.mjs
|
||||
```
|
||||
Exits with code 0 on success, or code 1 if any interval fails to pause, fails to resume, or if page errors occur.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user