Run the big model on the workstation, with admission control and the 1.7B as the floor #94

Merged
kami merged 3 commits from task/485-run-the-big-model-on-the-workstation-wit into master 2026-08-02 17:03:26 +02:00
Showing only changes of commit 2e97b905b4 - Show all commits
+12
View File
@@ -58,6 +58,18 @@ jobs.
The caller must be able to ask "is this peer usable right now" without a turn
hanging on a timeout. A dead remote is a normal state, not an error state.
`internal/llm.Pair` is that check on the Maven side. A prober caches the answer,
so `Available()` is an atomic read and no turn pays for a health check.
llama-server does not stay up on the workstation. It cannot: a resident 7-14B
would hold 16GB against the owner's CPT runs. So a supervisor there owns its
lifecycle, keeps it loaded while the card is free, and unloads it on idle or
when another process needs the card (owner's call, 2026-08-02, Vikunja #488).
That supervisor is still not a scheduler, and the distinction is worth holding.
It arbitrates nothing between callers. It reports whether it can take work and
manages one process to back that answer. Maven never asks it to start anything
and never learns that it did.
## What stays on homesrv, permanently