search

cardano-scaling / hydra

Implementation of the Hydra Head protocol
https://hydra.family/head-protocol/
Apache License 2.0
274 stars 84 forks source link

Add note about docker loading #1579

Closed noonio closed 3 weeks ago

noonio commented 3 weeks ago

Small fix on #1576 ( which was merged by the dangers of auto-merge! )

github-actions[bot] commented 3 weeks ago

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-08-19 17:33:02.581854331 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
Parties Tx size % max Mem % max CPU Min fee ₳
1 5188 5.93 2.35 0.44
2 5387 7.18 2.84 0.47
3 5590 8.37 3.30 0.49
5 5991 11.12 4.39 0.54
10 6996 18.11 7.16 0.66
56 16246 81.63 32.29 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 747 13.86 5.65 0.34
3 931 17.33 7.20 0.38
5 1309 24.65 10.44 0.48
10 2238 45.22 19.36 0.75
20 4123 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 33.86 13.39 0.55
3 170 769 46.39 18.55 0.69
4 227 879 58.69 23.73 0.83
5 283 989 74.08 30.17 1.01
6 338 1100 95.65 39.04 1.25

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 645 17.96 7.89 0.38
2 722 17.80 8.51 0.39
3 977 20.65 10.32 0.43
5 1238 23.57 12.92 0.49
10 1964 32.09 19.87 0.64
49 8135 99.60 74.47 1.85

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 670 20.98 9.41 0.42
2 740 22.03 10.46 0.44
3 957 24.29 12.52 0.48
5 1247 27.24 15.35 0.54
10 1868 34.51 22.31 0.67
49 7917 99.45 83.46 1.90

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 685 27.12 11.67 0.48
2 805 28.94 13.18 0.51
3 936 30.75 14.71 0.55
5 1157 33.81 17.36 0.60
10 2133 44.73 26.81 0.80
38 6398 98.15 72.58 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 5080 17.47 7.60 0.57
2 5221 29.27 12.90 0.71
3 5333 42.60 18.85 0.86
4 5622 60.76 27.10 1.08
5 5647 77.02 34.31 1.27
6 5594 80.20 35.34 1.30

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.75 3.28 0.46
5 1 57 5056 8.69 3.91 0.47
5 5 285 5192 13.41 6.84 0.54
5 10 570 5363 19.06 10.39 0.62
5 20 1136 5698 30.38 17.51 0.77
5 30 1704 6038 41.70 24.63 0.93
5 40 2278 6383 53.23 31.84 1.09
5 50 2844 6719 64.17 38.80 1.24
5 81 4609 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-08-19 17:35:25.347209346 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.838604041
P99 9.090128469999982ms
P95 6.629893549999995ms
P50 4.600554499999999ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 23.304459580
P99 49.55076700000004ms
P95 31.762663449999994ms
P50 21.284076499999998ms
Number of Invalid txs 0