docs(perf): close Slice B with full-bake evidence

This commit is contained in:
Erik 2026-07-24 14:10:50 +02:00
parent 90bf6bbf45
commit 49f3a48ee6
5 changed files with 196 additions and 20 deletions

View file

@ -2,8 +2,8 @@
**Date:** 2026-07-24
**Status:** Slice A tooling and diagnostic RDP baselines landed; Slice B active.
The physical-local Slice A gate still blocks Slice C.
**Status:** Slice A tooling and diagnostic RDP baselines landed; Slice B
complete. The physical-local Slice A gate still blocks Slice C.
**Scope:** Reconcile and sequence the existing Modern Pipeline (`MP`) and
Linux/headless (`LH`) tracks using the 2026-07-24 connected performance audit.
@ -578,7 +578,7 @@ effect, portal windows, and contention stacks are committed in
[`../research/2026-07-24-slice-a-rdp-baselines.md`](../research/2026-07-24-slice-a-rdp-baselines.md)
and its machine-readable companion. They prove the tooling is usable but are
diagnostic-only. The physical-local AMD-display repetitions remain required,
so Slice C is still blocked. Slice B is baseline-independent and is now active.
so Slice C is still blocked. Slice B was baseline-independent and is complete.
### Slice B — Finish MP1b EnvCell dedup and full bake
@ -599,6 +599,13 @@ so Slice C is still blocked. Slice B is baseline-independent and is now active.
sample equivalence tests pass; duplicate EnvCells share blob offsets; no runtime
code consumes the pak yet.
**Completed 2026-07-24:** 729,888 EnvCell keys collapsed to 17,117 unique
geometries plus 712,771 aliases (42.6×), with 751,141 total keys, 38,370
physical blobs, zero failures, a 28,192.4 MiB artifact, and an 81.4-second
validated atomic publication. The gate also exposed and corrected a real
collision in WorldBuilder's legacy 31× geometry hash. Evidence:
[`../research/2026-07-24-slice-b-full-bake-report.md`](../research/2026-07-24-slice-b-full-bake-report.md).
### Slice C — Runtime prepared-asset source and MP1c cutover
**Purpose:** Remove mesh/texture decode from portal frames.
@ -1116,12 +1123,11 @@ an improvement" carries the same evidence burden as a regression claim.
## 14. Current execution point
Slice A's tooling and diagnostic RDP evidence are complete. Its physical-local
exit gate remains open. Execute **Slice B** now: it is baseline-independent,
completes an implementation already present in the tree, and directly attacks
the benchmark's largest process-wide allocation source. Do not start Slice C
until the capped/uncapped nine-stop and pinned dense-Arwic routes have been
repeated on the physical local AMD display path and committed.
Slice A's tooling and diagnostic RDP evidence are complete, and Slice B's
prepared-content bake is complete. The next implementation is Slice C, but its
physical-local prerequisite remains open. Do not start Slice C until the
capped/uncapped nine-stop and pinned dense-Arwic routes have been repeated on
the physical local AMD display path and committed.
The intended order is therefore: