Skip to content
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

Remove unneeded allow-newers #1790

Closed
wants to merge 1 commit into from
Closed

Conversation

locallycompact
Copy link
Contributor

No description provided.

Copy link

Transaction cost differences

Script summary

Name Size (Bytes)
νInitial -
νCommit -
νHead -
μHead -
νDeposit -

Init transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 - - - -
2 - - - -
3 - - - -
5 - - - -
10 - - - -
44 - - - -

Commit transaction costs

UTxO Tx size % max Mem % max CPU Min fee ₳
1 - - - -
2 - - - -
3 - - - -
5 - - - -
10 - - - -
54 - - - -

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 - - - - -
2 - - - - -
3 - - - - -
4 - - - - -
5 - - - - -
6 - - - - -
7 - - - - -
8 - - - - -
9 - - - - -
10 - - - - -

Cost of Increment Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 - +0.39 +0.09 -
2 - +0.39 +0.09 +0.01
3 - - - -
5 - +0.39 +0.09 -
10 - - - -
43 - $${\color{green}-0.39}$$ $${\color{green}-0.09}$$ $${\color{green}-0.01}$$

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 - - - -
2 - - - -
3 - - - -
5 - - - -
10 - - - -
45 - - - -

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 - - - -
2 - - - -
3 - - - -
5 - - - -
10 - - - -
41 - - - -

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 - - - -
2 - - - -
3 - - - -
5 - - - -
10 - - - -
33 - - - -

FanOut transaction costs

UTxO, Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
(0, 10) - - - - -
(1, 10) - - - - -
(5, 10) - - - - -
(10, 10) - - - - -
(20, 10) - - - - -
(40, 10) - - - - -
(41, 10) - - - - -

Copy link

Transaction costs

Sizes and execution budgets for Hydra protocol transactions. Note that unlisted parameters are currently using arbitrary values and results are not fully deterministic and comparable to previous runs.

Metadata
Generated at 2025-01-17 10:47:35.502344339 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial c8a101a5c8ac4816b0dceb59ce31fc2258e387de828f02961d2f2045 2652
νCommit 61458bc2f297fff3cc5df6ac7ab57cefd87763b0b7bd722146a1035c 685
νHead 5350e9d521552ebfd9e846fd70c3b801f716fc14296134ec0fb71e97 14492
μHead 6b49dc4e571207d615dba01996548cb610b0caa85c30423d169d0091* 5612
νDeposit ae01dade3a9c346d5c93ae3ce339412b90a0b8f83f94ec6baa24e30c 1102
  • The minting policy hash is only usable for comparison. As the script is parameterized, the actual script is unique per head.

Init transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 6165 10.31 3.29 0.53
2 6366 12.38 3.94 0.56
3 6566 14.40 4.58 0.59
5 6969 18.36 5.81 0.65
10 7976 28.59 9.03 0.80
44 14811 98.04 30.85 1.82

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 561 2.44 1.16 0.20
2 740 3.38 1.73 0.22
3 923 4.36 2.33 0.24
5 1276 6.41 3.60 0.28
10 2174 12.13 7.25 0.40
54 10074 98.61 68.52 1.88

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 525 24.20 7.07 0.42
2 114 636 32.98 9.56 0.51
3 171 747 43.22 12.39 0.62
4 226 858 47.77 13.91 0.67
5 282 969 55.81 16.27 0.76
6 338 1081 62.80 18.24 0.84
7 395 1192 83.66 23.66 1.05
8 449 1303 84.43 24.39 1.07
9 504 1414 93.17 26.90 1.16

Cost of Increment Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 1747 22.74 7.55 0.47
2 1976 26.49 9.51 0.52
3 2120 28.04 10.67 0.55
5 2322 29.55 12.45 0.58
10 3215 40.89 19.65 0.76
41 7832 96.48 58.74 1.70

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 590 22.68 7.31 0.41
2 746 23.35 8.15 0.43
3 851 25.42 9.42 0.46
5 1225 29.90 12.00 0.53
10 2021 41.00 18.44 0.70
43 6877 99.28 56.80 1.66

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 670 28.60 9.16 0.48
2 804 30.31 10.36 0.51
3 932 32.10 11.58 0.53
5 1285 34.05 13.72 0.58
10 1988 42.80 19.90 0.73
40 6375 96.43 57.66 1.63

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 667 33.35 10.42 0.52
2 764 34.77 11.41 0.55
3 974 37.17 12.94 0.59
5 1257 41.65 15.74 0.66
10 2134 53.50 23.09 0.84
30 5130 96.75 50.54 1.52

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 6051 26.21 8.86 0.69
2 6116 31.42 10.59 0.75
3 6303 43.24 14.61 0.88
4 6363 48.70 16.43 0.94
5 6568 59.72 20.24 1.07
6 6731 67.26 22.80 1.15
7 6833 80.51 27.21 1.30
8 6988 89.78 30.43 1.40
9 7077 95.13 32.22 1.46

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 5 284 6331 28.18 10.22 0.73
10 20 1137 6839 56.83 21.77 1.07
10 30 1710 7184 76.42 29.65 1.30
10 40 2275 7519 95.65 37.39 1.52
10 42 2390 7588 99.94 39.10 1.57

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 2025-01-17 10:50:50.654995493 UTC

Baseline Scenario

Number of nodes 1
Number of txs 300
Avg. Confirmation Time (ms) 4.561041133
P99 10.336814309999994ms
P95 5.955468350000002ms
P50 4.3591345ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 900
Avg. Confirmation Time (ms) 24.894553840
P99 118.23347863ms
P95 35.73720159999999ms
P50 21.747034ms
Number of Invalid txs 0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant