Add new missions that trigger surge pricing/limiter at high volume traffic #64
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
dmkozh
force-pushed
the
high_traffic_mission
branch
2 times, most recently
from
8b62a00 to
c83cc14
Compare
| @@ -45,6 +48,8 @@ let allMissions : Map<string, Mission> = | |||
| ("ComplexTopology", complexTopology) | |||
| ("LoadGeneration", loadGeneration) | |||
| ("LoadGenerationWithSpikes", loadGenerationWithSpikes) | |||
| ("LoadGenerationWithTxSetLimit", loadGenerationWithTxSetLimit) | |||
There was a problem hiding this comment.
Did you also want to add these new missions to the CI?
There was a problem hiding this comment.
Indeed, but that should be a seprate PR to a different repo, right?
There was a problem hiding this comment.
yeah, wanted to make sure you're aware that another change is needed elsewhere
There was a problem hiding this comment.
Sounds good, I'll keep this in mind while it's blocked by the core PR release.
There was a problem hiding this comment.
heads up, we can update the CI now
dmkozh
force-pushed
the
high_traffic_mission
branch
from
c83cc14 to
a238d26
Compare
jeffreysmooths
approved these changes
Aug 17, 2022
marta-lokhova
approved these changes
Aug 17, 2022
dmkozh
force-pushed
the
high_traffic_mission
branch
from
1ce41ec to
106badb
Compare
Core changes have been finally merged (stellar/stellar-core#3492), so this should be ready to be merged, PTAL |
These are introduced by Core PR stellar/stellar-core#3492
…traffic: - Regular load generation, but with limiting/surge pricing triggering - Protocol upgrade under load/limiting - this would be relevant for e.g. p20 upgrade to use generalized tx sets - Running the mixed image version network at 51% quorum and with load - this could have caught network forking of 19.3.0 release.
dmkozh
force-pushed
the
high_traffic_mission
branch
from
106badb to
229190d
Compare
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 is based on the capability to generate load and ignore low fee tx errors (stellar/stellar-core#3492)
I'm adding the following scenarios: