Nonlinear Workload - Calculate Number of Agents based on Total Ramp Rate and Max Users/Sec per Agent #320
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
Zakaria-Kofiro
force-pushed
the
zkofiro/update-nonlinear-configuration
branch
from
d58a15d
to
eeb8a8d
Compare
Zakaria-Kofiro
changed the title
kevin-mcgoldrick
approved these changes
May 16, 2024
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.
Nonlinear Workload - Automatically Calculate Number of Agents based on Total Ramp Rate and Max Users/Sec per Agent
This change improves the user experience of setting up nonlinear workload jobs. Currently, the user inputs the ramp rate per agent and the number of agents they want for the job, which requires the person to work backward to find the total ramp rate. This change allows the user to set the total TPS (user/sec ramp) for the entire job, along with a max user/sec ramp rate per agent and lets the controller automatically calculate the number of agents needed for the job. This follows the same pattern as we have for linear jobs, where the user inputs the total users for the job and max users per agent.
Please make sure these check boxes are checked before submitting
mvn clean test -P default** PR review process **