Use max of start-chain-from and last known point

[ch1bo]

Instead of using the oldest, use the newest point when both, a last known head state and start-chain-from is present.

---

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

[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-06-17 09:56:13.881838083 UTC
Max. memory units	14000000
Max. CPU units	10000000000
Max. tx size (kB)	16384

Script summary

Name	Hash	Size (Bytes)
νInitial	baafeb5dc37bbe6e068784746bda0a3b1bb1d034fa0c55270f6079c1	4082
νCommit	fe7af84822bcba542fae377ae7311fc5fd20152f925ccd980f73ecdc	2061
νHead	93c08c55e804d7f82ca545a01883b5fda6a6d3623cb78885625800ae	9366
μHead	5e65c73722b4bb3f0cbfcc8433e1dcdfea099eaf0a43060f1731a65b*	4237

• 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	4818	5.83	2.29	0.43
2	5017	7.19	2.82	0.45
3	5218	8.59	3.37	0.47
5	5621	11.77	4.64	0.53
10	6629	18.61	7.33	0.65
58	16276	85.71	33.78	1.80

Cost of Commit Transaction

This is using ada-only outputs for better comparability.

UTxO	Tx size	% max Mem	% max CPU	Min fee ₳
1	559	9.69	3.82	0.28
2	746	12.48	5.10	0.32
3	937	15.33	6.40	0.36
5	1308	21.26	9.09	0.45
10	2246	37.35	16.27	0.67
25	5060	96.42	41.75	1.45

Cost of CollectCom Transaction

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	57	544	14.78	5.90	0.34
2	114	654	23.23	9.39	0.43
3	171	764	33.22	13.55	0.55
4	227	874	44.43	18.29	0.68
5	280	984	59.17	24.41	0.85
6	339	1095	74.64	30.92	1.02
7	394	1205	89.70	37.39	1.20

Cost of Close Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	599	8.22	4.57	0.28
2	684	8.52	5.30	0.29
3	949	10.07	7.06	0.32
5	1243	11.84	9.50	0.37
10	2011	16.16	15.47	0.48
50	8069	49.52	62.69	1.36

Cost of Contest Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	637	8.64	4.74	0.28
2	776	9.33	5.80	0.30
3	902	10.06	6.87	0.32
5	1191	12.00	9.35	0.37
10	2127	17.75	16.44	0.51
50	8160	51.48	63.73	1.38

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	4711	16.91	7.33	0.55
2	4766	26.89	11.65	0.66
3	4879	39.85	17.38	0.81
4	5037	49.64	21.57	0.93
5	5165	71.21	31.20	1.18
6	5399	98.25	43.29	1.49

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	4651	7.82	3.27	0.44
5	1	56	4685	8.97	3.98	0.46
5	5	285	4821	14.00	7.01	0.53
5	10	569	4990	19.34	10.39	0.60
5	20	1137	5328	31.08	17.61	0.76
5	30	1710	5674	42.40	24.66	0.92
5	40	2275	6008	54.35	31.97	1.08
5	50	2843	6347	65.26	38.85	1.24
5	79	4499	7335	98.97	59.67	1.70

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-06-17 09:59:27.128047527 UTC

Baseline Scenario

Number of nodes	1
Number of txs	3000
Avg. Confirmation Time (ms)	4.499051774
P99	8.292489489999983ms
P95	5.925406749999999ms
P50	4.274025ms
Number of Invalid txs	0

Three local nodes

Number of nodes	3
Number of txs	9000
Avg. Confirmation Time (ms)	22.097035163
P99	103.9465729000001ms
P95	30.32060084999999ms
P50	19.804612499999998ms
Number of Invalid txs	0

[github-actions]

Test Results

437 tests  ±0   425 ✅ ±0   14m 19s ⏱️ -59s
143 suites ±0    12 💤 ±0 
  5 files   ±0     0 ❌ ±0 

Results for commit 3281f07. ± Comparison against base commit 4fed462.