Repository navigation
Check cluster memory budgets per node - #141
Merged
WestWaters merged 1 commit intoOct 6, 2026
Merged
Conversation
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
2 participants
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.
Add
--cluster-profileto budget weights, KV and runtime headroom on each node instead of treating total cluster RAM as one allocation.Count unified memory once and check the smallest worker. KV defaults to replication. Explicit fractions describe partitioned KV and unequal weight shards; equal sharding is labeled as an assumption.
22 tests pass, including byte conversion and concurrent sequences. The documentation uses anonymous example nodes and distinguishes arithmetic fit from a tested deployment or an OOM guarantee. No private hardware profile is included.
Usage and limits:
notes/cluster-profile.md.I used AI assistance and reviewed and tested the changes.