From 96062b627e6aa24bcdbfae058701f838341c99b9 Mon Sep 17 00:00:00 2001 From: Frank Date: Wed, 16 Sep 2026 19:33:36 -0700 Subject: [PATCH] x4 note: post-reboot headroom (12.3 GiB, 240 blocks vs 475) is part of the record MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The ledger number in the note was pre-reboot. Same model, same pool, no clamp — but the host was measurably more fragmented when it came back, which is the sort of thing that decides whether the next co-tenant fits. --- serverAppConfigs-docs/LLM/x4-pair-experiment.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/serverAppConfigs-docs/LLM/x4-pair-experiment.md b/serverAppConfigs-docs/LLM/x4-pair-experiment.md index 2b40797..beeb553 100644 --- a/serverAppConfigs-docs/LLM/x4-pair-experiment.md +++ b/serverAppConfigs-docs/LLM/x4-pair-experiment.md @@ -299,6 +299,9 @@ Operational notes for the next run: of a restart trigger, or move the symlink aside. - Restarting frank-large needs the quadlet source back in `~/.config/containers/systemd/` plus `daemon-reload`; the generator re-creates - the unit from that file only. After the restore (and a host reboot, see the + the unit from that file only. After the restore (and the host reboot, see the landmines) the ledger read `400384 positions, ~27.2 GiB` against a 33.5 GiB - budget — no clamp — with 15.2 GiB left, and both endpoints answered `/health`. + budget — no clamp — with 12.3 GiB left for everything else (14.7 GiB before + the reboot: the same model, a more fragmented host afterwards — the engine + reported 240 free contiguous 2 MiB blocks against 475 earlier). Both endpoints + answered `/health` and served `/v1/models` under their names.