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

Example of the simple dropout example on-top of the raft branch #1786

Draft
wants to merge 1 commit into
base: raft-network
Choose a base branch
from

Conversation

noonio
Copy link
Contributor

@noonio noonio commented Jan 15, 2025

This shows that the node-dropout example of #1780 works on top of the raft fork.

More evidence for building in full raft support!

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-15 09:52:53.628063411 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 2ee477c60839936be49a50030690865b5bed4db8cd2f05bf255ac680 10068
μHead a1610f6e64843161f4a88229c0286176f5325de3e2f773eec2b1d818* 4508
νDeposit c2117fd9ebdee3e96b81fd67ff7092d638926415c10f1f7e5a267ad0 2791
  • 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 5100 5.98 2.37 0.44
2 5301 7.17 2.84 0.46
3 5500 8.37 3.30 0.48
5 5902 11.22 4.43 0.53
10 6907 18.30 7.24 0.65
57 16356 82.85 32.77 1.78

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 566 10.52 4.15 0.29
2 758 13.86 5.65 0.34
3 946 17.33 7.20 0.38
5 1318 24.65 10.44 0.48
10 2251 45.22 19.36 0.75
20 4131 95.99 40.76 1.40

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 560 21.49 8.43 0.41
2 114 671 33.89 13.40 0.55
3 171 782 44.21 17.74 0.67
4 226 893 61.40 24.72 0.86
5 283 1009 79.55 32.20 1.07
6 339 1116 91.14 37.32 1.20

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 639 17.70 7.79 0.38
2 776 19.34 9.16 0.41
3 908 20.48 10.34 0.43
5 1261 23.40 12.86 0.49
10 2097 33.44 20.37 0.66
49 7706 95.80 73.12 1.79

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 661 20.07 9.02 0.41
2 791 21.53 10.42 0.43
3 918 22.96 11.79 0.46
5 1355 27.01 15.60 0.54
10 2050 34.89 23.00 0.69
50 8268 98.76 84.39 1.92

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 708 25.93 11.17 0.47
2 807 27.69 12.65 0.50
3 1066 30.21 14.83 0.55
5 1253 33.33 17.48 0.60
10 1982 42.54 25.44 0.76
40 6404 98.12 73.30 1.75

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 4996 17.32 7.54 0.56
2 5104 28.50 12.49 0.70
3 5212 41.20 18.17 0.84
4 5389 57.98 25.72 1.04
5 5621 78.64 35.08 1.29
6 5711 97.04 43.27 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 4934 7.89 3.34 0.46
5 1 57 4969 8.83 3.96 0.47
5 5 284 5103 13.74 6.98 0.54
5 10 570 5274 19.29 10.49 0.61
5 20 1138 5612 30.13 17.40 0.77
5 30 1709 5955 41.85 24.69 0.93
5 40 2277 6293 53.17 31.82 1.09
5 50 2843 6629 64.31 38.86 1.24
5 81 4604 7677 99.47 60.99 1.73

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-15 10:00:59.344894321 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 40.172927751
P99 45.62109026999997ms
P95 42.938337499999996ms
P50 39.828683999999996ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 104.015751677
P99 126.48821564000002ms
P95 117.36434064999999ms
P50 103.61748ms
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