Repository navigation
0.25.1: VRAM-resident models chat under host RAM pressure - #35
Merged
Merged
Conversation
Goal runs refused every chat once available host RAM fell under 1.5 GiB, even when the exact calibrated model was still loaded at the calibrated context entirely in VRAM. That reserve covers starting the runtime; a loaded copy already holds its host memory, so the reading counted it twice. A copy entirely in VRAM now needs 512 MiB free. Cold loads, partly offloaded copies and unknown memory readings keep failing closed. The flat 1.5 GiB checks at the top of each generation and after strategy inference are gone: every chat already passes the per-chat admission, which sees the resident copy.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
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.
phonton-cli v0.25.1 — Local runs survive a busy laptop
0.25.0 recommends
qwen3.5:4bfor 4-6 GB GPUs, but on exactly that hardwarelocal goal runs often stopped halfway with
resource_pressure. 0.25.1 lets amodel that is already loaded in VRAM keep working when the rest of the
machine is busy.
A loaded model keeps working
phonton goal --localrefused every model call once available host RAM fellbelow 1.5 GiB, even when the exact calibrated model (same digest, same
context) was still loaded entirely in VRAM. That reserve covers starting the
runtime. A model that is already loaded holds its host memory, and the
available-RAM reading already excludes it, so the check counted that memory
twice. Running the project's checks between model calls, such as an offline
npm ciand jest, was enough to trip it with a browser and chat apps open.A call to a copy held entirely in VRAM now needs 512 MiB of free host RAM.
On Ollama 0.34.2 with an RTX 4050, loading
qwen3.5:4bat 16384 tokens tookabout 700 MiB of host RAM; a later 7,000-token call to the loaded copy loaded
nothing. Everything else still fails closed:
offloaded to the CPU);
and is admitted like a cold load;
Residency is still checked again immediately before each call; it is an
observation, not a reservation.
In the 0.25.0 Aider Polyglot run on a 16 GB RAM, 6 GB RTX 4050 laptop, this
check ended 18 of 51 Phonton runs, including 13 of 17 JavaScript runs, about
100 seconds in, after the jest checks.
Tests
018f0b0adds a repro: at that commit the run endsresource_pressurewherereview_readyis expected.5a04d53makes it pass.-D warningspass locally. The full workspace suite runs here in CI, because Bitdefender quarantined cargo.exe on the dev machine.