Add --dev-tx-interval-ms CLI option #2822
Closed
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
joske
approved these changes
Nov 8, 2023
vvp
force-pushed
the
feat/dev-tx-interval
branch
from
81d523a
to
7eb2b53
Compare
|
Closing this as obsolete after #3132 was already merged. |
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 PR adds a new CLI option for controlling transaction generation in development mode. For example
--dev-tx-interval-ms 1000makes a dev node execute and broadcast dummy transactions on a one-second interval. This setting works for other nodes besides--dev 0too and provides a simple way to increase load in a devnet for testing purposes.If the
--dev-tx-interval-msis not set, then node behaves similarly as before - only node--dev 0generates transactions every 500 msec.--dev-tx-interval-ms 0will disable the transaction generation (also with--dev 0).