Performance/Load Testing #317
Draft
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
catch-21
force-pushed
the
feat/performance-tests
branch
from
a112f39 to
ef3ecb8
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.
Description
We require performance and load testing on the Cardano Rosetta implementation. It would be good to take measurements using user scenarios. Once we define some acceptable benchmarks we are then able to detect any unacceptable differences in future.
Proposed Solution
Use a framework like https://github.com/alexfernandez/loadtest, or a tool like https://github.com/artilleryio/artillery.
Important Changes Introduced
Created some examples using Loadtest and Artillery. My preference is with Artillery. Non-preferred examples can be stripped out before merge.
Testing
Follow test/performance-test/readme.md