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

Remove initUTxO from Ledger handle #1312

Merged
merged 1 commit into from
Feb 20, 2024
Merged

Conversation

ch1bo
Copy link
Collaborator

@ch1bo ch1bo commented Feb 19, 2024

Minor refactor.

This was not really used anywhere and is redundant to the Monoid (UTxOType tx) constraint.


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

@ch1bo ch1bo requested a review from a team February 19, 2024 17:42
Copy link

github-actions bot commented Feb 19, 2024

Transactions 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-02-20 08:41:13.425746054 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial 985245919fcc6c0c5cd116023cd2c947c43e80dcbb5075fe12433fbb 4072
νCommit 7cb20fa71eb4c563ca283566ebe0aa65859d96c3f8cba35c52c181fd 2043
νHead 7a36661f5c15e9f1783aeaab890812c59b7286cbbc6de762d3110772 8816
μHead 8b111ac12274e46314769295a1c5dcab1d260096fc469fd698065463* 3851
  • The minting policy hash is only usable for comparison. As the script is parameterized, the actual script is unique per Head.

Cost of Init Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 4433 10.48 4.05 0.46
2 4633 12.57 4.83 0.49
3 4832 14.68 5.63 0.52
5 5237 19.20 7.35 0.59
10 6243 30.41 11.60 0.75
41 12475 99.12 37.64 1.77

Cost of Commit Transaction

This is using ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 594 11.37 4.44 0.30
2 781 15.04 6.07 0.35
3 968 18.85 7.75 0.40
5 1347 26.90 11.27 0.51
10 2278 49.55 20.97 0.80
19 3969 99.43 41.75 1.43

Cost of CollectCom Transaction

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 544 21.07 8.25 0.40
2 114 654 33.30 13.14 0.54
3 171 764 44.91 17.91 0.68
4 227 874 64.61 25.75 0.90
5 282 984 77.60 31.25 1.05
6 339 1095 96.81 39.14 1.26

Cost of Close Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 599 16.64 7.66 0.37
2 726 18.00 8.95 0.39
3 863 19.36 10.24 0.42
5 978 20.81 9.55 0.43
10 1909 30.05 20.17 0.62
50 7993 91.03 77.16 1.79

Cost of Contest Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 621 20.23 8.96 0.41
2 765 21.77 10.31 0.43
3 847 22.93 11.34 0.45
5 1222 26.72 14.69 0.53
10 1902 35.12 21.89 0.68
47 7664 98.42 77.54 1.84

Cost of Abort Transaction

Some variation because of random mixture of still initial and already committed outputs.

Parties Tx size % max Mem % max CPU Min fee ₳
1 4310 18.85 8.11 0.55
2 4485 32.01 13.95 0.71
3 4538 45.02 19.63 0.86
4 4725 63.59 27.87 1.07
5 4682 74.21 32.29 1.19
6 4913 98.07 42.98 1.47

Cost of FanOut Transaction

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 4265 7.84 3.28 0.42
5 1 57 4300 8.86 3.96 0.44
5 5 285 4435 14.07 7.13 0.51
5 10 570 4605 19.92 10.81 0.59
5 20 1138 4944 32.22 18.44 0.76
5 30 1710 5288 44.73 26.16 0.93
5 40 2283 5631 56.62 33.62 1.10
5 50 2848 5965 69.56 41.52 1.27
5 74 4210 6775 99.13 59.87 1.68

End-To-End Benchmark Results

This page is intended to collect the latest end-to-end benchmarks results produced by Hydra's Continuous Integration system from the latest master code.

Please take those results with a grain of salt as they are currently produced from very limited cloud VMs and not controlled hardware. Instead of focusing on the absolute results, the emphasis should be on relative results, eg. how the timings for a scenario evolve as the code changes.

Generated at 2024-02-20 08:42:17.035540254 UTC

Baseline Scenario

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 22.037993057
P99 104.1109925800002ms
P95 31.223011049999982ms
P50 19.7000535ms
Number of Invalid txs 0

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.610992321
P99 7.401887709999994ms
P95 5.913055199999999ms
P50 4.446867ms
Number of Invalid txs 0

@ch1bo ch1bo force-pushed the ch1bo/remove-ledger-init-utxo branch from 42882f9 to 2442c03 Compare February 20, 2024 07:49
Copy link

github-actions bot commented Feb 20, 2024

Test Results

416 tests  ±0   409 ✅ ±0   12m 54s ⏱️ -45s
139 suites ±0     7 💤 ±0 
  5 files   ±0     0 ❌ ±0 

Results for commit b3f4871. ± Comparison against base commit 39d0226.

♻️ This comment has been updated with latest results.

This was not really used anywhere and is redundant to the
Monoid (UTxOType tx) constraint.
@ch1bo ch1bo force-pushed the ch1bo/remove-ledger-init-utxo branch from 2442c03 to b3f4871 Compare February 20, 2024 08:35
@ch1bo ch1bo merged commit 4463d6f into master Feb 20, 2024
21 checks passed
@ch1bo ch1bo deleted the ch1bo/remove-ledger-init-utxo branch February 20, 2024 10:15
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