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

Disable Hydra CI for darwin builds #1242

Merged
merged 1 commit into from
Jan 9, 2024
Merged

Disable Hydra CI for darwin builds #1242

merged 1 commit into from
Jan 9, 2024

Conversation

ch1bo
Copy link
Collaborator

@ch1bo ch1bo commented Jan 9, 2024

The IOG Hydra CI is often failing on the darwin runners and we want to have less false negatives on our tests. Now that we have own github actions, this should only impact nix cache hits on cache.iog.io


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

@ch1bo ch1bo changed the title Disable Hydra CI for darwin runners Disable Hydra CI for darwin builds Jan 9, 2024
Copy link

github-actions bot commented Jan 9, 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-01-09 14:48:34.578579039 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial 985245919fcc6c0c5cd116023cd2c947c43e80dcbb5075fe12433fbb 4072
νCommit 7cb20fa71eb4c563ca283566ebe0aa65859d96c3f8cba35c52c181fd 2043
νHead 7a36661f5c15e9f1783aeaab890812c59b7286cbbc6de762d3110772 8816
μHead 8b111ac12274e46314769295a1c5dcab1d260096fc469fd698065463* 3851
  • 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 4375 10.40 4.01 0.46
2 4576 12.70 4.89 0.49
3 4777 14.73 5.65 0.52
5 5180 19.50 7.47 0.59
10 6185 30.29 11.55 0.75
41 12417 99.15 37.65 1.77

Cost of Commit Transaction

This is using ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 534 11.37 4.44 0.30
2 721 15.04 6.07 0.35
3 911 18.85 7.75 0.40
5 1285 26.90 11.27 0.51
10 2219 49.55 20.97 0.80
19 3899 99.43 41.75 1.43

Cost of CollectCom Transaction

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 484 21.78 8.51 0.41
2 114 590 33.30 13.14 0.54
3 170 700 48.45 19.21 0.71
4 227 814 59.37 23.84 0.84
5 283 920 80.03 32.16 1.07
6 339 1031 96.67 39.07 1.26

Cost of Close Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 469 15.16 6.43 0.34
2 748 18.45 9.33 0.40
3 862 19.73 10.57 0.42
5 935 21.17 9.77 0.43
10 2015 31.05 21.11 0.64
50 8778 96.33 82.47 1.91

Cost of Contest Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 566 20.23 8.95 0.40
2 768 22.30 10.71 0.44
3 941 24.11 12.34 0.48
5 1203 27.38 15.12 0.53
10 2147 37.29 23.75 0.72
43 7792 99.59 77.60 1.86

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 4307 19.02 8.18 0.55
2 4489 32.15 14.00 0.71
3 4683 47.53 20.87 0.89
4 4828 66.34 29.19 1.11
5 4921 80.07 35.15 1.27

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 4205 8.26 3.46 0.43
5 1 57 4240 9.28 4.13 0.44
5 5 285 4375 14.19 7.18 0.51
5 10 569 4544 20.55 11.08 0.60
5 20 1138 4883 32.85 18.71 0.77
5 30 1709 5226 44.94 26.25 0.93
5 40 2276 5563 57.33 33.92 1.10
5 50 2843 5901 69.52 41.50 1.27
5 74 4214 6719 99.34 59.96 1.68

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-01-09 14:51:15.036300944 UTC

Baseline Scenario

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 23.285673603
P99 117.75826750000002ms
P95 32.579188949999974ms
P50 19.8669455ms
Number of Invalid txs 0

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 3.990143864
P99 7.4482345099999945ms
P95 4.75111725ms
P50 3.846885ms
Number of Invalid txs 0

@ch1bo ch1bo requested a review from a team January 9, 2024 14:34
The IOG Hydra CI is often failing on the darwin runners and we want to
have less false negatives on our tests. Now that we have own github
actions, this should only impact nix cache hits on cache.iog.io
Copy link

github-actions bot commented Jan 9, 2024

Test Results

393 tests   385 ✅  18m 22s ⏱️
132 suites    8 💤
  5 files      0 ❌

Results for commit 55a8c68.

@ch1bo ch1bo merged commit 3c8f217 into master Jan 9, 2024
21 checks passed
@ch1bo ch1bo deleted the no-darwin-hydra-ci branch January 9, 2024 17:05
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