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

win gar dium levi ohhh sa #1588

Closed
wants to merge 2 commits into from
Closed

win gar dium levi ohhh sa #1588

wants to merge 2 commits into from

Conversation

ffakenz
Copy link
Contributor

@ffakenz ffakenz commented Aug 29, 2024


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

Copy link

github-actions bot commented Aug 29, 2024

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 2024-09-01 16:57:31.272683233 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial 2fac819a1f4f14e29639d1414220d2a18b6abd6b8e444d88d0dda8ff 3799
νCommit 2043a9f1a685bcf491413a5f139ee42e335157c8c6bc8d9e4018669d 1743
νHead bd9fad235c871fb7f837c767593018a84be3083ff80f9dab5f1c55f9 10194
μHead c8038945816586c4d38926ee63bba67821eb863794220ebbd0bf79ee* 4607
  • 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 5186 5.75 2.27 0.44
2 5390 7.09 2.80 0.46
3 5588 8.37 3.30 0.49
5 5998 11.22 4.43 0.54
10 6998 18.20 7.20 0.66
56 16244 81.52 32.24 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 749 13.86 5.65 0.34
3 933 17.33 7.20 0.38
5 1313 24.65 10.44 0.48
10 2242 45.22 19.36 0.75
20 4119 95.99 40.76 1.40

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 549 21.46 8.41 0.41
2 114 659 32.95 13.05 0.54
3 170 769 47.53 18.98 0.70
4 227 879 60.25 24.30 0.85
5 281 989 76.72 31.15 1.04
6 340 1100 91.97 37.66 1.21

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 638 17.71 7.80 0.38
2 786 19.11 9.08 0.40
3 891 20.76 10.44 0.43
5 1370 27.35 14.40 0.54
10 1909 32.24 20.01 0.64
47 7695 94.69 71.15 1.77

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 645 21.02 9.41 0.42
2 847 22.86 11.16 0.45
3 969 24.18 12.48 0.48
5 1215 27.31 15.36 0.54
10 2078 36.22 23.70 0.71
50 7784 97.58 82.31 1.87

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 666 27.18 11.67 0.48
2 819 28.94 13.19 0.52
3 941 30.75 14.71 0.55
5 1278 34.87 18.30 0.62
10 1988 43.98 25.99 0.78
40 6345 99.71 73.75 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 5052 17.32 7.53 0.57
2 5145 25.06 10.84 0.66
3 5341 42.48 18.80 0.86
4 5406 56.62 25.04 1.03
5 5604 72.14 32.02 1.21
6 5729 97.28 43.34 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 5022 7.84 3.32 0.46
5 1 57 5057 9.08 4.08 0.48
5 5 285 5192 13.21 6.75 0.53
5 10 569 5362 19.35 10.51 0.62
5 20 1139 5701 30.58 17.60 0.78
5 30 1709 6044 41.90 24.72 0.93
5 40 2276 6380 53.03 31.76 1.09
5 50 2845 6719 64.37 38.89 1.25
5 81 4610 7771 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-09-01 17:00:43.363824283 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 1.696075627
P99 2.329614239999999ms
P95 2.0156206ms
P50 1.6270775ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 39.949834839
P99 211.11770883000003ms
P95 118.09518139999999ms
P50 18.088697ms
Number of Invalid txs 0

@ffakenz ffakenz force-pushed the network-test-2 branch 2 times, most recently from 4cc812e to cfbc99a Compare September 1, 2024 16:29
@noonio noonio linked an issue Sep 2, 2024 that may be closed by this pull request
@ffakenz ffakenz closed this Sep 2, 2024
@ffakenz ffakenz deleted the network-test-2 branch September 2, 2024 08:37
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.

Don't persist the network messages and their acknowledgements
1 participant