feat(streaming): establish cost budget ledger
Add the validated frame-work profile, deterministic completion charges, and shadow admission meter before enforcing the scheduler in Slice E2. Lifecycle artifacts now expose elapsed work, would-yield limits, backlog bytes/age, and pending owner ledgers without changing accepted execution. Tests: dotnet build AcDream.slnx -c Release --no-restore; dotnet test AcDream.slnx -c Release --no-build --no-restore (8124 passed, 5 skipped)
This commit is contained in:
parent
2945896a6f
commit
ac45cb1bd7
14 changed files with 1280 additions and 71 deletions
|
|
@ -708,6 +708,16 @@ replace state produced by another job. CPU mesh extraction may still be schedule
|
|||
onto `ObjectMeshManager`'s thread-safe work queue, but the worker never publishes
|
||||
partially hydrated cell membership or shell placement to the renderer.
|
||||
|
||||
`RuntimeOptions.StreamingWorkBudgets` is the single startup profile for
|
||||
update-thread streaming cost. `StreamingWorkMeter` owns the frame-scoped
|
||||
admission ledger; `LandblockStreamResultCost` assigns deterministic charges to
|
||||
immutable completion arrays and logical retained entries without claiming to
|
||||
measure CLR allocator overhead. During Slice E1 the ledger is observational:
|
||||
the existing scheduler still executes its accepted work, while lifecycle
|
||||
artifacts record would-yield limits, elapsed work, retained backlog bytes/age,
|
||||
and pending publication/retirement counts. Enforcement belongs to the explicit
|
||||
Slice E scheduler, not to presentation owners or the worker.
|
||||
|
||||
### World-reveal readiness ownership
|
||||
|
||||
`WorldRevealCoordinator` is the single App-layer owner of each login or portal
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue