Docs: use Mithril client one line installer in tutorial

[jpraynaud]

This PR includes the usage of the one-line Mithril client installer in the tutorial page of the documentation website: this will allow to download the latest version of the Mithril client and removes the burden of keeping track of the correct Mithril distribution to use.

---

• Documentation updated

[github-actions]

Transaction cost differences

Script summary

Name	Size (Bytes)
νInitial	-
νCommit	-
νHead	-
μHead	-
νDeposit	-

Init transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	-	-	-	-
2	-	-	-	-
3	-	-	-	-
5	-	-	-	-
10	-	-	-	-
44	-	-	-	-

Commit transaction costs

UTxO	Tx size	% max Mem	% max CPU	Min fee ₳
1	-	-	-	-
2	-	-	-	-
3	-	-	-	-
5	-	-	-	-
10	-	-	-	-
54	-	-	-	-

CollectCom transaction costs

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	-	-	-	-	-
2	-	-	-	-	-
3	-	-	-	-	-
4	-	-	-	-	-
5	-	-	-	-	-
6	-	-	-	-	-
7	-	-	-	-	-
8	-	-	-	-	-
10	-	-	-	-	-

Cost of Increment Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	-	-	-	-
2	-	-	-	-
3	-	-	-	-
5	-	-	-	-
10	-	-	-	-
43	-	+0.39	+0.09	-

Cost of Decrement Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	-	-	-	-
2	-	-	-	-
3	-	-	-	-
5	-	-	-	-
10	-	-	-	-
45	-	-	-	-

Close transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	-	-	-	-
2	-	-	-	-
3	-	-	-	-
5	-	-	-	-
10	-	-	-	-
41	-	-	-	-

Contest transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	-	-	-	-
2	-	-	-	-
3	-	-	-	-
5	-	-	-	-
10	-	-	-	-
33	-	-	-	-

FanOut transaction costs

UTxO, Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
(0, 10)	-	-	-	-	-
(1, 10)	-	-	-	-	-
(5, 10)	-	-	-	-	-
(10, 10)	-	-	-	-	-
(20, 10)	-	-	-	-	-
(40, 10)	-	-	-	-	-
(41, 10)	-	-	-	-	-

[github-actions]

Transaction 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	2025-01-06 10:59:42.002700399 UTC
Max. memory units	14000000
Max. CPU units	10000000000
Max. tx size (kB)	16384

Script summary

Name	Hash	Size (Bytes)
νInitial	00a6ddbc130ab92f5b7cb8d1ccd8d79eca5bfe25f6843c07b62841f0	2667
νCommit	3e5a776bcee213e3dfd15806952a10ac5590e3e97d09d62eb99266b2	690
νHead	5350e9d521552ebfd9e846fd70c3b801f716fc14296134ec0fb71e97	14495
μHead	482c3ce15cde05bc905b915ccfa2546e500be1c5d722389026c37aa3*	5615
νDeposit	de09cec5f84eedaf64186cb52ba4ee6e74e6fc368af25b90d457f352	1118

• The minting policy hash is only usable for comparison. As the script is parameterized, the actual script is unique per head.

Init transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	6164	10.00	3.17	0.53
2	6367	12.67	4.05	0.56
3	6566	14.24	4.52	0.59
5	6966	18.19	5.75	0.65
10	7974	28.74	9.08	0.80
44	14810	98.28	30.94	1.82

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO	Tx size	% max Mem	% max CPU	Min fee ₳
1	561	2.45	1.17	0.20
2	742	3.40	1.74	0.22
3	921	4.39	2.34	0.24
5	1274	6.46	3.61	0.28
10	2180	12.24	7.28	0.40
54	10077	99.20	68.72	1.89

CollectCom transaction costs

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	57	525	25.00	7.26	0.43
2	114	636	33.14	9.62	0.52
3	169	747	43.54	12.47	0.62
4	227	858	52.31	15.00	0.72
5	284	969	60.82	17.44	0.81
6	338	1081	69.89	20.05	0.91
7	397	1192	78.28	22.43	1.00
8	451	1303	86.77	24.85	1.09
9	505	1414	94.03	27.11	1.17

Cost of Increment Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	1830	23.75	7.94	0.48
2	1941	25.60	9.16	0.51
3	2079	27.08	10.29	0.53
5	2334	30.02	12.56	0.59
10	3303	42.75	20.31	0.79
42	7761	92.81	57.95	1.66

Cost of Decrement Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	589	22.68	7.31	0.41
2	696	22.47	7.90	0.42
3	882	24.92	9.26	0.46
5	1237	29.74	11.95	0.53
10	1957	38.25	17.66	0.67
41	6685	95.87	54.50	1.61

Close transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	682	26.99	8.72	0.46
2	849	30.91	10.65	0.51
3	1005	30.74	11.35	0.52
5	1276	33.97	13.70	0.58
10	1865	41.62	19.33	0.71
39	6427	98.45	58.00	1.65

Contest transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	671	33.31	10.41	0.52
2	875	35.90	11.97	0.57
3	1008	37.94	13.27	0.60
5	1309	42.03	15.92	0.66
10	2004	52.62	22.64	0.83
32	5406	99.55	52.74	1.57

Abort transaction costs

There is some variation due to the random mixture of initial and already committed outputs.

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	6043	26.05	8.82	0.69
2	6245	35.76	12.15	0.80
3	6286	43.17	14.59	0.88
4	6460	49.90	16.88	0.96
5	6678	63.67	21.67	1.11
6	6765	72.75	24.73	1.21
7	6993	81.73	27.85	1.32
8	7036	87.72	29.76	1.38
9	6977	91.10	30.75	1.41

FanOut transaction costs

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 ₳
10	5	285	6332	28.18	10.22	0.73
10	10	570	6502	38.34	14.29	0.85
10	20	1139	6841	56.83	21.77	1.07
10	30	1708	7183	76.06	29.51	1.29
10	42	2390	7588	99.21	38.84	1.57

End-to-end benchmark results

This page is intended to collect the latest end-to-end benchmark results produced by Hydra's continuous integration (CI) system from the latest master code.

Please note that these results are approximate as they are currently produced from limited cloud VMs and not controlled hardware. Rather than focusing on the absolute results, the emphasis should be on relative results, such as how the timings for a scenario evolve as the code changes.

Generated at 2025-01-06 11:02:37.639307077 UTC

Baseline Scenario

Number of nodes	1
Number of txs	300
Avg. Confirmation Time (ms)	4.888212240
P99	13.224471469999992ms
P95	6.712943750000003ms
P50	4.571156ms
Number of Invalid txs	0

Three local nodes

Number of nodes	3
Number of txs	900
Avg. Confirmation Time (ms)	22.756931368
P99	36.775265919999995ms
P95	29.802509699999998ms
P50	21.1818405ms
Number of Invalid txs	0

[github-actions]

Test Results

  5 files  ±0  165 suites  ±0   32m 48s ⏱️ + 2m 3s
563 tests ±0  557 ✅ ±0  6 💤 ±0  0 ❌ ±0 
565 runs  ±0  559 ✅ ±0  6 💤 ±0  0 ❌ ±0 

Results for commit 2d2a0e7. ± Comparison against base commit e0dc991.

[locallycompact]

This makes sense I think.