Skip to content

A fast 2D and 3D game engine — TypeScript SDK, C++/WebAssembly core, visual editor. Ship one project to web, desktop, WeChat MiniGames, playable ads, and native Android / iOS.

docs(residency): publication is still one number, and a total is not a mechanism

esengine980caea12197
diff --git a/bench/residency/README.md b/bench/residency/README.md
index 9472799b5..6f641cfa9 100644
--- a/bench/residency/README.md
+++ b/bench/residency/README.md
@@ -180,7 +180,7 @@ while still inside the prefetch radius is speculated about again the instant it
goes — walking away from a place fetches it a second time. Held to in
`sdk/tests/world-residency.test.ts`, both directions.
-## Streaming Delivery v1 — frozen
+## What delivery has, and what it still owes
What the three benches together establish:
@@ -189,11 +189,15 @@ What the three benches together establish:
- **Delivery** readies content before demand, and it works: 100% hit rate on
ordinary movement, 0% when speculation is disabled, and a hit costs publication
alone.
-- **Publication** is the only cost demand cannot escape: ~6 ms of spawn for a
- 249-entity cell, landing on a 2.8–8.4 ms frame. Nothing here needs a budget
- scheduler.
- **Cancellation** gives back what speculation acquired, receipts included.
+**Publication is the one cost demand cannot escape, and it is still a single
+number.** ~6 ms of `spawn` for a 249-entity cell, landing on a 2.8–8.4 ms frame —
+but what that 6 ms IS (entity allocation, component writes, hierarchy, and which
+subsystem each write reaches) this measures nowhere. Until it does, "nothing here
+needs a budget scheduler" is a reading of a total, not of a mechanism, and
+delivery is not finished.
+
Not in v1, deliberately: velocity prediction, adaptive prefetch radius, memory
budget, priority scheduling. Each of them now has a number that would justify it,
and none of them has one yet.