feat(stress-test): custom transactions to tx generator, result summary #880
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
sdbondi
force-pushed
the
stress-test-enhancements
branch
from
180a532 to
984a3b4
Compare
sdbondi
force-pushed
the
stress-test-enhancements
branch
14 times, most recently
from
c9cb30f to
52e75f1
Compare
3 tasks
sdbondi
force-pushed
the
stress-test-enhancements
branch
from
52e75f1 to
a89b624
Compare
3 tasks
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jan 16, 2024
Description --- Move HS message receivers into worker, pass messages to the OnInboundMessage handler. This checks proposals for missing transactions and parks them if necessary. New transaction notifications are sent to the OnInboundMessage handler to check if any proposals can be unparked. Once unparked, they are added to the "next message buffer". The message buffer is polled (cancel safe) in the consensus worker tokio select loop. Motivation and Context --- Clean up after fix in #889 How Has This Been Tested? --- Running stress test from PR #880 What process can a PR reviewer use to test or verify this change? --- Consensus should still work as before Breaking Changes --- - [x] None - [ ] Requires data directory to be deleted - [ ] Other - Please specify
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jan 16, 2024
…ls (#894) Description --- Includes locks in evidence Checks locks when proposing to allow multiple input refs Motivation and Context --- Evidence for each shard within a TransactionAtom now includes the lock type. Updated the proposal db query to check each lock type and ensure that conflicts either don't occur or if they do they are all read locks. How Has This Been Tested? --- Ran a stress test from #880, previously after #885 was merged, funding the tariswap components would take a very long time (I've never actually run it to completion, but ran for 30 mins without completing). With this PR funding took roughly a minute on my test. Swap batches are also reaching finalization within an acceptable timeframe. What process can a PR reviewer use to test or verify this change? --- Submit multiple transactions which use a single substate as an input ref and check that they can be added to the same block. Breaking Changes --- - [ ] None - [x] Requires data directory to be deleted (Evidence struct changed) - [ ] Other - Please specify
sdbondi
force-pushed
the
stress-test-enhancements
branch
from
a89b624 to
9cd0130
Compare
* development: chore: rename substate/shard related identifiers (tari-project#903) chore: add prettier settings and format all code (tari-project#900)
* development: feat: remove serde-byte-array (tari-project#909) fix: ui (tari-project#907) fix: uncomment sync cucumber test (tari-project#905)
stringhandler
approved these changes
Jan 22, 2024
Merged
via the queue into
tari-project:development
with commit Jan 22, 2024
442fc83
11 checks passed
sdbondi
added a commit
to sdbondi/tari-dan
that referenced
this pull request
Jan 22, 2024
* development: fix: remove unused `hotstuff_rounds` consensus constant (tari-project#912) fix: remove excess tasks and buffers for messaging (tari-project#902) feat(stress-test): custom transactions to tx generator, result summary (tari-project#880) chore(deps): bump follow-redirects from 1.15.2 to 1.15.5 in /applications/tari_validator_node_web_ui (tari-project#904) chore(deps): bump h2 from 0.3.22 to 0.3.24 (tari-project#908) chore(deps-dev): bump vite from 4.4.12 to 4.5.2 in /applications/tari_dan_wallet_web_ui (tari-project#910)
sdbondi
added a commit
to sdbondi/tari-dan
that referenced
this pull request
Jan 22, 2024
* development: fix: remove unused `hotstuff_rounds` consensus constant (tari-project#912) fix: remove excess tasks and buffers for messaging (tari-project#902) feat(stress-test): custom transactions to tx generator, result summary (tari-project#880) chore(deps): bump follow-redirects from 1.15.2 to 1.15.5 in /applications/tari_validator_node_web_ui (tari-project#904) chore(deps): bump h2 from 0.3.22 to 0.3.24 (tari-project#908) chore(deps-dev): bump vite from 4.4.12 to 4.5.2 in /applications/tari_dan_wallet_web_ui (tari-project#910)
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.
Description
Allow a custom manifest to be used with transaction generator
Fetch results and summarize stress test results
Allow fee instructions to be generated from transaction manifests
Add test bench app for tariswaps
Fix bug in autofiller bug where input refs are "upgraded" to inputs
Motivation and Context
Support custom stress test transactions.
Manifests can now specify fee instructions by optionally declaring a
fee_main()functionAdds test runner app that sets up and submits thousands of swaps.
How Has This Been Tested?
Manually, tests updated as required
What process can a PR reviewer use to test or verify this change?
Use transaction generator with custom manifest
Breaking Changes