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

Renamed close type redeemers #1538

Merged
merged 2 commits into from
Jul 30, 2024
Merged

Conversation

ffakenz
Copy link
Contributor

@ffakenz ffakenz commented Jul 29, 2024

To be defined from the script's point of view.

  • Current -> Unused
  • Outdated -> Used

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

@ffakenz ffakenz self-assigned this Jul 29, 2024
@ffakenz ffakenz force-pushed the ensemble/rename-close-redeemer-types branch from fa43c52 to c40b4de Compare July 29, 2024 16:49
Copy link

github-actions bot commented Jul 29, 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-30 13:46:23.952813865 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 5189 6.02 2.39 0.44
2 5389 7.36 2.91 0.47
3 5590 8.56 3.39 0.49
5 5993 11.31 4.47 0.54
10 6998 18.10 7.16 0.66
56 16247 81.43 32.21 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 745 13.86 5.65 0.34
3 934 17.33 7.20 0.38
5 1301 24.65 10.44 0.48
10 2245 45.22 19.36 0.75
20 4120 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 33.03 13.08 0.54
3 170 769 47.31 18.89 0.70
4 227 879 62.55 25.15 0.88
5 282 989 76.88 31.21 1.04
6 339 1100 94.82 38.70 1.24

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 619 17.71 7.79 0.38
2 789 19.07 9.06 0.40
3 973 21.66 10.79 0.45
5 1252 24.37 13.22 0.50
10 2016 32.37 19.98 0.64
47 7578 96.52 71.84 1.78

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 672 20.98 9.41 0.42
2 731 22.03 10.46 0.44
3 909 23.96 12.21 0.47
5 1339 27.92 15.98 0.55
10 1981 35.43 23.03 0.69
50 7887 98.66 83.22 1.89

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 627 26.76 11.34 0.48
2 754 28.56 12.86 0.51
3 937 30.64 14.66 0.54
5 1209 34.11 17.66 0.61
10 1953 43.82 25.89 0.78
38 6194 96.90 71.30 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 5064 17.32 7.54 0.57
2 5186 28.51 12.49 0.70
3 5319 41.38 18.25 0.85
4 5367 52.55 23.11 0.98
5 5671 78.37 34.95 1.28
6 5651 90.60 40.19 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 5022 7.95 3.36 0.46
5 1 57 5057 8.49 3.82 0.47
5 5 284 5191 13.41 6.84 0.54
5 10 570 5363 18.87 10.31 0.61
5 20 1140 5702 30.78 17.68 0.78
5 30 1708 6043 41.51 24.55 0.93
5 40 2272 6376 52.64 31.59 1.08
5 50 2845 6719 64.37 38.89 1.25
5 81 4607 7768 99.33 60.93 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-07-30 13:49:00.163577541 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.607556686
P99 9.354474699999999ms
P95 5.962976749999998ms
P50 4.1757195ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 23.750517485
P99 101.87309036000022ms
P95 32.597825449999995ms
P50 21.319710999999998ms
Number of Invalid txs 0

@ffakenz ffakenz force-pushed the ensemble/rename-close-redeemer-types branch from c40b4de to 37f1ced Compare July 30, 2024 07:37
Copy link

github-actions bot commented Jul 30, 2024

Test Results

464 tests  ±0   457 ✅ ±0   18m 10s ⏱️ + 1m 20s
149 suites ±0     7 💤 ±0 
  5 files   ±0     0 ❌ ±0 

Results for commit ab5194e. ± Comparison against base commit b8f3e86.

This pull request removes 4 and adds 4 tests. Note that renamed tests count towards both.
Hydra.Chain.Direct.Contract/CloseCurrent ‑ does not survive random adversarial mutations
Hydra.Chain.Direct.Contract/CloseCurrent ‑ is healthy
Hydra.Chain.Direct.Contract/CloseOutdated ‑ does not survive random adversarial mutations
Hydra.Chain.Direct.Contract/CloseOutdated ‑ is healthy
Hydra.Chain.Direct.Contract/CloseUnused ‑ does not survive random adversarial mutations
Hydra.Chain.Direct.Contract/CloseUnused ‑ is healthy
Hydra.Chain.Direct.Contract/CloseUsed ‑ does not survive random adversarial mutations
Hydra.Chain.Direct.Contract/CloseUsed ‑ is healthy

♻️ This comment has been updated with latest results.

@ffakenz ffakenz marked this pull request as ready for review July 30, 2024 08:31
To be defined from the script's point of view.

- Current -> Unused
- Outdated -> Used
@ch1bo ch1bo force-pushed the ensemble/rename-close-redeemer-types branch from 126882b to ab5194e Compare July 30, 2024 13:43
Copy link
Collaborator

@ch1bo ch1bo left a comment

Choose a reason for hiding this comment

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

Rename is good, see open conversation for what we could do.

@ffakenz ffakenz merged commit 5133bd7 into master Jul 30, 2024
21 checks passed
@ffakenz ffakenz deleted the ensemble/rename-close-redeemer-types branch July 30, 2024 16:38
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