Repository navigation
feat(load): run the local fan-out up to 256 recipients - #5117
Merged
Merged
Conversation
Every batch up to 128 passed on the load VM, the largest one in 37 seconds of the 60-second deadline; 256 recipients should cross it. The organization fixture follows, at 256 members.
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 every fan-out batch up to 128 passed: adding and verifying 128 recipients took 37 s of the 60 s deadline (64: 17 s), so 256 should give the bracket. The local organization fixture follows, at 256 members (seeding 128 took 38 s). Shared DEV is unchanged.
Checked with
make node-checks(651/651).