-
Notifications
You must be signed in to change notification settings - Fork 43
Metrics and load testing #121
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
Conversation
wlawt
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
crates/system-tests/METRICS.md
Outdated
|
|
||
| **Usage:** | ||
| ```bash | ||
| load-test setup --master-key <KEY> --output <FILE> [OPTIONS] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be ./target/release/load-test ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yep, good catch!
crates/system-tests/METRICS.md
Outdated
|
|
||
| **Usage:** | ||
| ```bash | ||
| load-test load --wallets <FILE> [OPTIONS] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same comment here
| Wallets: 100 | ||
| Target Rate: 100 tx/s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
qq: is it correct to assume that the target TPS is evenly distributed across the number of wallets?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exactly. Could make this configurable as well if needed

Load tests send transactions to TIPS at a configurable rate using multiple wallets in parallel, then poll the sequencer to verify each transaction was successfully included in a block. Results are displayed as throughput metrics (tx/s) and categorized outcomes (included, reverted, timed out, send errors).