do-not-merge: feat(llm): offload the PLE table, resize the cap, cap the pools #21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "hermes/ple-offload-day-v2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Turns the documented offload-day change into a deployable commit, still
gated on hardware: amd has NOT been rebooted since 2026-08-26 (journal
boots + kernel "Memory: 62962476K" on 2026-08-29) so the 2x64 GiB
Kingston sticks are not populated yet. Deploy only after the sticks are
in, trained at speed, and memtest passed, in a restart window the opencode
traffic can survive.
48-52 GiB pinned n-gram table out of VRAM (~24-26 GiB/board freed).
container's cgroup (measured 2026-08-27), so the cap must sit above
48-52 GiB pinned + ~6.3 GiB anon; 16 GiB swap allowance kept.
commit: without hard caps the KV pool instantly re-eats the freed
VRAM. Measured safe set ~3.6 GiB/board, above observed peaks (131k
tokens, 16 mamba slots).
Verified: nix eval on nixosConfigurations.amd renders exactly these
flags. Deploy verification (per card t_044d1243): engine up, decode
~88 tok/s @18k, free VRAM per board clearly above the 3.7/4.4 GiB
baseline, qwen-tts containers untouched. Activating the restart also
switches on the already-committed --sleep-on-idle.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.