docs(perf): restate idle-memory target per-platform, close the 0.5 perf pass#30
Merged
Merged
Conversation
…rf pass The flat <250MB idle target was structurally unreachable on Windows: the empty WebView2 shell alone measures 248MB private (six-process floor, no supported trim switch), while the app adds only ~32MB for a medium repo (7MB JS heap). Restate PRD 8 per-platform, following the cold-start row's own precedent: macOS <250MB (unchanged, confirm on the Mac box), Windows <300MB private + <50MB app-attributable over the empty shell, Linux TBD at the GNOME/KDE platform pass. Windows passes both restated figures. Flips the last 0.5 perf item: ROADMAP's performance pass and TASKS' idle-memory line go to done, perf-baseline's verdict tables + webview finding 2 record the resolution.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes the last open item of the 0.5 performance pass. The flat < 250MB idle-memory PRD §8 target was structurally unreachable on Windows: the empty WebView2 shell (no repo open) already measures 248MB private — the six-process floor consumes 99% of the budget before any app data — while the app itself adds only ~32MB for a medium repo (7MB JS heap). WebView2 exposes no supported process-count switch (
--single-process-style flags are unsupported and risk rendering breakage), so trimming the floor was never a real lever.The target is restated per-platform, following the PRD §8 cold-start row's own precedent (1.0s Mac / 1.5s Windows):
Changes:
PRD.md§8 — memory row restated + dated rationale note under the tabledocs/perf-baseline.md— both verdict tables flip to ✅; webview finding 2 gets the "✅ Resolved 2026-07-06" paragraphTASKS.md— idle-memory item ◐ → ☑ROADMAP.md— 0.5 performance pass ◐ → ☑ + dated changelog entry; every PRD §8 target now passes on its measured platformTest plan
Doc-only change (markdown in PRD/ROADMAP/TASKS/docs) — no code paths touched, so no typecheck/build/test applies. Verified the four files render sanely and the measured figures quoted match the 2026-06-29 baseline section they cite.
🤖 Generated with Claude Code