From d3e8747c182eb5bdf1d165aacc59519cfc955b35 Mon Sep 17 00:00:00 2001 From: Valentin Popov Date: Sat, 18 Jul 2026 13:06:44 +0400 Subject: feat(game): timestamp load progress trace --- docs/tomes/05-render.md | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'docs') diff --git a/docs/tomes/05-render.md b/docs/tomes/05-render.md index 7dfd3db..ceea417 100644 --- a/docs/tomes/05-render.md +++ b/docs/tomes/05-render.md @@ -1132,6 +1132,16 @@ bounded probe can therefore retain both MAT0 and TEXM request milestones even when a later event is last. The behavior is diagnostic persistence only: it does not alter graph traversal, resource validation, or rendering. +Each trace row now keeps the phase name first and appends a monotonic +`elapsed_ms=` field from one process-local `Instant`; successful completion +is appended rather than overwriting the trace. A short rebuilt Part 2 probe +confirmed real timestamps from `Map` at 5 ms through `GraphVisualTextures` at +2,389 ms, then later MAT0 request milestones at 28,841 and 35,486 ms. The +probe was deliberately terminated and provides no frame/GPU result. These +timestamps measure whole elapsed intervals, including archive I/O, allocation, +validation, cache effects and progress-file writes; they are not per-parser +benchmarks. + A rebuilt executable then ran a controlled 180-second Part 2 `Autodemo.00` probe with the append-only trace. Before exact-child termination it recorded `GraphVisualTextureRequests(64)`, `GraphVisualMaterialRequests(100)`, and every -- cgit v1.2.3