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

Derive head id and seed from node id in offline mode #1551

Merged
merged 1 commit into from
Aug 8, 2024
Merged

Conversation

ch1bo
Copy link
Collaborator

@ch1bo ch1bo commented Aug 6, 2024

Something requested by @Quantumplation for hydra-doom, so would need to be backported to the version we use there.


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

Copy link

github-actions bot commented Aug 6, 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-08-08 12:44:11.077267345 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 5188 5.69 2.25 0.44
2 5390 7.03 2.77 0.46
3 5590 8.37 3.30 0.49
5 5998 11.26 4.45 0.54
10 6998 18.24 7.22 0.66
56 16246 81.61 32.28 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 748 13.86 5.65 0.34
3 934 17.33 7.20 0.38
5 1310 24.65 10.44 0.48
10 2244 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.93 13.42 0.55
3 170 769 47.40 18.92 0.70
4 225 879 62.78 25.24 0.88
5 284 989 76.60 31.10 1.04
6 339 1100 96.30 39.25 1.26

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 630 17.93 7.87 0.38
2 771 19.36 9.17 0.41
3 848 19.24 9.80 0.41
5 1289 24.17 13.14 0.50
10 2145 32.86 20.15 0.66
47 7600 97.41 72.29 1.79

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 596 20.60 9.07 0.41
2 792 22.45 10.81 0.44
3 1058 24.75 12.92 0.49
5 1179 26.86 15.01 0.53
10 2173 36.33 23.97 0.71
49 8236 99.52 84.22 1.92

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 674 27.14 11.66 0.48
2 835 28.98 13.22 0.52
3 964 30.76 14.72 0.55
5 1225 34.27 17.74 0.61
10 2057 44.84 26.65 0.80
39 6137 97.57 72.09 1.73

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 5066 17.43 7.58 0.57
2 5241 29.27 12.91 0.71
3 5359 42.84 18.95 0.87
4 5503 59.51 26.46 1.06
5 5515 74.47 33.01 1.23
6 5750 97.31 43.35 1.50

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 5056 8.88 3.99 0.47
5 5 285 5192 13.60 6.92 0.54
5 10 570 5362 18.87 10.31 0.61
5 20 1138 5701 30.58 17.60 0.78
5 30 1704 6038 41.51 24.55 0.93
5 40 2276 6380 53.23 31.84 1.09
5 50 2846 6720 64.37 38.89 1.25
5 81 4611 7773 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-08-08 12:47:33.384393468 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 3.894666858
P99 10.528685859999992ms
P95 4.593354849999998ms
P50 3.6690505ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 23.250163411
P99 114.81734859ms
P95 32.28822379999999ms
P50 20.453165499999997ms
Number of Invalid txs 0

Copy link

github-actions bot commented Aug 7, 2024

Test Results

465 tests  +1   458 ✅ +1   16m 48s ⏱️ +27s
149 suites ±0     7 💤 ±0 
  5 files   ±0     0 ❌ ±0 

Results for commit d30f3d7. ± Comparison against base commit 7e5730b.

♻️ This comment has been updated with latest results.

@ch1bo ch1bo requested review from Quantumplation and a team August 7, 2024 15:41
@ch1bo ch1bo marked this pull request as ready for review August 7, 2024 15:41
@ch1bo ch1bo force-pushed the offline-head-id branch 2 times, most recently from 0d9ce0d to d30f3d7 Compare August 8, 2024 07:03
@ch1bo ch1bo added this to the 0.18.0 milestone Aug 8, 2024
@ch1bo ch1bo merged commit a1b5f23 into master Aug 8, 2024
17 checks passed
@ch1bo ch1bo deleted the offline-head-id branch August 8, 2024 12:40
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