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

Add cardanonical schema as a submodule #1013

Merged
merged 2 commits into from
Aug 10, 2023
Merged

Add cardanonical schema as a submodule #1013

merged 2 commits into from
Aug 10, 2023

Conversation

ch1bo
Copy link
Member

@ch1bo ch1bo commented Aug 7, 2023

This will make our schema validation not fail without a commit.

Avoids https://github.com/input-output-hk/hydra/actions/runs/5788084058/job/15686670468#step:4:131 in the future.


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

This will make our schema validation not fail without a commit.
@github-actions
Copy link

github-actions bot commented Aug 7, 2023

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 2023-08-08 06:29:38.086673696 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial 7ceb53f05e444cfdabfd0a37a0590090066da457a1f1db30d613b8bd 4289
νCommit 70e70fc13217bfde96932956656c1d540a743b1588c845ca09dc3723 2124
νHead cda51d313c1c8285b6925ce2413def012db27f544e2bbd79b8173000 9185
μHead 1c0b665fc49bc2e9e2ce4e8252c8f37fe84dd75bd8e086abfdb92685* 4149
  • 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 4740 15.41 6.04 0.53
2 4945 16.81 6.54 0.55
3 5150 19.38 7.51 0.59
5 5563 23.01 8.85 0.64
10 6592 35.25 13.47 0.82
37 12125 98.81 37.38 1.75

Cost of Commit Transaction

This is using ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 599 14.97 5.73 0.34
2 784 19.66 7.73 0.40
3 969 24.76 9.87 0.46
5 1341 36.19 14.60 0.61
10 2290 71.91 28.91 1.04
13 2844 98.24 39.22 1.35

Cost of CollectCom Transaction

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 814 28.09 10.90 0.49
2 114 1136 43.99 17.19 0.68
3 170 1455 61.74 24.29 0.89
4 225 1783 83.37 32.93 1.14

Cost of Close Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 639 18.68 8.34 0.39
2 837 20.95 10.10 0.43
3 970 21.48 10.85 0.44
5 1299 24.27 13.37 0.50
10 1471 25.82 11.18 0.50
50 8733 87.25 69.99 1.74

Cost of Contest Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 676 24.44 10.50 0.45
2 841 26.16 11.87 0.48
3 1013 28.31 13.41 0.52
5 1336 31.75 16.15 0.58
10 2162 40.34 23.01 0.74
44 7773 98.80 69.64 1.79

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 4855 22.60 9.44 0.61
2 5177 37.05 15.68 0.79
3 5357 49.53 20.90 0.94
4 5819 74.51 31.94 1.24
5 6140 97.88 42.10 1.51

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 4769 8.72 3.59 0.46
5 1 57 4803 10.12 4.41 0.48
5 5 283 4944 15.71 7.72 0.55
5 10 568 5128 22.69 11.84 0.64
5 20 1138 5483 36.67 20.11 0.83
5 30 1709 5846 50.65 28.38 1.02
5 40 2277 6205 64.63 36.65 1.21
5 50 2846 6561 78.62 44.92 1.40
5 65 3702 7104 99.62 57.34 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 2023-08-08 06:23:57.229046585 UTC

3-nodes Scenario

A rather typical setup, with 3 nodes forming a Hydra head.

Number of nodes 3
Number of txs 900
Avg. Confirmation Time (ms) 102.591729972
P99 311.41218226999996ms
P95 230.98240399999997ms
P50 90.056389ms
Number of Invalid txs 0

Baseline Scenario

This scenario represents a minimal case and as such is a good baseline against which to assess the overhead introduced by more complex setups. There is a single hydra-node d with a single client submitting single input and single output transactions with a constant UTxO set of 1.

Number of nodes 1
Number of txs 300
Avg. Confirmation Time (ms) 4.293556663
P99 13.35813912ms
P95 9.27547605ms
P50 3.050727ms
Number of Invalid txs 0

@github-actions
Copy link

github-actions bot commented Aug 7, 2023

Test Results

359 tests  ±0   354 ✔️ ±0   19m 19s ⏱️ - 1m 33s
119 suites ±0       5 💤 ±0 
    6 files   ±0       0 ±0 

Results for commit 081dc8f. ± Comparison against base commit 15cb3e4.

♻️ This comment has been updated with latest results.

This is now needed as we depend on cardanonical as submodule in the
repository (as opposed to a remote link)
@ch1bo ch1bo merged commit 7b41adf into master Aug 10, 2023
33 checks passed
@ch1bo ch1bo deleted the cardanonical-submodule branch August 10, 2023 06:06
@ch1bo ch1bo added this to the 0.12.0 milestone Aug 18, 2023
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.

None yet

2 participants