cardano-node: 8.7.2

[locallycompact]

Required for Conway Support #1177

[github-actions]

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-12-13 12:35:30.788143702 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	4372	10.63	4.11	0.46
2	4576	12.68	4.88	0.49
3	4776	14.68	5.63	0.52
5	5177	19.22	7.35	0.59
10	6184	30.45	11.62	0.75
41	12415	99.06	37.61	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	720	15.04	6.07	0.35
3	912	18.85	7.75	0.40
5	1282	26.90	11.27	0.51
10	2216	49.55	20.97	0.80
19	3904	99.43	41.75	1.43

Cost of CollectCom Transaction

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	57	480	21.78	8.51	0.41
2	114	594	33.20	13.10	0.54
3	168	700	44.90	17.91	0.67
4	228	810	60.07	24.09	0.84
5	281	920	79.24	31.85	1.06

Cost of Close Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	536	16.72	7.69	0.36
2	720	18.40	9.28	0.40
3	924	20.35	10.99	0.43
5	1179	22.99	13.54	0.49
10	2116	32.11	21.95	0.66
50	9221	99.84	84.61	1.97

Cost of Contest Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	583	20.18	8.95	0.40
2	739	22.17	10.64	0.44
3	932	24.32	12.42	0.48
5	1246	27.80	15.45	0.54
10	2186	37.58	23.96	0.72
43	7825	99.64	77.57	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	4223	15.19	6.26	0.50
2	4478	31.84	13.87	0.70
3	4647	47.73	20.94	0.89
4	4814	66.06	29.08	1.11
5	4845	73.37	31.97	1.19

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	4206	8.05	3.37	0.42
5	1	57	4239	9.28	4.13	0.44
5	5	285	4376	14.19	7.18	0.51
5	10	570	4545	20.43	11.03	0.59
5	20	1135	4880	32.85	18.71	0.77
5	30	1709	5226	45.15	26.34	0.93
5	40	2278	5565	57.21	33.87	1.10
5	50	2845	5902	69.56	41.52	1.27
5	74	4216	6721	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 2023-12-13 12:40:17.929966862 UTC

Baseline Scenario

Number of nodes	3
Number of txs	9000
Avg. Confirmation Time (ms)	24.170942549
P99	52.45226841000002ms
P95	32.696467399999996ms
P50	22.320318999999998ms
Number of Invalid txs	0

Baseline Scenario

Number of nodes	1
Number of txs	3000
Avg. Confirmation Time (ms)	5.142526315
P99	10.787973849999988ms
P95	8.506483249999999ms
P50	4.603914ms
Number of Invalid txs	0

[github-actions]

Test Results

377 tests  ±0   372 ✔️ ±0   22m 4s ⏱️ - 1m 4s
128 suites ±0       5 💤 ±0 
    5 files   ±0       0 ❌ ±0 

Results for commit dda772a. ± Comparison against base commit b7c618c.

♻️ This comment has been updated with latest results.

[ch1bo]

Please update the CHANGELOG as we do require a different cardano-node version now (and should write that into the next release notes)

Also, do not just strip off the PR checklist.. it should have reminded you of that fact.

[ch1bo]

Not going to fight over a changelog entry.