jb/harness-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: retain failed paired run and isolate verification bottlenecks

Browse Source
This commit is contained in:
jb
2026-09-21 13:29:08 -04:00
parent acd57ae2a7
commit f2e42f5faf
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plans/fast-browser-performance.md
+5 -3
View File
@@ -3,8 +3,8 @@
## Status
- Status: active
- Current phase: integrated verification; A/B/C/D committed, live runtime gate passed, 20 paired benchmark runs executing.
- Next safe action: inspect paired results, run full verification, synchronize documentation and obtain independent review.
- Current phase: diagnosing integrated benchmark failure; live runtime gate passed but 20-pair workflow verification exposed a popup-close race and mixed total timings.
- Next safe action: add safe per-operation timing to the existing benchmark and diagnose close/readiness semantics before retaining a performance claim.
## Request and scope
@@ -118,4 +118,6 @@ After safe integration, make one record-only closure commit, prove reachability,
- Baseline real Chromium development validation passed (opt-in test exit 0, no skips).
- A corrections: alternate pair order, expose per-density timing/count evidence, independently check saved fixture data, make popup postcondition stable, fail/retain evidence on cleanup or missing counters, and sanitize errors to safe categories. This completes existing acceptance criteria without changing public scope.
- A correction smoke passed; historical pre-correction transient popup-close failure is preserved at `/tmp/performance-smoke-final.json`, not attributed to concurrent editing. Stable paired measurements must include all failures.
- Next safe action: inspect `/tmp/fast-browser-performance-20-pairs.json` after terminal callback, then full verification and independent review.
- First stable 20-pair result `/tmp/fast-browser-performance-20-pairs.json`: exit 1; baseline 19/20 and optimized 18/20 warm flows passed, all six cold attempts passed, counters/cleanup complete. Failures are popup-close verification (optimized samples 10/13, baseline sample 20). 60-control median observation 79 to 30ms; 10-control 16 to 7ms, but aggregate medians 445 to 551ms. These are diagnostic results, not acceptance.
- Additional bounded assignments: browser-hotpath read-only diagnosis (8 minutes), performance-benchmark safe per-operation timing in its existing four paths (15 minutes). Before state acd57ae, product paths clean; only parent performance doc untracked. No scope/API/security expansion: this is required existing benchmark verification.
- Next safe action: inspect diagnostic delivery, correct confirmed contract-preserving hot-path issues, then rerun the original paired command. Preserve every failed result.