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

Check that the era changes in the hardfork tests #1546

Merged
merged 1 commit into from
Aug 2, 2024

Conversation

noonio
Copy link
Contributor

@noonio noonio commented Aug 2, 2024


  • CHANGELOG updated or not needed
  • Documentation updated or not needed
  • Haddocks updated or not needed
  • No new TODOs introduced or explained herafter

@noonio noonio force-pushed the ensure-eras-change-on-forking-tests branch from 9e0d5c4 to 17aaba6 Compare August 2, 2024 10:39
Copy link

github-actions bot commented Aug 2, 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-08-02 11:02:18.107625821 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
  • 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.81 2.30 0.44
2 5390 7.17 2.84 0.47
3 5591 8.56 3.39 0.49
5 5993 11.22 4.43 0.54
10 7000 18.11 7.16 0.66
56 16247 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 749 13.86 5.65 0.34
3 934 17.33 7.20 0.38
5 1309 24.65 10.44 0.48
10 2252 45.22 19.36 0.75
20 4119 95.99 40.76 1.40

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 549 21.49 8.43 0.41
2 114 659 33.03 13.08 0.54
3 170 769 47.22 18.85 0.70
4 227 879 59.97 24.20 0.85
5 282 989 79.94 32.36 1.07
6 339 1100 88.80 36.48 1.18

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 633 17.96 7.88 0.38
2 717 17.84 8.52 0.39
3 896 20.51 10.34 0.43
5 1229 23.57 12.92 0.49
10 2121 36.23 21.49 0.69
49 7696 95.03 72.82 1.78

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 638 20.94 9.38 0.42
2 779 22.41 10.78 0.44
3 983 24.30 12.54 0.48
5 1348 27.99 16.01 0.55
10 1937 34.97 22.69 0.68
49 7738 95.92 81.15 1.85

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 690 27.18 11.70 0.48
2 800 28.94 13.18 0.51
3 895 30.22 14.32 0.54
5 1286 34.60 18.05 0.62
10 2154 44.81 26.86 0.80
38 6165 97.00 71.34 1.72

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 4978 13.91 5.81 0.52
2 5180 28.35 12.43 0.70
3 5350 42.75 18.91 0.87
4 5425 54.06 23.84 1.00
5 5593 76.09 33.80 1.25
6 5607 85.12 37.65 1.36

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.56 3.20 0.46
5 1 57 5056 9.28 4.16 0.48
5 5 286 5194 13.60 6.92 0.54
5 10 568 5361 19.06 10.39 0.62
5 20 1138 5700 30.19 17.43 0.77
5 30 1706 6040 41.51 24.55 0.93
5 40 2281 6385 53.23 31.84 1.09
5 50 2851 6725 64.17 38.80 1.24
5 81 4609 7770 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-08-02 10:44:36.147874665 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.028677978
P99 6.135396869999999ms
P95 4.396565499999999ms
P50 3.6926734999999997ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 22.428037117
P99 115.46111383000003ms
P95 30.615300649999973ms
P50 19.66501ms
Number of Invalid txs 0

Copy link

github-actions bot commented Aug 2, 2024

Test Results

464 tests  ±0   457 ✅ ±0   17m 40s ⏱️ -51s
149 suites ±0     7 💤 ±0 
  5 files   ±0     0 ❌ ±0 

Results for commit 17aaba6. ± Comparison against base commit 6360171.

@locallycompact locallycompact merged commit 1754eff into master Aug 2, 2024
21 checks passed
@locallycompact locallycompact deleted the ensure-eras-change-on-forking-tests branch August 2, 2024 11:47
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