From 658cab1bf5a49658f22e2fe49fc89d83804db80f Mon Sep 17 00:00:00 2001 From: 4gray Date: Wed, 14 Oct 2026 22:39:36 +0200 Subject: [PATCH] test(perf): widen the J3 mutation slack to 20 The rerun of a8505e0f9's journeys read 733 with one fifth-call iteration at 750, over the 749 limit; the run before it read 736 throughout. The usual value moves between 731 and 736 within one commit and a fifth bridge call adds exactly 17, so the band tops out at 753: slack 20. Co-Authored-By: Claude Opus 5.5 --- docs/architecture/performance-journeys.md | 24 ++++++++++++----------- tools/performance/journey-baselines.json | 4 ++-- 2 files changed, 15 insertions(+), 13 deletions(-) diff --git a/docs/architecture/performance-journeys.md b/docs/architecture/performance-journeys.md index ddb4db7d0..163e7dba2 100644 --- a/docs/architecture/performance-journeys.md +++ b/docs/architecture/performance-journeys.md @@ -1410,22 +1410,24 @@ changes) and the wall-clock entries did not move. Under still sees the jump that the journey no longer measures. `playback/renderer.domMutationsToPlaying` 733 is validated by #1817 and is -the one runtime counter enforced with slack. #1817 windowed the EPG +enforced with slack. #1817 windowed the EPG timeline: on the runner the counter fell from 6,182 to 731, `renderer.longTasks` from 1 to 0, and the click→`playing` P50 from 221-341 ms (four `master` runs) -to 196-215 ms (three dispatched runs of the branch). It is not identical -between commits: 731, 732, 733, 734 or 736 since #1817, and 748 in an -iteration where a fifth bridge call (`updateRemoteControlStatus`) lands -before `playing`. `slack` 16 covers that band; the regression it guards, the -timeline rendering the whole schedule again, is about 5,000 mutations above -it. `evidenceRun` 38311314484 (f60d79701) read 733 in every iteration. +to 196-215 ms (three dispatched runs of the branch). It is not identical: the +usual value is 731 to 736, and it moves between runs of the same commit (733 +and 736 for a8505e0f9). An iteration where a fifth bridge call +(`updateRemoteControlStatus`) lands before `playing` adds exactly 17 +(731→748, 733→750). `slack` 20 covers the top of that band, 736 + 17 = 753; +the regression it guards, the timeline rendering the whole schedule again, is +about 5,000 mutations above it. `evidenceRun` 38311314484 (f60d79701) read +733 in every iteration. The entry carries `"autoTighten": false`, so the weekly tightening leaves it alone: three runs that all read 731 would lower `value` to 731 and the limit -to 747, below the 748 of a normal fifth-call iteration. Lower it by hand, and -only with runs showing the top of the band fell too (a fifth-call iteration -at or below the new `value` + `slack`). Remove the slack and the flag once the -fifth call's race is gone and `master` runs agree. +to 751, below the 753 of a normal fifth-call iteration on a 736 run. Lower it +by hand, and only with runs showing the top of the band fell too (a +fifth-call iteration at or below the new `value` + `slack`). Remove the slack +and the flag once the fifth call's race is gone and `master` runs agree. The two J4 entries, `search/renderer.ipcCallsPerSearch` 1 and `search/renderer.sqlStatementsPerSearch` 2 (#1899, `evidenceRun` diff --git a/tools/performance/journey-baselines.json b/tools/performance/journey-baselines.json index 610e38952..e3111c72c 100644 --- a/tools/performance/journey-baselines.json +++ b/tools/performance/journey-baselines.json @@ -123,12 +123,12 @@ "renderer.domMutationsToPlaying": { "value": 733, "unit": "mutations", - "slack": 16, + "slack": 20, "autoTighten": false, "updatedAt": "2026-10-13", "evidencePr": 1817, "evidenceRun": "https://github.com/4gray/iptvnator/actions/runs/38311314484", - "measuredWith": "pnpm run perf:journeys (ubuntu-latest, xvfb); 731-736 across master commits since #1817, 748 with a fifth bridge call" + "measuredWith": "pnpm run perf:journeys (ubuntu-latest, xvfb); 731-736 across runs since #1817, +17 (up to 753) when a fifth bridge call lands before playing" }, "renderer.httpRequestsToPlaying": { "value": 2,