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.
What
The modification in this PR is to enhance the existing (very useful) functionality of being able to increase the amount locust users for a specific User Class.
Changes in this pr allows us to decrease the running locust users for individual user classes (rather than all user classes) deterministically.
The functionality remains the same for normal spawn/despawn events where user classes are not specified.
Currently in locust we can
[UserA, UserB, UserC]
and are running weight 1,1,1,{"UserA": 2, "UserB": 1, "UserC": 1}
,With the changes in this pr we can now do the following:
{"UserA": 1, "UserB": 1, "UserC": 1}
,new_dispatch( self, target_user_count=2, spawn_rate=1, user_classes[UserA] )
{"UserA": 0, "UserB": 1, "UserC": 1}