-
Notifications
You must be signed in to change notification settings - Fork 87
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
Re-use contestation period as a deposit deadline #1702
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 | 5098 | 5.61 | 2.21 | 0.44 |
2 | 5295 | 7.40 | 2.93 | 0.46 |
3 | 5498 | 8.37 | 3.30 | 0.48 |
5 | 5899 | 11.21 | 4.43 | 0.53 |
10 | 6906 | 18.21 | 7.20 | 0.65 |
57 | 16355 | 83.00 | 32.84 | 1.78 |
Commit
transaction costs
This uses ada-only outputs for better comparability.
UTxO | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | 569 | 10.84 | 4.26 | 0.29 |
2 | 756 | 14.31 | 5.80 | 0.34 |
3 | 947 | 17.92 | 7.39 | 0.39 |
5 | 1322 | 25.56 | 10.73 | 0.49 |
10 | 2254 | 47.11 | 19.97 | 0.77 |
19 | 3937 | 94.71 | 39.81 | 1.38 |
CollectCom
transaction costs
Parties | UTxO (bytes) | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|---|
1 | 57 | 560 | 19.84 | 7.58 | 0.39 |
2 | 113 | 671 | 27.93 | 10.64 | 0.48 |
3 | 171 | 782 | 37.63 | 14.30 | 0.59 |
4 | 226 | 893 | 44.25 | 16.83 | 0.67 |
5 | 283 | 1004 | 53.71 | 20.41 | 0.78 |
6 | 340 | 1120 | 59.94 | 22.80 | 0.85 |
7 | 394 | 1227 | 73.19 | 27.75 | 1.00 |
8 | 449 | 1338 | 73.49 | 27.98 | 1.00 |
9 | 506 | 1449 | 78.65 | 29.99 | 1.07 |
10 | 560 | 1560 | 90.74 | 34.51 | 1.20 |
Cost of Decrement Transaction
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | 658 | 18.68 | 8.18 | 0.39 |
2 | 787 | 19.80 | 9.40 | 0.41 |
3 | 923 | 21.45 | 10.81 | 0.44 |
5 | 1262 | 25.57 | 13.94 | 0.51 |
10 | 1992 | 32.92 | 20.61 | 0.65 |
48 | 7706 | 98.76 | 75.63 | 1.83 |
Close
transaction costs
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | 657 | 20.79 | 9.30 | 0.41 |
2 | 832 | 22.63 | 11.07 | 0.45 |
3 | 996 | 24.06 | 12.52 | 0.48 |
5 | 1253 | 27.05 | 15.43 | 0.54 |
10 | 1837 | 33.69 | 22.19 | 0.66 |
50 | 7858 | 98.15 | 85.16 | 1.90 |
Contest
transaction costs
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | 699 | 26.81 | 11.50 | 0.48 |
2 | 761 | 28.20 | 12.71 | 0.50 |
3 | 999 | 30.39 | 14.72 | 0.55 |
5 | 1237 | 33.70 | 17.64 | 0.60 |
10 | 1999 | 43.99 | 26.55 | 0.79 |
39 | 6377 | 98.66 | 74.86 | 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 | 4994 | 15.51 | 6.64 | 0.54 |
2 | 5053 | 21.25 | 9.06 | 0.61 |
3 | 5254 | 29.14 | 12.65 | 0.71 |
4 | 5473 | 36.30 | 15.86 | 0.80 |
5 | 5636 | 43.55 | 19.10 | 0.89 |
6 | 5398 | 39.58 | 16.67 | 0.83 |
7 | 5818 | 54.69 | 23.79 | 1.02 |
8 | 5837 | 60.66 | 26.29 | 1.09 |
9 | 5914 | 63.88 | 27.52 | 1.12 |
10 | 6033 | 70.80 | 30.54 | 1.21 |
11 | 6450 | 87.58 | 38.41 | 1.42 |
12 | 6478 | 92.56 | 40.42 | 1.47 |
13 | 6555 | 93.89 | 40.85 | 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 ₳ |
---|---|---|---|---|---|---|
10 | 0 | 0 | 5089 | 9.60 | 4.01 | 0.48 |
10 | 1 | 57 | 5123 | 10.76 | 4.73 | 0.50 |
10 | 5 | 284 | 5259 | 15.43 | 7.62 | 0.56 |
10 | 10 | 568 | 5427 | 21.67 | 11.41 | 0.65 |
10 | 20 | 1137 | 5767 | 33.13 | 18.54 | 0.81 |
10 | 30 | 1710 | 6112 | 45.13 | 25.91 | 0.97 |
10 | 40 | 2279 | 6450 | 56.93 | 33.20 | 1.13 |
10 | 50 | 2845 | 6786 | 68.44 | 40.36 | 1.29 |
10 | 76 | 4323 | 7667 | 98.97 | 59.26 | 1.71 |
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-10-14 10:55:04.440519324 UTC
Baseline Scenario
Number of nodes | 1 |
---|---|
Number of txs | 300 |
Avg. Confirmation Time (ms) | 4.652948246 |
P99 | 12.466295209999998ms |
P95 | 8.0743129ms |
P50 | 4.1299600000000005ms |
Number of Invalid txs | 0 |
Three local nodes
Number of nodes | 3 |
---|---|
Number of txs | 900 |
Avg. Confirmation Time (ms) | 25.063598587 |
P99 | 118.42610734ms |
P95 | 31.281826199999994ms |
P50 | 21.9528825ms |
Number of Invalid txs | 0 |
ad0b172
to
a959822
Compare
a959822
to
c14cc59
Compare
edf38e7
to
64b314b
Compare
Transaction cost differences Script summary
|
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | +0.18 | +0.08 | - | |
2 | +6 | - | ||
3 | +0.15 | +0.07 | +0.01 | |
5 | - | +0.05 | +0.02 | - |
10 | - | |||
57 | - |
Commit
transaction costs
UTxO | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | +3 | - | - | - |
2 | - | - | - | - |
3 | - | - | - | |
5 | +8 | - | - | - |
10 | +2 | - | - | - |
19 | - | - | - |
CollectCom
transaction costs
Parties | UTxO (bytes) | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|---|
1 | - | ||||
2 | - | - | +2.08 | +0.77 | +0.02 |
3 | +2 | - | |||
4 | - | +0.75 | +0.26 | +0.01 | |
5 | - | +6.79 | +2.5 | +0.07 | |
6 | - | - | |||
7 | - | - | +2.24 | +0.85 | +0.03 |
8 | - | ||||
9 | +2 | - | +5.03 | +1.84 | +0.05 |
Cost of Decrement Transaction
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | +12 | - | - | - |
2 | +93 | +2.53 | +1.01 | +0.03 |
3 | +61 | - | ||
5 | +27 | - | ||
10 | ||||
49 |
Close
transaction costs
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | +67 | +0.41 | +0.36 | +0.01 |
2 | +11 | - | ||
3 | ||||
5 | - | |||
10 | +117 | +1.39 | +1.05 | +0.03 |
49 | +0.08 |
Contest
transaction costs
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | - | |||
2 | +8 | - | +0.02 | - |
3 | ||||
5 | +98 | +0.52 | +0.42 | +0.01 |
10 | +96 | +0.21 | +0.31 | +0.01 |
39 | +30 | +1.34 | +0.63 | +0.01 |
Abort
transaction costs
Parties | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|
1 | +33.0 | - | +0.01 | - |
2 | +9.0 | |||
3 | ||||
4 | +85.0 | +0.59 | +0.35 | +0.02 |
5 | +4.0 | +0.33 | +0.13 | - |
6 | +67.0 | +1.2 | +0.6 | +0.02 |
7 | ||||
8 | +58.0 | +3.75 | +1.73 | +0.04 |
9 | ||||
10 | +147.0 | +4.96 | +2.41 | +0.07 |
11 | +82.0 | +1.47 | +0.7 | +0.02 |
12 | +1.33 | +0.44 | +0.01 | |
13 | +197.0 | +2.06 | +1.25 | +0.04 |
FanOut
transaction costs
Parties | UTxO | UTxO (bytes) | Tx size | % max Mem | % max CPU | Min fee ₳ |
---|---|---|---|---|---|---|
10 | - | - | +1 | +0.4 | +0.17 | +0.01 |
10 | - | - | - | - | ||
10 | - | - | ||||
10 | - | +0.39 | +0.17 | - | ||
10 | - | +2 | +2 | +0.79 | +0.34 | +0.01 |
10 | - | - | +1 | - | ||
10 | - | - | ||||
10 | - | |||||
10 | +1 | +56 | +32 | +1.37 | +0.81 | +0.02 |
64b314b
to
0bf6e69
Compare
0bf6e69
to
fed456a
Compare
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.
Looks good! I assume the reason the golden output changes is because of the API type changes?
yes, now we also provide the information about the deadline |
Depends on #1702 ### Why Improve documention related to committing to a Head (especially when it comes to incremental commits) --- <!-- Consider each and tick it off one way or the other --> * [x] CHANGELOG updated or not needed * [x] Documentation updated or not needed * [x] Haddocks updated or not needed * [x] No new TODOs introduced or explained herafter
Depends on #1700
Reuse contestation deadline as a deposit deadline. This is a follow-up from offchain incremental commits where we just used the current time as the deposit deadline. Now the contestation period is re-used as a deposit deadline and on top of that we provide information about it in the
CommitRecorded
server output.