Update gatling #3
Open
Conversation
This file contains 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
ubergeek42
commented
Nov 8, 2022
| String PASSWORD="secret"; | ||
|
|
||
| // How many "actions" a team will take (actions are things like submitting, requesting clarification, viewing a scoreboard) | ||
| int NUM_TEAM_ACTIONS = 5; |
There was a problem hiding this comment.
Adjust this to make a team "user" last longer/do more things.
ubergeek42
commented
Nov 8, 2022
| int NUM_TEAM_ACTIONS = 5; | ||
|
|
||
| // Maximum amount of time the scenario can run | ||
| int MAX_MINUTES = 5; |
There was a problem hiding this comment.
Sets a cap for how long this will run (which also sets how long a spectator will keep refreshing for.
ubergeek42
commented
Nov 8, 2022
| // While we're polling the teampage, lets pretend to do some actions like a real team might | ||
| .repeat(NUM_TEAM_ACTIONS, "i").on( | ||
| exec( | ||
| randomSwitch().on( |
There was a problem hiding this comment.
These are the random actions that a team will do, and the probabilities of each one.
ubergeek42
commented
Nov 8, 2022
| ) | ||
| ) | ||
| // Sleep anywhere between 5s and 1 minute before doing another action | ||
| .pause(5,60) |
There was a problem hiding this comment.
How much time between each team "action". This is in seconds, so teams will take an action between 5 and 60s after their last action.
ubergeek42
commented
Nov 8, 2022
Comment on lines
+173
to
+187
| teamScenario.injectClosed( | ||
| incrementConcurrentUsers(10) // Batches of this many users | ||
| .times(10) // how many "levels" to test | ||
| .eachLevelLasting(60) // hold the number of users for this duration | ||
| .separatedByRampsLasting(60) // Take 60s between adding each user | ||
| .startingFrom(10) // Start with 10 users | ||
| ), | ||
| // spectatorScenario.injectOpen(atOnceUsers(10)) | ||
| spectatorScenario.injectClosed( | ||
| incrementConcurrentUsers(10) // Batches of this many spectators | ||
| .times(10) // how many "levels" to test | ||
| .eachLevelLasting(60) // hold the number of users for this duration | ||
| .separatedByRampsLasting(60) // Take 60s between adding each user | ||
| .startingFrom(10) // Start with 10 users | ||
| ) |
There was a problem hiding this comment.
This is the bit you'll want to adjust to tune how many concurrent users are hammering the system. Probably play with these things until it falls over.
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.
This replaces all the old scala stuff with shiny new java based dsl (it's still a bit weird, but less weird than scala).
See the rungatling script for the required zip you need to download/extract.
See seeding/seed.sh for what you need to do to set up the data to run gatling (basically create a bunch of
gatling0001/secretteam accounts, and a contest with a hello world problem that they're all a part of)I'll add some inline comments for things you might want to tune when adjusting the scaling.
The scenarios it runs through are:
/publicevery 30s forever (to simulate the autorefresh)/teamevery 30s (to simulate the autorefresh), then periodically does a random action (submits some code, views the problems page, views the team scoreboard, or submits a clarification request).At the bottom you can tune how many users are injected/how it ramps up/down.