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 new hydra logo and give credit #1411

Merged
merged 2 commits into from
May 3, 2024
Merged

Add new hydra logo and give credit #1411

merged 2 commits into from
May 3, 2024

Conversation

ch1bo
Copy link
Collaborator

@ch1bo ch1bo commented May 2, 2024

Replaces the logo used on https://hydra.family and https://explorer.hydra.family


  • 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 May 2, 2024 13:29
@ch1bo ch1bo marked this pull request as draft May 2, 2024 13:30
@ch1bo ch1bo force-pushed the new-logo branch 2 times, most recently from ce0f558 to fd2b53c Compare May 2, 2024 13:30
Copy link

github-actions bot commented May 2, 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-05-03 13:14:51.297326296 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial bccf2a430c016bc960fbf31b02694011cd399d20da8882aac9d33611 4110
νCommit 56b0f0b597150e619c76bed60683f3b1e42d7bc0685ed951b882bfc5 1975
νHead 86bff95ba20e9d1d1b34899a56d86bbacc9fed999260b27dcc92d128 9351
μHead 88f533cf67cd0fc93d7d9ccf0a8b1d69ffd1208a825efbebbc1d36ba* 4213
  • 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 4795 8.78 3.35 0.46
2 4995 10.85 4.15 0.49
3 5194 12.89 4.94 0.52
5 5604 16.72 6.41 0.58
10 6605 26.12 10.01 0.72
48 14245 99.85 38.32 1.86

Cost of Commit Transaction

This is using ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 559 10.24 4.04 0.29
2 749 13.88 5.64 0.34
3 936 17.66 7.29 0.39
5 1310 25.66 10.74 0.49
10 2250 48.19 20.30 0.78
19 3926 97.83 40.79 1.41

Cost of CollectCom Transaction

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 544 16.52 6.53 0.35
2 113 654 26.30 10.50 0.47
3 170 764 38.72 15.57 0.61
4 226 878 50.28 20.41 0.74
5 283 988 69.00 28.00 0.95
6 338 1095 82.24 33.70 1.11

Cost of Close Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 624 8.34 4.63 0.28
2 749 9.04 5.69 0.30
3 976 10.57 7.43 0.33
5 1188 11.40 9.13 0.36
10 1312 14.18 7.74 0.38
50 4539 38.02 22.90 0.82

Cost of Contest Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 644 8.69 4.76 0.28
2 716 8.89 5.44 0.29
3 914 9.98 6.84 0.32
5 1355 13.11 10.32 0.39
10 2029 17.45 16.10 0.50
50 8069 51.64 63.65 1.38

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 4657 17.09 7.39 0.55
2 4739 26.77 11.60 0.66
3 4975 41.84 18.40 0.84
4 5101 58.36 25.64 1.03
5 5139 67.19 29.29 1.13
6 5230 86.82 37.92 1.36

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 4627 8.06 3.37 0.44
5 1 57 4661 9.00 3.99 0.46
5 5 283 4796 13.40 6.75 0.52
5 10 571 4968 19.58 10.49 0.60
5 20 1140 5308 30.69 17.44 0.76
5 30 1706 5645 42.01 24.49 0.91
5 40 2277 5986 53.75 31.72 1.08
5 50 2846 6325 65.29 38.86 1.24
5 79 4496 7308 99.21 59.77 1.70

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-05-03 13:17:03.137538492 UTC

Baseline Scenario

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 21.394644196
P99 107.80623691ms
P95 30.691922599999987ms
P50 18.7843545ms
Number of Invalid txs 0

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 3.621624457
P99 5.648038459999991ms
P95 4.251283699999999ms
P50 3.506527ms
Number of Invalid txs 0

Copy link

github-actions bot commented May 2, 2024

Test Results

425 tests  ±0   415 ✅ ±0   14m 16s ⏱️ +24s
138 suites ±0    10 💤 ±0 
  2 files   ±0     0 ❌ ±0 

Results for commit fd2b53c. ± Comparison against base commit 24c6bd8.

@ch1bo ch1bo self-assigned this May 3, 2024
ch1bo added 2 commits May 3, 2024 15:11
This uses also the automatic switch of black/white in the SVG.
@ch1bo ch1bo marked this pull request as ready for review May 3, 2024 13:11
@ch1bo ch1bo enabled auto-merge May 3, 2024 13:12
@ch1bo ch1bo merged commit 45292ad into master May 3, 2024
19 of 20 checks passed
@ch1bo ch1bo deleted the new-logo branch May 3, 2024 13:20
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