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

Bump GHC further to 9.2.8 #1005

Merged
merged 1 commit into from
Jul 31, 2023
Merged

Bump GHC further to 9.2.8 #1005

merged 1 commit into from
Jul 31, 2023

Conversation

ch1bo
Copy link
Collaborator

@ch1bo ch1bo commented Jul 28, 2023

This is a patch release ahead of previously 9.2.7 and promises better support for newer linux kernels.

Note that this is producing the exact same scripts as plutus-tx with 9.2.7 and hence is no breaking change over current master.


  • CHANGELOG updated or not needed (GHC update already in there)
  • Documentation updated or not needed
  • Haddocks updated or not needed
  • No new TODOs introduced or explained herafter

@github-actions
Copy link

github-actions bot commented Jul 28, 2023

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 2023-07-28 18:53:08.503627104 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial 7ceb53f05e444cfdabfd0a37a0590090066da457a1f1db30d613b8bd 4289
νCommit 70e70fc13217bfde96932956656c1d540a743b1588c845ca09dc3723 2124
νHead cda51d313c1c8285b6925ce2413def012db27f544e2bbd79b8173000 9185
μHead 1c0b665fc49bc2e9e2ce4e8252c8f37fe84dd75bd8e086abfdb92685* 4149
  • 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 4743 13.81 5.39 0.51
2 4948 16.96 6.60 0.55
3 5156 18.67 7.23 0.58
5 5560 22.86 8.79 0.64
10 6589 34.06 12.99 0.81
36 11924 98.25 37.21 1.74

Cost of Commit Transaction

This is using ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 599 14.97 5.73 0.34
2 784 19.66 7.73 0.40
3 974 24.76 9.87 0.46
5 1348 36.19 14.60 0.61
10 2285 71.91 28.91 1.04
13 2838 98.24 39.22 1.35

Cost of CollectCom Transaction

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 814 27.96 10.85 0.49
2 113 1134 43.64 17.06 0.68
3 170 1455 62.29 24.50 0.89
4 227 1777 82.53 32.60 1.13

Cost of Close Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 635 18.98 8.46 0.39
2 804 20.08 9.60 0.42
3 970 21.48 10.85 0.44
5 1296 24.27 13.37 0.50
10 2132 31.27 19.66 0.64
50 8733 87.55 70.11 1.75

Cost of Contest Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 676 24.87 10.67 0.46
2 832 26.16 11.87 0.48
3 1015 28.31 13.41 0.52
5 1327 31.32 15.99 0.58
10 2161 40.34 23.01 0.74
44 7772 98.80 69.64 1.79

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 4856 22.60 9.44 0.61
2 5179 37.05 15.68 0.79
3 5499 54.19 23.12 1.00
4 5818 73.86 31.70 1.23
5 6140 97.75 42.05 1.51

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 4761 8.72 3.59 0.46
5 1 57 4802 10.12 4.41 0.48
5 5 285 4941 15.71 7.72 0.55
5 10 569 5124 22.69 11.85 0.64
5 20 1139 5484 36.67 20.11 0.83
5 30 1709 5848 50.65 28.38 1.02
5 40 2276 6200 64.63 36.65 1.21
5 50 2848 6561 78.62 44.92 1.40
5 65 3702 7105 99.62 57.34 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 2023-07-28 18:45:36.113992758 UTC

3-nodes Scenario

A rather typical setup, with 3 nodes forming a Hydra head.

Number of nodes 3
Number of txs 900
Avg. Confirmation Time (ms) 146.599817185
P99 275.04050635999994ms
P95 217.54940029999995ms
P50 137.4571185ms
Number of Invalid txs 0

Baseline Scenario

This scenario represents a minimal case and as such is a good baseline against which to assess the overhead introduced by more complex setups. There is a single hydra-node d with a single client submitting single input and single output transactions with a constant UTxO set of 1.

Number of nodes 1
Number of txs 300
Avg. Confirmation Time (ms) 9.954522250
P99 21.029815079999988ms
P95 17.645915100000003ms
P50 8.6086665ms
Number of Invalid txs 0

This is a patch release ahead of previously 9.2.7 and promises better
support for newer linux kernels.
@github-actions
Copy link

github-actions bot commented Jul 28, 2023

Test Results

350 tests  ±0   345 ✔️ ±0   23m 43s ⏱️ + 4m 38s
117 suites ±0       5 💤 ±0 
    6 files   ±0       0 ±0 

Results for commit e7f3515. ± Comparison against base commit 52dac61.

♻️ This comment has been updated with latest results.

CHANGELOG.md Show resolved Hide resolved
@abailly-iohk abailly-iohk merged commit ac83344 into master Jul 31, 2023
32 checks passed
@abailly-iohk abailly-iohk deleted the ch1bo/ghc-9.2.8 branch July 31, 2023 06:40
@ch1bo ch1bo added this to the 0.12.0 milestone Aug 18, 2023
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.

3 participants