-
Notifications
You must be signed in to change notification settings - Fork 84
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
Update networking docs #1649
Update networking docs #1649
Conversation
Transaction costsSizes and execution budgets for Hydra protocol transactions. Note that unlisted parameters are currently using
Script summary
|
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | 5097 | 5.81 | 2.30 | 0.44 |
2 | 5297 | 6.99 | 2.76 | 0.46 |
3 | 5498 | 8.46 | 3.34 | 0.48 |
5 | 5899 | 11.12 | 4.39 | 0.53 |
10 | 6906 | 18.26 | 7.22 | 0.65 |
57 | 16353 | 83.22 | 32.93 | 1.78 |
Commit
transaction costs
This uses ada-only outputs for better comparability.
UTxO | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | 566 | 10.52 | 4.15 | 0.29 |
2 | 755 | 13.86 | 5.65 | 0.34 |
3 | 947 | 17.33 | 7.20 | 0.38 |
5 | 1323 | 24.65 | 10.44 | 0.48 |
10 | 2250 | 45.22 | 19.36 | 0.75 |
20 | 4133 | 95.99 | 40.76 | 1.40 |
CollectCom
transaction costs
Parties | UTxO (bytes) | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|---|
1 | 56 | 559 | 21.46 | 8.41 | 0.41 |
2 | 114 | 671 | 32.95 | 13.05 | 0.54 |
3 | 171 | 782 | 47.08 | 18.79 | 0.70 |
4 | 227 | 893 | 58.93 | 23.81 | 0.84 |
5 | 285 | 1004 | 72.51 | 29.59 | 0.99 |
6 | 339 | 1116 | 87.91 | 36.13 | 1.17 |
Cost of Decrement Transaction
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | 628 | 17.95 | 7.88 | 0.38 |
2 | 818 | 20.12 | 9.44 | 0.42 |
3 | 858 | 19.21 | 9.79 | 0.41 |
5 | 1290 | 26.10 | 13.93 | 0.52 |
10 | 2058 | 32.76 | 20.12 | 0.65 |
50 | 8107 | 99.88 | 75.47 | 1.86 |
Close
transaction costs
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | 665 | 20.11 | 9.04 | 0.41 |
2 | 833 | 21.88 | 10.72 | 0.44 |
3 | 872 | 22.50 | 11.44 | 0.45 |
5 | 1322 | 26.52 | 15.24 | 0.53 |
10 | 1996 | 34.14 | 22.45 | 0.68 |
50 | 8090 | 98.50 | 83.73 | 1.91 |
Contest
transaction costs
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | 691 | 25.89 | 11.14 | 0.47 |
2 | 825 | 27.69 | 12.66 | 0.50 |
3 | 1082 | 30.17 | 14.83 | 0.55 |
5 | 1374 | 34.01 | 18.13 | 0.62 |
10 | 2190 | 43.78 | 26.44 | 0.79 |
39 | 6394 | 97.65 | 72.61 | 1.74 |
Abort
transaction costs
There is some variation due to the random mixture of initial and already committed outputs.
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | 5010 | 17.43 | 7.59 | 0.57 |
2 | 5095 | 28.46 | 12.47 | 0.69 |
3 | 5205 | 41.61 | 18.34 | 0.85 |
4 | 5338 | 57.04 | 25.22 | 1.03 |
5 | 5418 | 69.44 | 30.67 | 1.17 |
6 | 5669 | 97.60 | 43.47 | 1.50 |
FanOut
transaction costs
Involves spending head output and burning head tokens. Uses ada-only UTxO for better comparability.
Parties | UTxO | UTxO (bytes) | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|---|---|
5 | 0 | 0 | 4934 | 7.89 | 3.34 | 0.46 |
5 | 1 | 57 | 4968 | 8.63 | 3.88 | 0.47 |
5 | 5 | 285 | 5104 | 13.15 | 6.73 | 0.53 |
5 | 10 | 569 | 5274 | 19.40 | 10.54 | 0.62 |
5 | 20 | 1136 | 5611 | 30.33 | 17.48 | 0.77 |
5 | 30 | 1707 | 5953 | 41.65 | 24.61 | 0.93 |
5 | 40 | 2274 | 6291 | 53.17 | 31.82 | 1.09 |
5 | 50 | 2846 | 6633 | 64.70 | 39.03 | 1.25 |
5 | 81 | 4609 | 7682 | 99.47 | 60.99 | 1.73 |
End-to-end benchmark results
This page is intended to collect the latest end-to-end benchmark results produced by Hydra's continuous integration (CI) system from the latest master
code.
Please note that these results are approximate as they are currently produced from limited cloud VMs and not controlled hardware. Rather than focusing on the absolute results, the emphasis should be on relative results, such as how the timings for a scenario evolve as the code changes.
Generated at 2024-09-23 10:09:37.465946503 UTC
Baseline Scenario
Number of nodes | 1 |
---|---|
Number of txs | 3000 |
Avg. Confirmation Time (ms) | 4.454889078 |
P99 | 11.371062219999951ms |
P95 | 4.674574849999998ms |
P50 | 3.693236ms |
Number of Invalid txs | 0 |
Three local nodes
Number of nodes | 3 |
---|---|
Number of txs | 9000 |
Avg. Confirmation Time (ms) | 22.713582824 |
P99 | 117.22957666000002ms |
P95 | 29.73267965ms |
P50 | 19.6350165ms |
Number of Invalid txs | 0 |
Notably adding expected properties of the Network layer.
These are not relevant for documenting our approach to networking.
Adds more introductory information on our
Network
component in the Architecture > Networking page.This also drops old/outdated information and investigations of the Cardano network stack (not really relevant anymore). Ideally we would be able to find these back if we'd want, but not sure how to ensure this?