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

Run CI on merge queue things #1658

Merged
merged 2 commits into from
Sep 27, 2024
Merged

Run CI on merge queue things #1658

merged 2 commits into from
Sep 27, 2024

Conversation

noonio
Copy link
Contributor

@noonio noonio commented Sep 27, 2024

Should unblock our merge queues.


  • 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 Sep 27, 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-27 12:12:38.692495483 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.81 2.30 0.44
2 5301 7.13 2.82 0.46
3 5498 8.37 3.30 0.48
5 5901 11.22 4.43 0.53
10 6906 18.11 7.16 0.65
57 16353 83.13 32.89 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 756 13.86 5.65 0.34
3 944 17.33 7.20 0.38
5 1318 24.65 10.44 0.48
10 2250 45.22 19.36 0.75
20 4124 95.99 40.76 1.40

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 560 22.14 8.66 0.42
2 114 671 32.95 13.05 0.54
3 170 782 45.11 18.07 0.68
4 226 893 62.69 25.21 0.88
5 283 1004 76.92 31.23 1.04
6 339 1116 96.81 39.45 1.27

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 655 17.66 7.78 0.38
2 791 18.54 8.78 0.40
3 974 20.18 10.15 0.43
5 1181 23.32 12.91 0.48
10 2053 32.91 20.18 0.65
50 7947 97.97 74.68 1.83

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 641 20.07 9.01 0.41
2 785 21.50 10.39 0.43
3 982 23.37 12.15 0.47
5 1246 26.30 14.95 0.53
10 2073 34.86 23.06 0.69
50 7790 97.27 82.32 1.87

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 684 25.90 11.14 0.47
2 768 27.31 12.33 0.49
3 1082 30.21 14.84 0.55
5 1281 33.24 17.47 0.60
10 2091 43.29 26.04 0.78
39 6402 98.14 73.15 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 4977 17.47 7.60 0.57
2 5169 29.45 12.99 0.71
3 5270 42.54 18.82 0.86
4 5404 58.21 25.81 1.04
5 5525 72.51 32.16 1.21
6 5569 90.63 40.20 1.42

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.70 3.25 0.45
5 1 57 4968 9.02 4.05 0.47
5 5 285 5104 13.55 6.89 0.53
5 10 570 5275 18.81 10.28 0.61
5 20 1138 5613 30.52 17.57 0.77
5 30 1707 5953 41.84 24.69 0.93
5 40 2277 6293 52.58 31.56 1.08
5 50 2849 6635 64.31 38.86 1.24
5 81 4607 7681 99.87 61.16 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-27 12:15:14.463683909 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.889662219
P99 10.133993629999996ms
P95 6.691475799999996ms
P50 4.672841ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 23.549570207
P99 116.59240349000002ms
P95 30.168725199999997ms
P50 21.093454ms
Number of Invalid txs 0

Copy link

github-actions bot commented Sep 27, 2024

Test Results

503 tests  ±0   497 ✅ ±0   22m 26s ⏱️ -3s
160 suites ±0     6 💤 ±0 
  7 files   ±0     0 ❌ ±0 

Results for commit 5e318a7. ± Comparison against base commit 47410de.

♻️ This comment has been updated with latest results.

@locallycompact locallycompact added this pull request to the merge queue Sep 27, 2024
@noonio noonio removed this pull request from the merge queue due to the queue being cleared Sep 27, 2024
@ch1bo ch1bo added this pull request to the merge queue Sep 27, 2024
Merged via the queue into master with commit be2157f Sep 27, 2024
28 checks passed
@ch1bo ch1bo deleted the merge-queue-workflow-additions branch September 27, 2024 12:34
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.

3 participants