Docs: use our original violet again

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	2024-08-15 14:01:23.857180341 UTC
Max. memory units	14000000
Max. CPU units	10000000000
Max. tx size (kB)	16384

Script summary

Name	Hash	Size (Bytes)
νInitial	2fac819a1f4f14e29639d1414220d2a18b6abd6b8e444d88d0dda8ff	3799
νCommit	2043a9f1a685bcf491413a5f139ee42e335157c8c6bc8d9e4018669d	1743
νHead	bd9fad235c871fb7f837c767593018a84be3083ff80f9dab5f1c55f9	10194
μHead	c8038945816586c4d38926ee63bba67821eb863794220ebbd0bf79ee*	4607

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	5188	5.61	2.21	0.44
2	5390	6.99	2.76	0.46
3	5590	8.56	3.39	0.49
5	5993	11.22	4.43	0.54
10	6998	18.02	7.12	0.66
56	16248	81.63	32.29	1.76

`Commit` transaction costs

This uses ada-only outputs for better comparability.

UTxO	Tx size	% max Mem	% max CPU	Min fee ₳
1	559	10.52	4.15	0.29
2	745	13.86	5.65	0.34
3	933	17.33	7.20	0.38
5	1309	24.65	10.44	0.48
10	2237	45.22	19.36	0.75
20	4117	95.99	40.76	1.40

`CollectCom` transaction costs

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	57	549	22.14	8.66	0.42
2	113	659	33.93	13.42	0.55
3	169	769	44.03	17.66	0.67
4	227	879	57.80	23.40	0.82
5	283	989	75.46	30.69	1.02
6	340	1100	94.68	38.65	1.24

Cost of Decrement Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	645	17.93	7.88	0.38
2	834	20.38	9.55	0.42
3	960	21.33	10.65	0.44
5	1168	22.77	12.62	0.48
10	2086	35.13	21.08	0.68
48	7687	98.39	73.40	1.81

`Close` transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	651	20.98	9.39	0.42
2	789	22.41	10.80	0.44
3	943	23.92	12.22	0.47
5	1213	27.27	15.34	0.53
10	2013	35.39	23.06	0.69
49	8141	98.97	83.78	1.91

`Contest` transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	674	27.14	11.66	0.48
2	868	29.40	13.55	0.52
3	1003	31.17	15.06	0.55
5	1317	34.97	18.37	0.62
10	2030	44.28	26.27	0.79
38	6281	96.89	71.59	1.73

`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	5051	17.32	7.53	0.57
2	5177	28.58	12.52	0.70
3	5281	37.68	16.48	0.81
4	5481	58.51	25.93	1.05
5	5653	78.03	34.71	1.28
6	5614	88.46	39.19	1.39

`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 ₳
5	0	0	5022	7.95	3.36	0.46
5	1	57	5056	8.88	3.99	0.47
5	5	283	5191	13.41	6.84	0.54
5	10	568	5360	19.06	10.39	0.62
5	20	1140	5703	30.19	17.43	0.77
5	30	1705	6040	41.51	24.55	0.93
5	40	2276	6380	53.23	31.84	1.09
5	50	2845	6719	64.17	38.80	1.24
5	81	4612	7774	99.53	61.01	1.74

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 2024-08-15 14:03:51.372166157 UTC

Baseline Scenario

Number of nodes	1
Number of txs	3000
Avg. Confirmation Time (ms)	4.998735267
P99	11.820923339999952ms
P95	5.486143299999998ms
P50	4.137276ms
Number of Invalid txs	0

Three local nodes

Number of nodes	3
Number of txs	9000
Avg. Confirmation Time (ms)	23.056417477
P99	106.63517390000004ms
P95	32.32069334999999ms
P50	20.697295ms
Number of Invalid txs	0

cardano-scaling / hydra