Repository navigation
feat(load): run local capacity ladders past the load VM's limits - #5116
Merged
Merged
Conversation
The ramp and the fan-out passed every level up to 16 on the load VM, so they only gave lower bounds. Locally the ramp now goes to 64 and the fan-out to 128 recipients, on a 128-member organization. Shared DEV keeps its ladders within the agreed budgets.
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.
Part of #5107. On the load VM the ramp and the fan-out passed every level up to 16, so
capacityonly gave lower bounds. Locally the ramp now goes to 64 and the fan-out to 128 recipients (on a 128-member organization); mixed already found its bracket. Shared DEV keeps 1–16, within its agreed budgets (the ramp'sMAX_VUS=96covers level 16 only).Checked with
make node-checks(650/650).