Update networking page

[noonio]

This is a short writeup of the findings; added to the "networking" page as an investigation.

I think a broader re-write of the page is in order, but can come separately, as it's a bit more work to document all the existing knowledge and implementation details.

Note also that I took the liberty to update the version of Docusaurus. Edit: Nope, not doing this now, as it requires too many changes.

Locally, it gives only some additional warnings; nothing errors and it seems to render the same. The main reason for this change is that the new Docusaurus version has a more up-to-date mermaidjs implementation that allows for nicer diagrams, such as this one, a block-beta style:

block-beta
    columns 3
    space alice space
    space:3
    bob space carol
    
    alice --> bob
    bob   --> alice

    carol --> alice
    alice --> carol
    
    bob --> carol
    carol --> bob

Loading

Compare that to the exact same diagram in a normal mermaid "graph":

graph
    alice --> bob
    bob   --> alice

    carol --> alice
    alice --> carol
    
    bob --> carol
    carol --> bob

Loading

[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-09-09 11:06:37.184626429 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	2ee477c60839936be49a50030690865b5bed4db8cd2f05bf255ac680	10068
μHead	a1610f6e64843161f4a88229c0286176f5325de3e2f773eec2b1d818*	4508
νDeposit	c2117fd9ebdee3e96b81fd67ff7092d638926415c10f1f7e5a267ad0	2791

• 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	5097	5.61	2.21	0.44
2	5297	7.18	2.84	0.46
3	5498	8.56	3.39	0.49
5	5901	11.17	4.41	0.53
10	6907	18.30	7.24	0.65
57	16353	82.81	32.75	1.77

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO	Tx size	% max Mem	% max CPU	Min fee ₳
1	569	10.52	4.15	0.29
2	757	13.86	5.65	0.34
3	939	17.33	7.20	0.38
5	1323	24.65	10.44	0.48
10	2257	45.22	19.36	0.75
20	4124	95.99	40.76	1.40

CollectCom transaction costs

Parties	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	57	560	21.46	8.41	0.41
2	114	671	32.21	12.78	0.53
3	169	782	47.31	18.89	0.70
4	227	893	57.89	23.43	0.83
5	281	1004	77.20	31.31	1.04
6	338	1116	96.13	39.18	1.26

Cost of Decrement Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	632	17.66	7.77	0.38
2	764	19.01	9.03	0.40
3	954	20.62	10.31	0.43
5	1230	23.52	12.90	0.49
10	1970	31.72	19.73	0.64
50	7980	97.87	74.66	1.83

Close transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	658	20.03	8.99	0.41
2	783	21.53	10.41	0.43
3	925	22.92	11.79	0.46
5	1320	26.64	15.28	0.53
10	1989	34.08	22.49	0.68
50	8084	98.95	83.97	1.91

Contest transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	668	25.89	11.13	0.47
2	810	27.65	12.63	0.50
3	948	29.38	14.13	0.53
5	1266	33.44	17.54	0.60
10	2056	43.54	26.17	0.78
40	6603	99.26	74.24	1.78

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	4894	13.94	5.82	0.52
2	5177	29.41	12.97	0.71
3	5233	41.50	18.30	0.85
4	5317	53.06	23.33	0.98
5	5657	80.22	35.84	1.31
6	5690	94.10	41.86	1.46

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	4934	8.09	3.42	0.46
5	1	57	4968	8.83	3.96	0.47
5	5	284	5103	13.55	6.89	0.53
5	10	569	5274	19.40	10.54	0.62
5	20	1138	5612	30.13	17.40	0.77
5	30	1708	5955	42.04	24.77	0.93
5	40	2279	6296	52.98	31.73	1.08
5	50	2845	6631	64.11	38.78	1.24
5	81	4609	7682	99.67	61.07	1.73

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-09-09 11:09:01.41076675 UTC

Baseline Scenario

Number of nodes	1
Number of txs	3000
Avg. Confirmation Time (ms)	4.034639856
P99	10.566171299999954ms
P95	4.75379ms
P50	3.803088ms
Number of Invalid txs	0

Three local nodes

Number of nodes	3
Number of txs	9000
Avg. Confirmation Time (ms)	23.547095904
P99	118.03701054000001ms
P95	32.57831069999999ms
P50	20.4823015ms
Number of Invalid txs	0

[github-actions]

Test Results

488 tests  ±0   483 ✅ ±0   22m 28s ⏱️ + 2m 2s
153 suites ±0     5 💤 ±0 
  6 files   ±0     0 ❌ ±0 

Results for commit 782f02b. ± Comparison against base commit c4baec6.

♻️ This comment has been updated with latest results.