project finn console ram ceiling 88gb 20260715T102407

Justin asked about bumping Console's RAM allocation from 80GB to 95GB. Investigation (2026-07-15) found Finn is already at ~97G used of 126G total with 6G in swap, while also running the Home Assistant VM (4G) and 11 LXCs (Plex, media-server, ERPNext, Frigate, Immich, n8n, forge-data Postgres, AdGuard, forge-metrics, mail, openwebui).

Why: A 95G Console under a build/compile storm would push Finn's committed memory to ~120G+ of 126G, risking swap/OOM for Frigate/Plex/Immich. Modeling yesterday's peak load against an 88G ceiling kept it at ~83% (below the reaper's band-3 85% OOM-danger threshold); 95G would not.

How to apply: If Justin revisits Console's RAM allocation, treat 88GB as the defensible max on the current Finn (126GB total), not 95GB, unless Finn's own RAM is upgraded first (see [[project_reference_finn_ram_128gb_upgrade]]). Also note: Console's actual problem is burst RAM from next dev servers during dev-slot activity, not steady-state usage (was only 22G/78G used at check time) — the dev-slot reaper's --server-only teardown (kills the node process, keeps DB/worktree) is the real fix, not a bigger VM.

[auto-memory session 60d132de-4659-485c-8044-427af0ccce7f, confidence 0.70, mode staged]