Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tx-generator: Implement governance action / voting workload #5999

Draft
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

mgmeier
Copy link
Contributor

@mgmeier mgmeier commented Sep 27, 2024

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

  • Create new workbench profile specifying voting workload for local clusters
  • Load DRep SigningKeys from Genesis / testnet-data
  • Build, sign and validate proposal transactions
  • Build, sign and valiadate voting transactions
  • Switch the local cluster to Porotocol Version 10.0
  • Split genesis fund to pay for proposal submission and tx fees (possibly adjusting govActionDeposit)
  • Submit proposals during splitting phase
  • Submit votes during benchmarking phase
  • Make number of active proposals varying and adjust tx submission stream accordingly
  • Validate workload: analyzing chainDB, monitoring ongoing run with queries, creating test cases
  • Fine-tune workload: adjust dRepVotingThresholds et al., to maximize stress on the system
  • Scale local workbench profile to the cloud cluster

Checklist

  • Commit sequence broadly makes sense and commits have useful messages
  • New tests are added if needed and existing tests are updated. These may include:
    • golden tests
    • property tests
    • roundtrip tests
    • integration tests
      See Runnings tests for more details
  • Any changes are noted in the CHANGELOG.md for affected package
  • The version bounds in .cabal files are updated
  • CI passes. See note on CI. The following CI checks are required:
    • Code is linted with hlint. See .github/workflows/check-hlint.yml to get the hlint version
    • Code is formatted with stylish-haskell. See .github/workflows/stylish-haskell.yml to get the stylish-haskell version
    • Code builds on Linux, MacOS and Windows for ghc-8.10.7 and ghc-9.2.7
  • Self-reviewed the diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants