Add an adversarial stress tester for the query service #1277
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
The new nasty-client program runs a loop that generates a random workload for the sequencer query service. The workload is intended to be adversarial and do things that a realistic rollup client wouldn't do. The current workload specifically reproduces some behavior we've seen on Gibraltar, such as opening very old streams and keeping multiple streams open at once. It should be easy to extend the client with new actions if we want to test additional behaviors.
jbearer
requested review from
nomaxg,
philippecamacho,
ImJeremyHe and
sveitser
as code owners
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.
The new nasty-client program runs a loop that generates a random workload for the sequencer query service. The workload is intended to be adversarial and do things that a realistic rollup client wouldn't do. The current workload specifically reproduces some behavior we've seen on Gibraltar, such as opening very old streams and keeping multiple streams open at once.
It should be easy to extend the client with new actions if we want to test additional behaviors.