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

cardano-node: 9.0.0 -> 9.1.0 #1531

Merged
merged 1 commit into from
Jul 25, 2024
Merged

cardano-node: 9.0.0 -> 9.1.0 #1531

merged 1 commit into from
Jul 25, 2024

Conversation

locallycompact
Copy link
Contributor

@locallycompact locallycompact commented Jul 25, 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 Jul 25, 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-07-25 11:36:37.18113231 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 7ae23bc9f0833a5689b9fc812dd92fbe9dac881a632f14b28e8eb8db 10193
μHead 3ebfb5b268e0c94200e2c8a8eeebf704aabf303a769af602edb3603a* 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 5188 5.61 2.21 0.44
2 5390 7.13 2.82 0.47
3 5590 8.69 3.44 0.49
5 5993 11.53 4.57 0.54
10 6999 18.10 7.16 0.66
56 16250 81.53 32.25 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 748 13.86 5.65 0.34
3 937 17.33 7.20 0.38
5 1306 24.65 10.44 0.48
10 2239 45.22 19.36 0.75
20 4118 95.99 40.76 1.40

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 549 22.14 8.66 0.42
2 114 659 32.17 12.77 0.53
3 169 769 45.38 18.18 0.68
4 227 879 62.59 25.16 0.88
5 283 989 78.01 31.62 1.05
6 340 1100 95.06 38.81 1.25

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 618 17.93 7.87 0.38
2 782 19.36 9.17 0.41
3 888 20.76 10.44 0.43
5 1237 24.13 13.21 0.49
10 1995 32.64 20.17 0.65
48 8104 99.95 73.82 1.85

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 662 20.98 9.41 0.42
2 781 22.45 10.79 0.44
3 913 23.96 12.21 0.47
5 1277 27.66 15.68 0.54
10 2068 36.07 23.64 0.70
49 8097 99.01 83.45 1.91

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 627 26.76 11.34 0.48
2 763 28.56 12.86 0.51
3 947 30.60 14.65 0.54
5 1157 33.89 17.39 0.60
10 2172 45.45 27.27 0.81
39 6322 98.35 72.83 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 5051 17.36 7.55 0.57
2 5168 28.46 12.47 0.70
3 5391 42.91 19.00 0.87
4 5486 58.03 25.74 1.05
5 5472 72.61 32.14 1.21
6 5790 88.57 39.32 1.40

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 5023 7.75 3.28 0.46
5 1 57 5057 9.08 4.08 0.48
5 5 283 5190 13.21 6.75 0.53
5 10 568 5361 19.26 10.48 0.62
5 20 1139 5702 30.19 17.43 0.77
5 30 1706 6040 41.90 24.72 0.93
5 40 2275 6379 53.03 31.76 1.09
5 50 2843 6717 64.17 38.80 1.24
5 81 4614 7775 99.73 61.10 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-07-25 11:38:58.139614907 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.653840435
P99 9.085762629999989ms
P95 5.7687123499999995ms
P50 4.223520000000001ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 22.883403893
P99 67.24691736000011ms
P95 31.083259149999996ms
P50 20.570932ms
Number of Invalid txs 0

Copy link

github-actions bot commented Jul 25, 2024

Test Results

464 tests  ±0   457 ✅ +5   16m 20s ⏱️ -8s
148 suites ±0     7 💤  - 5 
  5 files   ±0     0 ❌ ±0 

Results for commit c0d7a56. ± Comparison against base commit 9076612.

♻️ This comment has been updated with latest results.

@locallycompact locallycompact requested a review from a team July 25, 2024 09:52
@locallycompact locallycompact enabled auto-merge (squash) July 25, 2024 09:52
hydra-cluster/test/Test/CardanoNodeSpec.hs Outdated Show resolved Hide resolved
@locallycompact locallycompact merged commit 713db26 into master Jul 25, 2024
21 checks passed
@locallycompact locallycompact deleted the lc/cardano-node-9.1.0 branch July 25, 2024 11:58
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.

2 participants