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

Improve message printed when era is not supported #1255

Merged
merged 1 commit into from
Jan 17, 2024

Conversation

ch1bo
Copy link
Collaborator

@ch1bo ch1bo commented Jan 16, 2024

We distinguish an era not supported yet from not supported anymore. This allows us to give better instructions.

Note that no "supported yet" era exists right now.


  • 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 January 16, 2024 14:58
Copy link

github-actions bot commented Jan 16, 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-01-17 13:57:03.673454407 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 4375 10.25 3.95 0.45
2 4576 12.70 4.89 0.49
3 4776 15.07 5.79 0.52
5 5180 19.31 7.39 0.59
10 6188 30.30 11.55 0.75
41 12417 98.92 37.55 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 724 15.04 6.07 0.35
3 905 18.85 7.75 0.40
5 1285 26.90 11.27 0.51
10 2216 49.55 20.97 0.80
19 3901 99.43 41.75 1.43

Cost of CollectCom Transaction

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 480 21.12 8.27 0.40
2 114 590 32.22 12.74 0.53
3 170 700 46.18 18.38 0.69
4 227 814 62.14 24.85 0.87
5 283 920 77.70 31.28 1.04

Cost of Close Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 565 16.72 7.71 0.37
2 671 18.00 8.95 0.39
3 874 19.81 10.61 0.43
5 1267 23.54 14.10 0.50
10 2212 32.95 22.50 0.68
50 8981 98.78 83.91 1.95

Cost of Contest Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 573 20.22 8.95 0.40
2 746 22.22 10.66 0.44
3 902 23.83 12.06 0.47
5 1247 27.84 15.47 0.54
10 2077 36.72 23.26 0.71
43 7815 98.74 77.50 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 4222 15.23 6.27 0.50
2 4383 27.11 11.58 0.65
3 4569 42.38 18.35 0.83
4 4838 66.23 29.16 1.11
5 4897 80.37 35.25 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 4206 8.05 3.37 0.42
5 1 57 4239 9.28 4.13 0.44
5 5 285 4375 14.19 7.18 0.51
5 10 570 4545 20.34 10.99 0.59
5 20 1138 4883 32.85 18.71 0.77
5 30 1706 5223 44.94 26.25 0.93
5 40 2275 5562 57.46 33.97 1.10
5 50 2846 5904 69.44 41.47 1.27
5 74 4209 6715 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-01-17 14:01:10.047074849 UTC

Baseline Scenario

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 23.969738871
P99 116.22827548000001ms
P95 33.60205499999999ms
P50 21.00026ms
Number of Invalid txs 0

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.479276407
P99 9.73211864ms
P95 5.550465549999998ms
P50 4.246463ms
Number of Invalid txs 0

@ch1bo ch1bo added this to the 0.15.0 milestone Jan 16, 2024
Copy link

github-actions bot commented Jan 16, 2024

Test Results

408 tests  ±0   401 ✅ ±0   16m 11s ⏱️ +11s
136 suites ±0     7 💤 ±0 
  5 files   ±0     0 ❌ ±0 

Results for commit 16f8e93. ± Comparison against base commit 2a68a74.

♻️ This comment has been updated with latest results.

We distinguish an era not supported yet from not supported anymore. This
allows us to give better instructions.

Note that no "supported yet" era exists right now.
@ch1bo ch1bo merged commit d845064 into master Jan 17, 2024
21 checks passed
@ch1bo ch1bo deleted the era-not-supported-message branch January 17, 2024 15:54
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