fix(provider): yield 4GiB warms while 8GiB jobs wait - #411
Merged
Conversation
A 4 GiB warm cannot be claimed by linux-release or priority-integration. Refilling that class onto an empty 16 GiB member was the packing that kept Almaty 8 GiB JIT queued. ReconcileWarm treats the smaller-class target as zero until the larger wait clears; same-size warms of another pool yield too. This is v0.1.5-nddev.128.
Bind the warm-yield source commit and the twice-built linux-amd64 binary digest so the reproducible provider gate can ship the release.
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
1 participant
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.
Why
Almaty 8 GiB jobs (linux-release Android/Rust, priority-integration) waited while 4 GiB warms sat on empty 16 GiB members. Those warms cannot be claimed by the 8 GiB class. Draining them live placed four 8 GiB JITs immediately.
What
ReconcileWarm yields the smaller class (effective target 0) while a larger-memory job is queued or assigned, and while a same-size job of another pool is waiting. Same-class waiters of this pool still refill.
This is provider
v0.1.5-nddev.128. Does not shrink the 8 GiB envelope. Does not cancel queued jobs.Verify
make verify