Simulation framework #371
Open
Simulation framework #371
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
sekulicd
force-pushed
the
SimulationFramework
branch
from
4618b8c to
fa2449f
Compare
worth cherry-picking them in a dedicated PR, so we dont hold them for the simulation to be reviewed? |
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 introduces a simulation framework designed to test the server by simulating multiple clients performing various actions over several rounds. The framework reads simulation configurations from YAML files, validates them against a predefined schema, and executes the simulation accordingly.
This contains code for local and remote(AWS) simulation, check README.
Few issues were fixed while testing (af492a7, 28116d0) @louisinger take a look.
Also there is separate PR for handling panic recovery in go routines started before server startup.
Note that AWS setup doesnt work always for many users (100) as there is rate limit for creating many ECS tasks in parallel (for bigger setup AWS support needs to be contacted to increase rate limit).
This should be enhanced with Signet support.
Prev PR was closed cause it had logs of commits and resolving conflicts while rebasing was complicated.
@tiero @altafan @louisinger please review.