Repository navigation
client: set totalcompute from usable cores - #18
Merged
Merged
Conversation
valerian-roche
approved these changes
Oct 16, 2026
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.
Alternative to #17
Linux arm64 w/ 18 cores, 9 reservable
After
cpu=1000 job:
cores=2 job added:
Saturate with cores=1 jobs:
So with 1 cores=8 job the utilization looks right:
And then trying to schedule a cpu=4000 job the rejection looks right:
Reversing the submission order works as expected.
cpu=4000 job results in:
cores=8 job results in:
With cpu_total_compute=20000
After a cores=8 job:
After a cpu=4000 job is added:
With cpu_total_compute=50000
Trying to run multiple jobs with cores=8:
But cpu=4000 jobs still fit: