From 6301e4dbeac56745b5ca41189ee589a9f5bc0561 Mon Sep 17 00:00:00 2001 From: Erik Date: Sun, 30 Aug 2026 16:23:03 +0200 Subject: [PATCH] docs: Campaign FW - the FW3.4 perf pair numbers; the stop rule triggers Co-Authored-By: Claude Fable 5 --- docs/plans/2026-08-30-campaign-fw-frame-walk.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/plans/2026-08-30-campaign-fw-frame-walk.md b/docs/plans/2026-08-30-campaign-fw-frame-walk.md index 94b9521f..ea561836 100644 --- a/docs/plans/2026-08-30-campaign-fw-frame-walk.md +++ b/docs/plans/2026-08-30-campaign-fw-frame-walk.md @@ -434,6 +434,18 @@ diagnostic read; interiors 3.3 ms) - candidates: collapse the two-pass walk, batch per-cell shells, cache the outdoor-statics index, cut per-segment rebinds. +**FW3.4 PERF PAIR (2026-08-30, same session/conditions, exact +binaries):** dense Arwic uncapped, PRE (@87853359, old static path) +vs POST (@3a05d659, walk-driven): CPU p50 23.6 -> 31.6 ms (+33.5%), +p95 36.3 -> 44.3 ms (+21.9%), alloc p50 133 KB -> 1,920 KB/frame +(14x). THE +/-20% STOP RULE TRIGGERS. Sources are the flagged known +costs (two walk passes/frame, per-cell single-segment submissions +with full section rebinds, per-cell record-array copies in the world +data). FW3.4a fixes them (single walk pass; prepare-once/draw-ranges +- the deferred-alpha architecture; pooled record segments), then the +pair re-measures against the SAME baseline; the owner decision only +triggers if it still exceeds 20% after the known fixes. + - **FW3.4 — perf checkpoint + gates.** BASELINE CORRECTION: the 519.7 fps / 1.869 / 1.096 ms numbers are the Aerlinthe ordinary-production profile, NOT dense Arwic. Before the cutover