[deployment] Add a loadbalancer to perform better load tests#1549
Merged
Conversation
mickmis
approved these changes
Jul 2, 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
3 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.
This PR add a load balancer to the local testing stack, fixing one issue described in interuss/dss#1559
A DSS may have different q/s depending on CockroachDB spread data. In the 3 node scenario described in interuss/dss#1559, there is usually one DSS faster that others ones, but in average, q/s are the same.
Tested with the 3 node scenario: across multiple restart, average q/s are the same, and with same number of clients, results are the sum of what has been measured in the issue (second graph).