tx-generator: Implement governance action / voting workload #5999
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.
Description
This PR tracks the development of the new governance action / voting workload for the
tx-generator
.The governance action used for benchmarking was chosen to be Treasury Withdrawals. They don't have dependencies on prior governance actions, and are not mutually blocking. Furthermore, they only require DRep votes to be ratified.
The workload is designed to keep a constant number of proposals "active" (= being voted on), thus keeping the stress on ledger pulsing constant. This means adjusting / throttling vote submissions such that when we know a quorum was reached for one proposal, subsequent votes will go to the next "empty" (= without any votes) proposal.
Issue List
govActionDeposit
)dRepVotingThresholds
et al., to maximize stress on the systemChecklist
See Runnings tests for more details
CHANGELOG.md
for affected package.cabal
files are updatedhlint
. See.github/workflows/check-hlint.yml
to get thehlint
versionstylish-haskell
. See.github/workflows/stylish-haskell.yml
to get thestylish-haskell
versionghc-8.10.7
andghc-9.2.7