erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs(perf): record corrected Slice A RDP baselines

Browse source
This commit is contained in:
Erik 2026-07-24 13:29:23 +02:00
parent 24f898c54d
commit 05a22dee99
4 changed files with 256 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

28
docs/plans/2026-07-24-modern-runtime-architecture.md
View file

@ -2,7 +2,8 @@
**Date:** 2026-07-24
**Status:** Planning complete; implementation not started
**Status:** Slice A tooling and diagnostic RDP baselines landed; Slice B active.
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.
@ -569,6 +570,16 @@ capped-local nine-stop baselines, a pinned dense-town uncapped baseline
(name the town, pin the camera), and per-portal allocation/frame timelines
around each teleport materialization.
**Progress (2026-07-24):** the corrected GL timer, per-frame history, process
counter/trace capture, screenshot comparison, reference configuration, binary
provenance, and route-bound stationary sampling have landed. Corrected capped
and uncapped nine-stop RDP routes, a pinned dense-Arwic RDP sample, observer
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.
### Slice B — Finish MP1b EnvCell dedup and full bake
**Purpose:** Make the existing pak physically usable.
@ -1103,15 +1114,14 @@ an improvement" carries the same evidence burden as a regression claim.
---
## 14. Recommended starting point
## 14. Current execution point
Begin with **Slice A**, then **Slice B**.
Slice A is small and makes all later GPU and frame gates honest. Slice B completes
an implementation already present in the tree and directly attacks the
benchmark's largest allocation source. The first meaningful runtime cutover is
Slice C; do not begin the render-scene migration before the portal content storm
has been removed and measured.
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.
The intended order is therefore: