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 tx metadata to label Hydra transactions #1311

Merged
merged 2 commits into from
Feb 19, 2024
Merged

Add tx metadata to label Hydra transactions #1311

merged 2 commits into from
Feb 19, 2024

Conversation

ch1bo
Copy link
Member

@ch1bo ch1bo commented Feb 16, 2024

This is only for informational purposes and helps with debugging by identifying Hydra protocol transactions more quickly.

For example with renderTx:
image


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

This is only for informational purposes and helps with debugging by
identifying Hydra protocol transactions more quickly.
@ch1bo ch1bo requested a review from a team February 16, 2024 14:45
Copy link

github-actions bot commented Feb 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-02-16 16:04:01.383535246 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.25 3.95 0.46
2 4634 12.47 4.79 0.49
3 4835 14.68 5.63 0.52
5 5237 19.12 7.31 0.59
10 6240 30.30 11.55 0.75
41 12476 99.11 37.63 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 782 15.04 6.07 0.35
3 972 18.85 7.75 0.40
5 1345 26.90 11.27 0.51
10 2275 49.55 20.97 0.80
19 3967 99.43 41.75 1.43

Cost of CollectCom Transaction

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 56 543 21.07 8.25 0.40
2 114 658 34.16 13.45 0.55
3 170 764 45.00 17.95 0.68
4 226 874 59.00 23.71 0.84
5 282 984 74.67 30.18 1.01
6 340 1095 91.72 37.28 1.21

Cost of Close Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 595 16.68 7.67 0.37
2 731 18.04 8.96 0.39
3 724 17.75 7.78 0.38
5 1217 23.03 13.54 0.49
10 1883 29.76 20.04 0.62
50 7805 88.98 75.74 1.76

Cost of Contest Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 636 20.22 8.96 0.41
2 757 21.85 10.34 0.43
3 889 23.42 11.71 0.46
5 1203 26.77 14.70 0.53
10 2094 36.56 23.02 0.70
46 7596 98.96 77.25 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 4222 15.19 6.26 0.50
2 4420 30.84 13.37 0.69
3 4578 46.46 20.31 0.87
4 4774 64.36 28.30 1.08
5 4911 85.46 37.65 1.33

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 4266 7.84 3.28 0.42
5 1 57 4300 8.44 3.78 0.43
5 5 284 4435 13.77 7.00 0.51
5 10 571 4606 19.92 10.81 0.59
5 20 1137 4942 32.22 18.44 0.76
5 30 1710 5287 44.52 26.07 0.93
5 40 2277 5625 56.83 33.70 1.10
5 50 2849 5967 68.93 41.25 1.27
5 74 4208 6773 98.92 59.78 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-16 16:07:27.039837338 UTC

Baseline Scenario

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 22.369150979
P99 115.96961958ms
P95 31.527943149999967ms
P50 19.500669000000002ms
Number of Invalid txs 0

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.032315389
P99 7.624928829999973ms
P95 4.915809049999998ms
P50 3.8861600000000003ms
Number of Invalid txs 0

Copy link

github-actions bot commented Feb 16, 2024

Test Results

415 tests  ±0   408 ✅ ±0   13m 13s ⏱️ +37s
139 suites ±0     7 💤 ±0 
  5 files   ±0     0 ❌ ±0 

Results for commit e8fb5fe. ± Comparison against base commit a19389f.

♻️ This comment has been updated with latest results.

This allows for targeted debugging and quick identification of transactions.
@ch1bo ch1bo merged commit 8c6e4bf into master Feb 19, 2024
21 checks passed
@ch1bo ch1bo deleted the add-tx-metadata branch February 19, 2024 10: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