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

Update instructions on how to get the explorer self-hosted runner up #1644

Merged
merged 2 commits into from
Sep 19, 2024

Conversation

ch1bo
Copy link
Collaborator

@ch1bo ch1bo commented Sep 19, 2024

Something more declarative would be more desirable, but this was an unplanned effort to get explorer.hydra.family working again.

Something more declarative would be more desirable, but this was an
unplanned effort to get explorer.hydra.family working again.
@ch1bo ch1bo requested a review from a team September 19, 2024 07:20
Copy link

github-actions bot commented Sep 19, 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-09-19 07:33:03.578658136 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 2ee477c60839936be49a50030690865b5bed4db8cd2f05bf255ac680 10068
μHead a1610f6e64843161f4a88229c0286176f5325de3e2f773eec2b1d818* 4508
νDeposit c2117fd9ebdee3e96b81fd67ff7092d638926415c10f1f7e5a267ad0 2791
  • 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 5100 5.85 2.31 0.44
2 5298 6.99 2.76 0.46
3 5498 8.41 3.32 0.48
5 5901 11.22 4.43 0.53
10 6906 18.21 7.20 0.65
57 16355 82.99 32.83 1.78

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 569 10.52 4.15 0.29
2 757 13.86 5.65 0.34
3 947 17.33 7.20 0.38
5 1320 24.65 10.44 0.48
10 2255 45.22 19.36 0.75
20 4132 95.99 40.76 1.40

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 560 22.14 8.66 0.42
2 113 675 32.10 12.73 0.53
3 170 786 44.99 18.02 0.68
4 227 893 57.69 23.35 0.82
5 282 1004 76.46 31.04 1.04
6 340 1116 96.98 39.52 1.27

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 638 17.95 7.88 0.38
2 768 18.54 8.78 0.40
3 1024 22.29 11.01 0.45
5 1302 24.36 13.22 0.50
10 1871 30.47 19.28 0.62
47 7701 94.49 71.21 1.77

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 653 20.07 9.02 0.41
2 783 21.57 10.43 0.43
3 1017 23.87 12.52 0.48
5 1177 25.96 14.63 0.52
10 1928 33.94 22.25 0.67
50 8009 97.85 83.21 1.89

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 663 25.89 11.13 0.47
2 801 27.69 12.65 0.50
3 958 29.37 14.14 0.53
5 1360 34.05 18.12 0.62
10 2073 43.06 25.92 0.78
39 6269 96.30 71.89 1.72

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 4971 17.47 7.59 0.56
2 5097 28.42 12.45 0.69
3 5261 42.37 18.75 0.86
4 5288 52.89 23.25 0.98
5 5473 71.27 31.54 1.19
6 5694 97.52 43.46 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 4935 8.09 3.42 0.46
5 1 56 4968 8.80 3.95 0.47
5 5 284 5103 13.55 6.89 0.53
5 10 568 5273 19.20 10.45 0.61
5 20 1138 5612 30.33 17.48 0.77
5 30 1706 5952 41.65 24.61 0.93
5 40 2274 6291 52.78 31.65 1.08
5 50 2847 6633 64.31 38.86 1.24
5 81 4612 7686 99.67 61.07 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-09-19 07:35:23.46847279 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.447940845
P99 10.475000259999984ms
P95 5.544232749999998ms
P50 4.216734499999999ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 22.754895147
P99 115.26809516000002ms
P95 29.671064349999995ms
P50 20.13113ms
Number of Invalid txs 0

@ch1bo ch1bo self-assigned this Sep 19, 2024
Copy link

github-actions bot commented Sep 19, 2024

Test Results

503 tests  ±0   497 ✅ ±0   21m 49s ⏱️ + 1m 22s
160 suites ±0     6 💤 ±0 
  7 files   ±0     0 ❌ ±0 

Results for commit 54886ee. ± Comparison against base commit aa61177.

♻️ This comment has been updated with latest results.

@ch1bo ch1bo merged commit f72a220 into master Sep 19, 2024
28 checks passed
@ch1bo ch1bo deleted the update-github-runner-instructions branch September 19, 2024 07:41
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