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

Incremental decommit e2e scenario #1208

Merged
merged 5 commits into from
Dec 13, 2023

Conversation

v0d1ch
Copy link
Contributor

@v0d1ch v0d1ch commented Dec 12, 2023

fix #1205


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

@v0d1ch
Copy link
Contributor Author

v0d1ch commented Dec 12, 2023

It's expected that the hydra-cluster test will fail for this PR since the implementation is missing.

Copy link

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-12-12 16:35:27.105270126 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 4379 10.25 3.95 0.45
2 4573 12.57 4.83 0.49
3 4777 14.68 5.63 0.52
5 5179 19.16 7.33 0.59
10 6182 30.39 11.59 0.75
41 12415 99.15 37.65 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 534 11.37 4.44 0.30
2 723 15.04 6.07 0.35
3 910 18.85 7.75 0.40
5 1288 26.90 11.27 0.51
10 2218 49.55 20.97 0.80
19 3909 99.43 41.75 1.43

Cost of CollectCom Transaction

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 484 21.12 8.27 0.40
2 114 590 32.30 12.77 0.53
3 170 700 47.15 18.73 0.70
4 226 810 61.64 24.66 0.86
5 283 920 82.44 33.02 1.09
6 338 1031 93.11 37.77 1.22

Cost of Close Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 555 16.68 7.68 0.36
2 713 18.49 9.31 0.40
3 890 19.77 10.61 0.43
5 1252 23.35 13.88 0.49
10 2225 32.71 22.41 0.67
50 8882 98.74 83.36 1.94

Cost of Contest Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 569 20.27 8.97 0.40
2 749 22.26 10.68 0.44
3 943 24.15 12.36 0.48
5 1304 27.84 15.58 0.54
10 2210 37.88 24.21 0.73
43 7755 99.15 77.25 1.85

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 4324 18.89 8.13 0.55
2 4410 27.02 11.56 0.65
3 4670 47.48 20.85 0.89
4 4822 66.02 29.06 1.11
5 4947 80.65 35.39 1.27

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 4205 7.84 3.28 0.42
5 1 57 4239 9.49 4.22 0.44
5 5 284 4374 14.40 7.27 0.51
5 10 568 4543 20.55 11.08 0.60
5 20 1140 4886 32.85 18.71 0.77
5 30 1710 5228 45.15 26.34 0.93
5 40 2278 5565 57.33 33.92 1.10
5 50 2846 5904 69.35 41.43 1.27
5 74 4210 6715 99.34 59.96 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-12-12 16:39:40.934394074 UTC

Baseline Scenario

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 23.403225056
P99 118.27788289000001ms
P95 32.28985445ms
P50 19.844242ms
Number of Invalid txs 0

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.029961576
P99 5.756109959999997ms
P95 4.707107699999998ms
P50 3.914789ms
Number of Invalid txs 0

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.

LGTM and should serve us well as a driver for the next steps.

@ch1bo ch1bo merged commit cc69ed1 into feature/incremental-decommit Dec 13, 2023
19 of 20 checks passed
@ch1bo ch1bo deleted the incremental-decommit-e2e-scenario branch December 13, 2023 08:57
@ch1bo ch1bo linked an issue Dec 13, 2023 that may be closed by this pull request
ch1bo added a commit that referenced this pull request Dec 13, 2023
…e-scenario

Incremental decommit e2e scenario
ch1bo added a commit that referenced this pull request Dec 14, 2023
…e-scenario

Incremental decommit e2e scenario
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.

Create the happy path End-to-End scenario
2 participants