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.1.1 -> 9.2.0 #1651

Merged
merged 1 commit into from
Sep 25, 2024
Merged

cardano-node: 9.1.1 -> 9.2.0 #1651

merged 1 commit into from
Sep 25, 2024

Conversation

locallycompact
Copy link
Contributor

No description provided.

@locallycompact locallycompact force-pushed the lc/cardano-node-9.2 branch 2 times, most recently from be763e7 to 0d85a19 Compare September 23, 2024 12:42
Copy link

github-actions bot commented Sep 23, 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-24 19:35:26.43430561 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 5094 5.71 2.25 0.44
2 5302 7.18 2.84 0.46
3 5496 8.37 3.30 0.48
5 5903 11.21 4.43 0.53
10 6910 18.02 7.12 0.65
57 16356 82.95 32.81 1.78

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 569 10.52 4.15 0.29
2 759 13.86 5.65 0.34
3 944 17.33 7.20 0.38
5 1322 24.65 10.44 0.48
10 2256 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.46 8.41 0.41
2 114 675 32.20 12.78 0.53
3 171 782 45.14 18.08 0.68
4 227 893 58.82 23.78 0.84
5 283 1004 79.90 32.34 1.07
6 338 1116 96.25 39.23 1.26

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 637 17.91 7.86 0.38
2 825 20.36 9.53 0.42
3 933 20.66 10.41 0.43
5 1325 26.12 13.96 0.52
10 1966 33.23 20.39 0.65
49 7989 97.39 73.67 1.82

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 672 20.07 9.03 0.41
2 805 21.50 10.41 0.43
3 910 22.92 11.78 0.46
5 1282 26.68 15.27 0.53
10 2184 35.11 23.47 0.70
50 8020 97.91 83.23 1.89

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 672 25.90 11.13 0.47
2 803 27.73 12.66 0.50
3 1015 29.80 14.49 0.54
5 1205 32.83 17.11 0.59
10 2079 43.37 26.06 0.78
40 6627 99.81 74.88 1.79

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 4895 13.95 5.82 0.52
2 5045 27.55 12.00 0.68
3 5275 42.94 19.00 0.87
4 5304 52.92 23.27 0.98
5 5560 77.49 34.49 1.27

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 4935 7.50 3.17 0.45
5 1 57 4969 8.83 3.96 0.47
5 5 284 5103 13.55 6.89 0.53
5 10 568 5272 19.40 10.54 0.61
5 20 1139 5614 30.33 17.48 0.77
5 30 1708 5954 41.45 24.52 0.92
5 40 2278 6295 52.78 31.65 1.08
5 50 2849 6635 64.51 38.95 1.24
5 81 4609 7683 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 2024-09-24 19:37:49.484956306 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 3.794522346
P99 5.432935139999992ms
P95 4.4259134499999995ms
P50 3.716786ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 22.767936030
P99 116.32230202000001ms
P95 29.690823449999993ms
P50 19.6601755ms
Number of Invalid txs 0

Copy link

github-actions bot commented Sep 23, 2024

Test Results

503 tests  ±0   497 ✅ ±0   22m 4s ⏱️ + 1m 5s
160 suites ±0     6 💤 ±0 
  7 files   ±0     0 ❌ ±0 

Results for commit 951bedf. ± Comparison against base commit 2a36ef7.

♻️ This comment has been updated with latest results.

@locallycompact locallycompact enabled auto-merge (squash) September 25, 2024 09:18
@noonio noonio self-requested a review September 25, 2024 09:47
Copy link
Contributor

@noonio noonio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@locallycompact locallycompact merged commit 47410de into master Sep 25, 2024
28 checks passed
@locallycompact locallycompact deleted the lc/cardano-node-9.2 branch September 25, 2024 09:57
v0d1ch pushed a commit that referenced this pull request Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants