*DO NOT MERGE* Doom hotfixes

[noonio]

• Memory leak hotfix ( see DONT MERGE: Not leak memory #1572 )
• Persistence hotfix ( see NOT MERGE: Less reliable persistence prototype #1495 )

Note that this will never be merged; it's merely an attempt to get a "fastest-possible" estimate for writing something, and not crashing with too much memory.

Instead of this PR, we will:

• Use a different persistence backend
• Actually address memory issues Event Log Rotation and Memory Growth #1581

[github-actions]

Transaction cost differences

No cost or size differences found

[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	2024-11-21 16:22:44.408930665 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	8fc2a74df32d01d1db56b3acb561831ef9c9970123079423abfcb86e	12622
μHead	c40e78e78083a4c137734abe9ac4070cc978842e9755fe88e0c7b922*	11133
νDeposit	2feb47889a4f658dc593cefcb0e37d584b9431944f08a687f3dab4af	4865

• 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	11719	8.94	2.92	0.76
2	11919	10.94	3.58	0.79
3	12119	12.53	4.09	0.81
5	12522	15.90	5.18	0.87
10	13528	24.86	8.09	1.00
24	16341	49.68	16.17	1.39

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO	Tx size	% max Mem	% max CPU	Min fee ₳
1	558	2.45	1.17	0.20
2	738	3.40	1.74	0.22
3	923	4.39	2.34	0.24
5	1280	6.46	3.61	0.28
10	2179	12.24	7.28	0.40
54	10062	99.20	68.72	1.89

CollectCom transaction costs

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	57	560	24.08	7.04	0.42
2	114	671	33.71	9.73	0.52
3	170	782	40.39	11.72	0.60
4	226	893	51.69	14.84	0.71
5	281	1004	60.12	17.25	0.80
6	337	1116	63.03	18.34	0.84
7	392	1227	77.10	22.11	0.99
8	449	1342	83.76	24.24	1.06
9	507	1449	95.42	27.45	1.18

Cost of Decrement Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	628	22.35	7.24	0.41
2	852	25.21	8.69	0.45
3	918	25.22	9.38	0.46
5	1120	26.74	11.10	0.50
10	1993	39.34	17.98	0.69
40	6831	99.57	54.93	1.65

Close transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	606	23.82	7.74	0.43
2	775	25.99	9.19	0.46
3	1011	28.03	10.63	0.50
5	1258	31.03	12.91	0.55
10	2024	40.00	19.35	0.70
43	7091	99.50	61.67	1.71

Contest transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	714	30.47	9.65	0.50
2	840	32.36	10.90	0.53
3	992	34.62	12.37	0.56
5	1325	38.84	15.12	0.63
10	2047	48.90	21.71	0.79
34	5626	98.14	53.69	1.58

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	11600	25.67	8.73	0.93
2	11669	30.85	10.45	0.99
3	11918	43.10	14.73	1.13
4	12052	52.54	17.99	1.23
5	12140	59.81	20.43	1.31
6	12230	69.26	23.54	1.42
7	12453	76.43	26.04	1.50
8	12419	84.47	28.67	1.59
9	12732	95.64	32.65	1.72

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	0	0	11714	17.86	6.13	0.85
10	1	57	11748	19.92	6.96	0.88
10	5	285	11884	27.33	10.01	0.97
10	10	570	12055	35.49	13.42	1.06
10	20	1139	12394	54.38	21.17	1.29
10	30	1707	12733	73.79	29.11	1.52
10	40	2278	13074	92.90	36.94	1.74
10	44	2504	13208	99.22	39.59	1.82

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-11-21 16:26:17.436448242 UTC

Baseline Scenario

Number of nodes	1
Number of txs	300
Avg. Confirmation Time (ms)	1.659291423
P99	2.3659402ms
P95	2.0507759500000002ms
P50	1.607994ms
Number of Invalid txs	0

Three local nodes

Number of nodes	3
Number of txs	900
Avg. Confirmation Time (ms)	44.274605558
P99	216.03407653ms
P95	121.22297174999999ms
P50	19.3894885ms
Number of Invalid txs	0