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

Provide additional consequence related to obtaining HeadId #1170

Closed
wants to merge 2 commits into from

Conversation

v0d1ch
Copy link
Contributor

@v0d1ch v0d1ch commented Nov 20, 2023


  • CHANGELOG updated or not needed
  • Documentation updated or not needed
  • Haddocks updated or not needed
  • No new TODOs introduced or explained herafter

@v0d1ch v0d1ch self-assigned this Nov 20, 2023
Copy link

Transactions 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 2023-11-20 13:58:18.690118045 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial 57dd0a3aba3f4477afed74e7d12b6e86d7abad22ee51612ff81b4194 4059
νCommit 171a1e6bdbc8aa96d957a65b3f505517386af06ba265e3f784741f67 2050
νHead e89b0c4a6155bac2434d1e500bd49c155b2b56744ccf5a0efa72a82e 9092
μHead 92368af5649999c05211407d9a837cdd10ecf98c5829b385e89a3648* 4062
  • The minting policy hash is only usable for comparison. As the script is parameterized, the actual script is unique per Head.

Cost of Init Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 4594 11.01 4.37 0.47
2 4799 13.39 5.29 0.51
3 5008 15.42 6.05 0.54
5 5414 19.72 7.69 0.60
10 6439 30.71 11.88 0.77
41 12796 99.67 38.21 1.79

Cost of Commit Transaction

This is using ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 537 12.23 4.81 0.31
2 726 15.93 6.48 0.36
3 914 19.77 8.20 0.41
5 1284 27.87 11.80 0.52
10 2220 50.58 21.69 0.81
18 3722 94.20 40.16 1.36

Cost of CollectCom Transaction

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 56 483 22.20 8.87 0.41
2 114 593 34.81 14.01 0.56
3 170 703 48.36 19.64 0.71
4 226 813 64.63 26.36 0.90
5 282 923 82.57 33.82 1.10

Cost of Close Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 551 17.76 8.35 0.38
2 745 19.48 9.97 0.41
3 803 20.28 10.86 0.43
5 1282 24.73 14.85 0.51
10 1918 31.09 21.15 0.64
50 8974 96.21 83.28 1.92

Cost of Contest Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 591 21.33 9.72 0.42
2 745 23.31 11.40 0.45
3 969 25.16 13.10 0.49
5 1231 28.70 16.21 0.55
10 2171 37.59 24.20 0.72
45 8021 98.84 79.26 1.87

Cost of Abort Transaction

Some variation because of random mixture of still initial and already committed outputs.

Parties Tx size % max Mem % max CPU Min fee ₳
1 4544 20.18 8.78 0.58
2 4709 33.94 14.95 0.74
3 4905 50.39 22.35 0.93
4 5073 69.39 30.89 1.16
5 5120 84.77 37.55 1.33

Cost of FanOut Transaction

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 4416 9.08 3.82 0.45
5 1 57 4452 10.51 4.67 0.46
5 5 284 4596 15.46 7.75 0.53
5 10 569 4775 22.18 11.81 0.62
5 20 1139 5136 34.69 19.56 0.80
5 30 1710 5498 47.90 27.60 0.98
5 40 2277 5855 60.89 35.55 1.16
5 50 2844 6212 73.88 43.51 1.33
5 69 3928 6898 98.67 58.67 1.67

End-To-End Benchmark Results

This page is intended to collect the latest end-to-end benchmarks results produced by Hydra's Continuous Integration system from the latest master code.

Please take those results with a grain of salt as they are currently produced from very limited cloud VMs and not controlled hardware. Instead of focusing on the absolute results, the emphasis should be on relative results, eg. how the timings for a scenario evolve as the code changes.

Generated at 2023-11-20 13:52:16.911791008 UTC

3-nodes Scenario

A rather typical setup, with 3 nodes forming a Hydra head.

Number of nodes 3
Number of txs 900
Avg. Confirmation Time (ms) 22.939895213
P99 115.65214025ms
P95 30.960022499999997ms
P50 20.099713ms
Number of Invalid txs 0

Baseline Scenario

This scenario represents a minimal case and as such is a good baseline against which to assess the overhead introduced by more complex setups. There is a single hydra-node d with a single client submitting single input and single output transactions with a constant UTxO set of 1.

Number of nodes 1
Number of txs 300
Avg. Confirmation Time (ms) 3.905823313
P99 4.842332389999994ms
P95 4.448449800000001ms
P50 3.8340305ms
Number of Invalid txs 0

Copy link

Test Results

368 tests  ±0   363 ✔️ ±0   21m 29s ⏱️ -49s
124 suites ±0       5 💤 ±0 
    5 files   ±0       0 ±0 

Results for commit a1192df. ± Comparison against base commit 4cc76a4.

@v0d1ch
Copy link
Contributor Author

v0d1ch commented Nov 21, 2023

We altered the decision here and the actuall PR will contain the updated ADR document

@v0d1ch v0d1ch closed this Nov 21, 2023
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.

None yet

2 participants