From 409a014ff0ebc1b66fb87f7a0b3f5b306b26d0e6 Mon Sep 17 00:00:00 2001 From: rdbtCVS <87152661+rdbtCVS@users.noreply.github.com> Date: Sun, 18 Oct 2026 00:33:48 +0100 Subject: [PATCH] Report the progressive title RSS comparison and its limits --- docs/performance/startup-stage-3.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/performance/startup-stage-3.md b/docs/performance/startup-stage-3.md index a728da34b..330269889 100644 --- a/docs/performance/startup-stage-3.md +++ b/docs/performance/startup-stage-3.md @@ -41,3 +41,5 @@ Screenshots from these probes: - [World after the tail join](../../benchmarks/startup-stage-3-20261018/world-after-rest.png) The full parity selection against `origin/main` also includes the unmerged Stage 2 ancestors (313 harnesses). The local run was bounded at 30 minutes; its log recorded passes for `active_effects`, `active_effect_tick` and `anchor`. The remainder needs CI or a longer dedicated run. The client Rust tests, focused startup probes and memory measurements are separate from that incomplete parity run. + +Progressive-title RSS was measured separately with audio disabled, render distance 4 and a 30 FPS cap, using separate temporary game directories. The first 30-second pair measured 1,055,132 KiB before and 1,721,772 KiB after. A warm 60-second repeat in reverse order measured 1,031,948 KiB before and 1,145,776 KiB after: an increase of 113,828 KiB (about 111 MiB, 11%). These launches ran during compilation and did not advance through startup/streaming identically. They establish a memory cost to investigate, not a claim of RSS parity; a quiet-machine cold/warm comparison remains needed before merging the stack.