-
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
Use our copy of cardano.json instead of external #1578
Conversation
- Then we are robust to their version changing! - We should still update our version at some point
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.
Thanks.
Please file a follow-up issue to discuss a broader API conformity switch.
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 | 5186 | 5.81 | 2.30 | 0.44 |
2 | 5391 | 7.18 | 2.84 | 0.47 |
3 | 5591 | 8.59 | 3.40 | 0.49 |
5 | 5993 | 11.17 | 4.41 | 0.54 |
10 | 6996 | 18.02 | 7.12 | 0.66 |
56 | 16246 | 81.63 | 32.29 | 1.76 |
Commit
transaction costs
This uses ada-only outputs for better comparability.
UTxO | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | 559 | 10.52 | 4.15 | 0.29 |
2 | 748 | 13.86 | 5.65 | 0.34 |
3 | 932 | 17.33 | 7.20 | 0.38 |
5 | 1311 | 24.65 | 10.44 | 0.48 |
10 | 2250 | 45.22 | 19.36 | 0.75 |
20 | 4120 | 95.99 | 40.76 | 1.40 |
CollectCom
transaction costs
Parties | UTxO (bytes) | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|---|
1 | 58 | 550 | 21.46 | 8.41 | 0.41 |
2 | 114 | 659 | 32.28 | 12.81 | 0.53 |
3 | 171 | 769 | 47.15 | 18.82 | 0.70 |
4 | 226 | 879 | 61.53 | 24.78 | 0.86 |
5 | 281 | 994 | 73.51 | 29.94 | 1.00 |
6 | 338 | 1100 | 95.32 | 38.91 | 1.25 |
Cost of Decrement Transaction
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | 631 | 17.96 | 7.89 | 0.38 |
2 | 806 | 20.18 | 9.46 | 0.42 |
3 | 887 | 20.01 | 10.08 | 0.42 |
5 | 1174 | 22.65 | 12.58 | 0.48 |
10 | 1911 | 32.21 | 19.99 | 0.64 |
50 | 7818 | 99.25 | 75.23 | 1.84 |
Close
transaction costs
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | 657 | 20.98 | 9.41 | 0.42 |
2 | 806 | 22.45 | 10.82 | 0.45 |
3 | 923 | 23.88 | 12.19 | 0.47 |
5 | 1337 | 28.03 | 16.02 | 0.55 |
10 | 2006 | 35.35 | 23.03 | 0.69 |
50 | 7949 | 99.19 | 83.76 | 1.91 |
Contest
transaction costs
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | 690 | 27.14 | 11.67 | 0.48 |
2 | 849 | 29.36 | 13.52 | 0.52 |
3 | 952 | 30.76 | 14.72 | 0.55 |
5 | 1209 | 34.36 | 17.83 | 0.61 |
10 | 2164 | 44.97 | 26.93 | 0.80 |
38 | 6455 | 99.58 | 73.41 | 1.77 |
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 | 5070 | 17.51 | 7.62 | 0.57 |
2 | 5189 | 28.43 | 12.46 | 0.70 |
3 | 5364 | 42.63 | 18.87 | 0.87 |
4 | 5375 | 52.60 | 23.13 | 0.98 |
5 | 5604 | 77.62 | 34.52 | 1.27 |
6 | 5769 | 96.49 | 43.04 | 1.49 |
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 | 5023 | 7.95 | 3.36 | 0.46 |
5 | 1 | 57 | 5057 | 9.08 | 4.08 | 0.48 |
5 | 5 | 284 | 5192 | 13.60 | 6.92 | 0.54 |
5 | 10 | 568 | 5360 | 19.06 | 10.39 | 0.62 |
5 | 20 | 1139 | 5701 | 30.38 | 17.51 | 0.77 |
5 | 30 | 1710 | 6044 | 41.70 | 24.63 | 0.93 |
5 | 40 | 2280 | 6384 | 53.23 | 31.84 | 1.09 |
5 | 50 | 2845 | 6720 | 64.56 | 38.97 | 1.25 |
5 | 81 | 4607 | 7768 | 99.53 | 61.01 | 1.74 |
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-08-19 13:37:16.363014575 UTC
Baseline Scenario
Number of nodes | 1 |
---|---|
Number of txs | 3000 |
Avg. Confirmation Time (ms) | 4.297863416 |
P99 | 8.888766629999985ms |
P95 | 5.473987399999999ms |
P50 | 4.031084ms |
Number of Invalid txs | 0 |
Three local nodes
Number of nodes | 3 |
---|---|
Number of txs | 9000 |
Avg. Confirmation Time (ms) | 23.062288925 |
P99 | 104.75616836000003ms |
P95 | 31.34722035ms |
P50 | 20.694529000000003ms |
Number of Invalid txs | 0 |
Don't refer to the [potientially-changing](CardanoSolutions/cardanonical@cf11243) cardano.json from "cardanonical"; just use the one in our repo for now.
Don't refer to the potientially-changing cardano.json from "cardanonical"; just use the one in our repo for now.
Todo: