Test hydra-cluster on all networks

[locallycompact]

---

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

[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	2024-03-19 12:33:18.004486502 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	4798	8.93	3.42	0.46
2	4999	10.70	4.09	0.49
3	5197	12.83	4.92	0.52
5	5599	16.43	6.29	0.57
10	6605	26.31	10.09	0.73
48	14245	99.96	38.36	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	594	10.24	4.04	0.29
2	784	13.88	5.64	0.34
3	968	17.66	7.29	0.39
5	1348	25.66	10.74	0.49
10	2283	48.19	20.30	0.79
19	3965	97.83	40.79	1.41

Cost of CollectCom Transaction

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	57	544	16.52	6.53	0.35
2	113	654	26.34	10.52	0.47
3	170	764	38.09	15.32	0.60
4	226	874	53.34	21.55	0.77
5	283	984	65.28	26.64	0.91
6	336	1095	81.88	33.56	1.10

Cost of Close Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	596	8.29	4.59	0.28
2	726	9.00	5.65	0.30
3	892	9.70	6.74	0.32
5	1257	11.93	9.54	0.37
10	1978	15.82	15.23	0.47
50	7822	50.05	62.37	1.35

Cost of Contest Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	623	8.65	4.73	0.28
2	715	8.93	5.45	0.29
3	846	9.70	6.54	0.31
5	1207	11.93	9.33	0.37
10	1978	16.25	15.31	0.48
50	7884	50.25	62.46	1.35

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	4585	13.89	5.75	0.51
2	4738	26.81	11.61	0.66
3	4922	40.77	17.86	0.83
4	5215	60.81	26.86	1.06
5	5203	76.15	33.48	1.24

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.06	3.37	0.44
5	1	57	4661	9.42	4.17	0.46
5	5	284	4796	13.82	6.93	0.52
5	10	570	4967	19.58	10.49	0.60
5	20	1139	5306	30.90	17.53	0.76
5	30	1706	5645	42.43	24.67	0.92
5	40	2276	5986	54.17	31.89	1.08
5	50	2847	6326	65.50	38.95	1.24
5	80	4549	7338	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-03-19 12:35:36.13784272 UTC

Baseline Scenario

Number of nodes	3
Number of txs	9000
Avg. Confirmation Time (ms)	22.668298577
P99	100.1243080100001ms
P95	31.530504949999997ms
P50	20.0285685ms
Number of Invalid txs	0

Baseline Scenario

Number of nodes	1
Number of txs	3000
Avg. Confirmation Time (ms)	4.333661217
P99	9.229883709999998ms
P95	6.148644399999996ms
P50	4.055981ms
Number of Invalid txs	0

[github-actions]

Test Results

425 tests  +2   418 ✅ +3   13m 45s ⏱️ +8s
138 suites ±0     7 💤  - 1 
  5 files   ±0     0 ❌ ±0 

Results for commit 9de3443. ± Comparison against base commit 89f8fb5.

This pull request removes 2 and adds 4 tests. Note that renamed tests count towards both.

Test.CardanoNode ‑ withCardanoNodeOnKnownNetwork on mainnet starts synchronizing within 5 seconds
Test.CardanoNode ‑ withCardanoNodeOnKnownNetwork on sanchonet starts synchronizing within 5 seconds

Test.CardanoNode ‑ withCardanoNodeOnKnownNetwork starts synchronizing within 10 seconds (Mainnet)
Test.CardanoNode ‑ withCardanoNodeOnKnownNetwork starts synchronizing within 10 seconds (Preproduction)
Test.CardanoNode ‑ withCardanoNodeOnKnownNetwork starts synchronizing within 10 seconds (Preview)
Test.CardanoNode ‑ withCardanoNodeOnKnownNetwork starts synchronizing within 10 seconds (Sanchonet)

♻️ This comment has been updated with latest results.

[ch1bo]

Does the full smoke test work on preview?

[ffakenz]

It's unclear to me why are we doing this.

Anyhow, wdyt about running the test against multiple networks? ... its just 5 seconds!

[ch1bo]

It's unclear to me why are we doing this.

Anyhow, wdyt about running the test against multiple networks? ... its just 5 seconds!

Good idea. There is even a forEachKnownNetwork helper already.

[ch1bo]

Left also a comment on duplicated code.