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

Re-enable Mithril integration tests on all networks #1432

Merged
merged 1 commit into from
May 13, 2024
Merged

Conversation

ch1bo
Copy link
Collaborator

@ch1bo ch1bo commented May 13, 2024

Now that all networks work with the currently selected mithril-client version, we can test against all networks again.


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

Now that all networks work with the currently selected mithril-client
version, we can test against all networks again.
@ch1bo ch1bo requested a review from locallycompact May 13, 2024 13:42
Copy link

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-13 13:45:15.691537808 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 4792 9.14 3.51 0.46
2 4999 10.61 4.05 0.49
3 5197 12.64 4.83 0.52
5 5600 16.72 6.41 0.58
10 6604 26.33 10.09 0.73
48 14245 99.81 38.30 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 935 17.66 7.29 0.39
5 1306 25.66 10.74 0.49
10 2245 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 548 16.52 6.53 0.35
2 113 654 26.34 10.52 0.47
3 171 764 37.85 15.25 0.60
4 226 874 50.64 20.55 0.75
5 282 984 66.90 27.24 0.93
6 339 1095 86.17 35.12 1.15

Cost of Close Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 596 8.25 4.58 0.28
2 830 9.37 6.02 0.31
3 868 9.66 6.70 0.31
5 1217 11.85 9.47 0.37
10 2103 17.25 16.24 0.50
50 8067 52.27 64.25 1.39

Cost of Contest Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 646 8.65 4.74 0.28
2 715 8.93 5.45 0.29
3 931 10.43 7.17 0.33
5 1311 12.29 9.69 0.38
10 2013 16.88 15.72 0.49
50 8124 51.26 63.34 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 4687 16.96 7.34 0.55
2 4842 28.91 12.66 0.69
3 4900 41.08 17.97 0.83
4 5174 61.21 27.00 1.07
5 5221 78.03 34.34 1.26
6 5385 98.10 43.22 1.49

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 4628 8.27 3.45 0.45
5 1 57 4662 9.00 3.99 0.46
5 5 285 4797 13.61 6.84 0.52
5 10 567 4965 19.37 10.40 0.60
5 20 1140 5308 30.48 17.36 0.76
5 30 1707 5646 42.30 24.61 0.92
5 40 2273 5983 53.75 31.72 1.08
5 50 2842 6322 65.71 39.04 1.24
5 80 4551 7340 99.73 60.22 1.71

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-13 13:48:57.140405335 UTC

Baseline Scenario

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 22.642187342
P99 67.93271082000058ms
P95 33.20112139999999ms
P50 20.091003999999998ms
Number of Invalid txs 0

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.541888929
P99 8.401686879999964ms
P95 5.857151799999999ms
P50 4.310171ms
Number of Invalid txs 0

Copy link

Test Results

426 tests  ±0   418 ✅ +2   15m 25s ⏱️ + 1m 4s
138 suites ±0     8 💤  - 2 
  2 files   ±0     0 ❌ ±0 

Results for commit 3646bef. ± Comparison against base commit 616b962.

@ch1bo ch1bo merged commit d8d2f93 into master May 13, 2024
20 checks passed
@ch1bo ch1bo deleted the mithril-tests branch May 13, 2024 14:34
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