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

Remove hydra-explorer from this repo #1736

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

noonio
Copy link
Contributor

@noonio noonio commented Nov 8, 2024

This removes the hydra-explorer from this repo; and needs to be merged in combination with cardano-scaling/hydra-explorer#5.

Note that there was one set of tests in the hydra-cluster tool that depended on the explorer; I've had to then remove those here, but am not yet sure if I can get them to work over on the other side.

Todo:

  • Update changelog
  • Check for references in the docs
  • ???

Copy link

github-actions bot commented Nov 8, 2024

Transaction cost differences

No cost or size differences found

Copy link

github-actions bot commented Nov 8, 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-11-14 11:02:34.78726403 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial 00a6ddbc130ab92f5b7cb8d1ccd8d79eca5bfe25f6843c07b62841f0 2667
νCommit 3e5a776bcee213e3dfd15806952a10ac5590e3e97d09d62eb99266b2 690
νHead 00e0e6aceb51fcb4fcc5dc6032cc524a641163f0723b25d995de3ae8 12633
μHead 134f18365d53de72b07af2e703c96d8a6f0643c71d4c1a2050b8182a* 11111
νDeposit 2feb47889a4f658dc593cefcb0e37d584b9431944f08a687f3dab4af 4865
  • 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 11695 8.69 2.83 0.76
2 11897 10.61 3.46 0.78
3 12098 12.20 3.97 0.81
5 12499 16.05 5.24 0.87
10 13505 24.84 8.09 1.00
24 16321 49.11 15.95 1.38

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 561 2.45 1.17 0.20
2 736 3.40 1.74 0.22
3 916 4.39 2.34 0.24
5 1276 6.46 3.61 0.28
10 2170 12.24 7.28 0.40
54 10054 99.20 68.72 1.89

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 560 24.73 7.20 0.43
2 114 671 31.60 9.23 0.50
3 170 782 39.50 11.53 0.59
4 227 893 52.91 15.18 0.73
5 282 1004 59.86 17.16 0.80
6 338 1116 68.20 19.62 0.89
7 393 1227 82.96 23.60 1.04
8 448 1342 92.85 26.39 1.15

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 633 22.54 7.29 0.41
2 817 25.05 8.65 0.45
3 949 26.53 9.74 0.48
5 1216 28.61 11.64 0.52
10 1930 37.02 17.33 0.66
43 6711 93.46 55.21 1.60

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 644 24.31 8.00 0.43
2 737 25.26 8.87 0.45
3 933 27.43 10.33 0.49
5 1320 31.63 13.21 0.56
10 2018 39.94 19.27 0.70
43 7069 99.59 61.57 1.71

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 687 30.32 9.61 0.49
2 811 32.21 10.85 0.52
3 1051 35.16 12.65 0.57
5 1288 38.40 14.88 0.62
10 2056 48.77 21.63 0.79
33 5726 98.87 53.78 1.59

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 11598 25.71 8.76 0.93
2 11652 33.15 11.21 1.01
3 11733 38.50 12.99 1.07
4 11950 49.07 16.71 1.19
5 12181 61.36 20.93 1.33
6 12192 66.22 22.49 1.38
7 12446 79.04 27.10 1.53
8 12671 87.77 30.01 1.63
9 12746 97.52 33.16 1.74

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 ₳
10 0 0 11692 16.98 5.80 0.84
10 1 57 11726 19.19 6.70 0.87
10 5 285 11862 26.60 9.74 0.96
10 10 570 12032 36.96 13.95 1.08
10 20 1139 12371 54.38 21.17 1.29
10 30 1710 12715 74.00 29.19 1.52
10 40 2278 13052 91.44 36.40 1.73
10 44 2504 13186 98.85 39.45 1.81

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-11-14 11:06:31.338908511 UTC

Baseline Scenario

Number of nodes 1
Number of txs 300
Avg. Confirmation Time (ms) 4.383723986
P99 9.337087859999983ms
P95 5.501549400000003ms
P50 4.144717999999999ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 900
Avg. Confirmation Time (ms) 23.962907955
P99 116.76716360999994ms
P95 33.6463994ms
P50 20.846647500000003ms
Number of Invalid txs 0

Copy link

github-actions bot commented Nov 8, 2024

Test Results

  5 files  ±0  161 suites   - 1   28m 58s ⏱️ +29s
551 tests  - 3  545 ✅  - 3  6 💤 ±0  0 ❌ ±0 
553 runs   - 3  547 ✅  - 3  6 💤 ±0  0 ❌ ±0 

Results for commit 5d12347. ± Comparison against base commit 27fc223.

This pull request removes 3 tests.
Test.HydraExplorer ‑ can observe hydra transactions created by multiple hydra-nodes
Test.HydraExplorer ‑ can query for all hydra heads observed
Test.HydraExplorer ‑ can query for latest point in time observed on chain

♻️ This comment has been updated with latest results.

@noonio noonio force-pushed the remove-hydra-explorer-from-repo branch 2 times, most recently from 4dc77d8 to 76ee960 Compare November 13, 2024 10:07
@v0d1ch v0d1ch marked this pull request as ready for review November 14, 2024 10:57
@v0d1ch v0d1ch force-pushed the remove-hydra-explorer-from-repo branch from 76ee960 to 5d12347 Compare November 14, 2024 10:58
@locallycompact locallycompact added this pull request to the merge queue Nov 15, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 15, 2024
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