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

Only test ones we know will succeed #1628

Merged
merged 3 commits into from
Sep 13, 2024
Merged

Conversation

noonio
Copy link
Contributor

@noonio noonio commented Sep 13, 2024

A bit of a hack to only run the network tests we expect to succeed. This at least ensures we don't get any worse, even if it doesn't directly allow us to track if we're getting better.

See also actions/runner#2347

Copy link

github-actions bot commented Sep 13, 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-13 09:31:33.10278436 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 5097 5.89 2.33 0.44
2 5298 7.09 2.80 0.46
3 5498 8.55 3.38 0.49
5 5902 11.26 4.45 0.53
10 6907 18.10 7.16 0.65
57 16355 82.85 32.77 1.78

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 567 10.52 4.15 0.29
2 759 13.86 5.65 0.34
3 941 17.33 7.20 0.38
5 1320 24.65 10.44 0.48
10 2260 45.22 19.36 0.75
20 4133 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 112 671 33.93 13.42 0.55
3 170 782 47.47 18.95 0.70
4 225 893 57.83 23.41 0.83
5 280 1004 75.24 30.60 1.02
6 340 1116 93.25 38.13 1.23

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 636 17.95 7.88 0.38
2 785 19.34 9.16 0.41
3 920 19.94 10.06 0.42
5 1124 21.80 12.26 0.46
10 1954 32.78 20.21 0.65
49 7922 98.48 74.12 1.83

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 644 20.07 9.01 0.41
2 780 21.57 10.43 0.43
3 872 22.58 11.47 0.45
5 1336 26.71 15.32 0.54
10 2004 34.08 22.50 0.68
50 8002 97.40 83.03 1.89

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 684 25.89 11.14 0.47
2 810 27.73 12.66 0.50
3 943 29.42 14.14 0.53
5 1313 33.70 17.82 0.61
10 2105 43.22 26.01 0.78
39 6501 98.00 73.30 1.76

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 4984 17.47 7.60 0.57
2 5122 28.50 12.50 0.70
3 5163 40.47 17.77 0.83
4 5351 56.51 25.02 1.02
5 5402 69.49 30.68 1.17
6 5639 91.97 40.87 1.44

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 4934 7.89 3.34 0.46
5 1 57 4969 8.63 3.88 0.47
5 5 285 5104 13.35 6.81 0.53
5 10 569 5273 19.01 10.37 0.61
5 20 1138 5612 30.52 17.57 0.77
5 30 1707 5954 42.04 24.77 0.93
5 40 2273 6289 53.17 31.82 1.09
5 50 2844 6631 64.31 38.86 1.24
5 81 4608 7681 99.87 61.16 1.74

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-13 09:34:02.452818369 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 5.002209922
P99 13.041224379999992ms
P95 6.759920599999998ms
P50 4.530806ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 24.376750373
P99 107.58444267ms
P95 34.76120139999999ms
P50 21.8584325ms
Number of Invalid txs 0

Copy link

github-actions bot commented Sep 13, 2024

Test Results

490 tests  ±0   485 ✅ ±0   19m 56s ⏱️ +7s
155 suites ±0     5 💤 ±0 
  6 files   ±0     0 ❌ ±0 

Results for commit 20c212f. ± Comparison against base commit 7d9499c.

♻️ This comment has been updated with latest results.

@noonio noonio force-pushed the only-expected-success-network-tests branch from 6c82eb7 to 20c212f Compare September 13, 2024 09:28
@ch1bo ch1bo merged commit a589d93 into master Sep 13, 2024
28 checks passed
@ch1bo ch1bo deleted the only-expected-success-network-tests branch September 13, 2024 10:33
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