[loadtest] Add loadtest guidance for good results - #1616
Merged
Conversation
BenjaminPelletier
marked this pull request as ready for review
August 5, 2026 22:30
github-actions Bot
added a commit
to brandoncorrea/monitoring
that referenced
this pull request
Aug 12, 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
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.
Benchmarker (#1566) is an attempt to standardize performance measurements so they capture useful information and are repeatable. However, it is not yet to full MVP and users are likely to want to explore new ideas for measuring performance under load using locust even after benchmarker reaches MVP since loadtest's use of locust makes it a good interactive R&D tool. To support this kind of usage of loadtest, this PR proposes general usage guidance to avoid pitfalls of poor measurement quality due to overwhelming the system under test.