Generate non-ada UTxO in the fanout property tests

[vrom911]

The fanout generator only ever produced ada-only outputs, so the property tests never covered outputs carrying native tokens or datums. Parameterize genStOpen on the in-head UTxO generator and have genFanoutTx draw a mix of ada-only and arbitrary outputs.

Output value and datum size is what the on-chain accumulator hashing spends its budget on, so the arbitrary branch is capped: uncapped, a fanout of a few outputs each carrying ~100 assets overspends execution memory (14.3M against the 14M limit). Steps stay at ~82%, so memory is the binding constraint, and it scales with per-output size rather than output count - hence the cap on the size parameter, not the count

---

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

[github-actions]

Transaction cost differences

No cost or size differences found

[github-actions]

End-to-end benchmark differences

Comparing d0cb782 (PR) against merge-base 0928801. Each runner measures both sides; every delta is the median over the same-machine pairs. Colored rows exceed the per-metric noise threshold with directional agreement (a calibrated heuristic, not a significance test); ≈ is within noise; uncolored rows are context. 🟢 = improvement, 🔴 = regression.

Round-trip latency (3 nodes, closed-loop, 3x250 txs)

Metric	master	PR	Δ
End-to-end TPS (tx/s)	158.57	158.07	≈ +0.6%
Sustained TPS, slope (tx/s)	159.97	160.90	≈ +0.3%
Backlog drain time (s)	0.01	0.01	🟢 -22.7%
Snapshots per second (/s)	108.25	107.28	≈ -0.0%
Avg txs per snapshot	1.46	1.47	≈ +0.6%
Avg. Confirmation Time (s)	0.019	0.019	≈ -0.3%
P50 confirmation (s)	0.018	0.018	≈ -1.1%
P95 confirmation (s)	0.024	0.024	≈ -0.2%
Tx validation time p50 (s)	0.005	0.005	≈ +0.9%
Alloc MB per confirmed tx	4.13	4.12	≈ -0.2%
Alloc MB per snapshot	6.04	6.08	≈ +0.6%
Mutator CPU s per 1k txs	14.63	14.63	≈ -0.6%
Max live MB (max node)	16.36	16.35	≈ +0.0%
Peak node RSS (MB)	126.92	126.88	≈ +0.1%
Invalid txs	0.00	0.00	≈ +0.0

Sustained load (3 nodes, 3x5000 txs)

Metric	master	PR	Δ
End-to-end TPS (tx/s)	717.28	722.59	≈ +0.7%
Sustained TPS, slope (tx/s)	1,167.15	1,195.66	≈ -2.0%
Backlog drain time (s)	20.35	20.05	≈ -0.4%
Snapshots per second (/s)	0.79	0.77	≈ -0.9%
Avg txs per snapshot	909.93	937.50	≈ +3.1%
Tx validation time p50 (s)	5.243	5.514	≈ +6.6%
Alloc MB per confirmed tx	3.91	3.83	≈ -1.5%
Alloc MB per snapshot	3,561.30	3,573.60	≈ +1.4%
Mutator CPU s per 1k txs	3.86	3.79	≈ -0.8%
Max live MB (max node)	81.78	81.07	≈ -0.9%
Peak node RSS (MB)	337.13	332.11	≈ -0.1%
Invalid txs	0.00	0.00	≈ +0.0

Plateau 1000 UTxO (1 node, 4000 txs)

Metric	master	PR	Δ
End-to-end TPS (tx/s)	601.72	641.73	≈ +8.6%
Sustained TPS, slope (tx/s)	674.27	621.85	≈ -9.8% (3/4 pairs)
Backlog drain time (s)	6.58	6.17	≈ -7.8%
Snapshots per second (/s)	1.57	2.41	+63.6%
Avg txs per snapshot	403.85	266.67	-34.4%
Tx validation time p50 (s)	2.874	3.004	≈ +4.5%
Alloc MB per confirmed tx	3.16	3.04	≈ -3.6%
Alloc MB per snapshot	1,278.91	809.83	-36.5%
Mutator CPU s per 1k txs	2.07	2.00	≈ -1.7%
Max live MB (max node)	25.92	20.85	🟢 -22.5%
Peak node RSS (MB)	161.28	151.09	≈ -6.1%
Invalid txs	0.00	0.00	≈ +0.0

---

• bench-results-m1: AMD EPYC 9V74 80-Core Processor (4 vCPU, 16 GB)
• bench-results-m2: AMD EPYC 9V74 80-Core Processor (4 vCPU, 16 GB)
• bench-results-m3: AMD EPYC 9V74 80-Core Processor (4 vCPU, 16 GB)
• bench-results-m4: AMD EPYC 7763 64-Core Processor (4 vCPU, 16 GB)
• Same-code spread across runners (End-to-end TPS), the noise an unpaired comparison would see:
  • Round-trip latency (3 nodes, closed-loop, 3x250 txs): branch 10.7%, master 9.7%
  • Sustained load (3 nodes, 3x5000 txs): branch 11.6%, master 10.5%
  • Plateau 1000 UTxO (1 node, 4000 txs): branch 6.1%, master 11.1%

Per-run raw values

Machine	Slot	Side	Scenario	E2E TPS	Outcome
bench-results-m1	1	branch	Round-trip latency (3 nodes, closed-loop, 3x250 txs)	152.56	ok
bench-results-m1	1	branch	Sustained load (3 nodes, 3x5000 txs)	731.22	ok
bench-results-m1	1	branch	Plateau 1000 UTxO (1 node, 4000 txs)	653.37	ok
bench-results-m1	2	master	Round-trip latency (3 nodes, closed-loop, 3x250 txs)	157.04	ok
bench-results-m1	2	master	Sustained load (3 nodes, 3x5000 txs)	700.92	ok
bench-results-m1	2	master	Plateau 1000 UTxO (1 node, 4000 txs)	592.68	ok
bench-results-m2	1	master	Round-trip latency (3 nodes, closed-loop, 3x250 txs)	151.12	ok
bench-results-m2	1	master	Sustained load (3 nodes, 3x5000 txs)	735.81	ok
bench-results-m2	1	master	Plateau 1000 UTxO (1 node, 4000 txs)	625.97	ok
bench-results-m2	2	branch	Round-trip latency (3 nodes, closed-loop, 3x250 txs)	157.34	ok
bench-results-m2	2	branch	Sustained load (3 nodes, 3x5000 txs)	713.96	ok
bench-results-m2	2	branch	Plateau 1000 UTxO (1 node, 4000 txs)	616.01	ok
bench-results-m3	1	branch	Round-trip latency (3 nodes, closed-loop, 3x250 txs)	158.81	ok
bench-results-m3	1	branch	Sustained load (3 nodes, 3x5000 txs)	743.54	ok
bench-results-m3	1	branch	Plateau 1000 UTxO (1 node, 4000 txs)	653.48	ok
bench-results-m3	2	master	Round-trip latency (3 nodes, closed-loop, 3x250 txs)	160.10	ok
bench-results-m3	2	master	Sustained load (3 nodes, 3x5000 txs)	733.63	ok
bench-results-m3	2	master	Plateau 1000 UTxO (1 node, 4000 txs)	610.76	ok
bench-results-m4	1	master	Round-trip latency (3 nodes, closed-loop, 3x250 txs)	165.72	ok
bench-results-m4	1	master	Sustained load (3 nodes, 3x5000 txs)	666.07	ok
bench-results-m4	1	master	Plateau 1000 UTxO (1 node, 4000 txs)	563.66	ok
bench-results-m4	2	branch	Round-trip latency (3 nodes, closed-loop, 3x250 txs)	168.94	ok
bench-results-m4	2	branch	Sustained load (3 nodes, 3x5000 txs)	666.22	ok
bench-results-m4	2	branch	Plateau 1000 UTxO (1 node, 4000 txs)	630.09	ok

Workflow run

[github-actions]

Transaction costs

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	2026-09-01 17:03:09.662456723 UTC
Max. memory units	14000000
Max. CPU units	10000000000
Max. tx size (kB)	16384

Script summary

Name	Hash	Size (Bytes)
νHead	1d511733200df551c8cd8cddb3160ed39087af815638be37a1b80ffd	12962
μHead	603f261bc5a01f5f4ed988cc07a40a130b94e6820c28e9affde82d9e*	4971
νDeposit	eafae2c32f99ab347c7bb15961e0e84c74305f9088c1a7b8abf88e7f	2117
νCRS	09db7ee6cf7a4b358dd5c8a2f19d2c048336ffc5a01ef35a47ca7072	2736

• 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	5476	9.55	3.14	0.50
2	5572	10.04	3.30	0.51
3	5667	10.32	3.38	0.51
5	5861	11.62	3.80	0.53
10	6345	14.12	4.60	0.58
50	10183	35.18	11.16	0.97
100	14982	62.30	19.66	1.46
114	16326	70.07	22.08	1.60

Cost of Increment Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	2823	20.88	7.49	0.70
2	2954	21.85	8.46	0.72
3	3086	23.43	9.64	0.74
5	3348	24.71	11.37	0.78
10	4001	29.82	16.33	0.88
50	9245	72.22	56.25	1.75
75	12523	96.85	80.64	2.26

Cost of Decrement Transaction

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	642	18.50	6.69	0.58
2	777	19.47	7.67	0.60
3	909	20.46	8.65	0.62
5	1171	22.37	10.59	0.66
10	1822	27.16	15.44	0.76
50	7063	68.20	54.92	1.61
75	10338	93.60	79.53	2.13

Close transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	670	17.75	11.66	0.61
2	800	18.71	12.63	0.63
3	931	19.70	13.61	0.65
5	1194	21.70	15.58	0.69
10	1853	26.61	20.49	0.79
75	10365	93.63	84.88	2.17

Contest transaction costs

Parties	Tx size	% max Mem	% max CPU	Min fee ₳
1	701	21.47	14.90	0.66
2	832	22.61	15.93	0.68
3	964	23.78	16.96	0.71
5	1226	26.00	19.00	0.75
10	1885	31.82	24.17	0.86
50	7121	79.38	65.69	1.78
67	9345	99.78	83.38	2.17

FanOut transaction costs

Involves spending head output and burning head tokens. Uses ada-only UTXO for better comparability.
Rows first grow the UTxO set at a fixed 10 parties, then show the largest set that still fits per number of parties (burning more participation tokens leaves less room for outputs).

Parties	UTxO	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
10	0	0	5644	23.70	43.00	1.14
10	1	57	5678	26.05	45.51	1.18
10	5	285	5815	36.28	55.83	1.34
10	10	570	5984	50.26	69.12	1.56
10	20	1139	6323	82.76	97.10	2.04
1	20	1137	6042	76.54	95.13	1.96
5	20	1135	6164	79.31	96.00	1.99
10	20	1139	6324	82.76	97.10	2.04
20	20	1137	6632	90.08	99.38	2.13
50	15	854	7394	95.05	92.01	2.15

PartialFanOut transaction costs

Largest chunk of ada-only outputs that can be distributed in one partial fanout step, computed dynamically. The last row is the maximum total UTxO count where at least one output can still be distributed.

Total UTxO	Distributed	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
11	10	569	986	35.29	66.46	1.20
25	23	1305	1424	68.58	99.53	1.73
30	23	1308	1427	68.58	99.53	1.73
40	23	1308	1427	68.58	99.53	1.73
50	23	1308	1427	68.58	99.53	1.73
100	23	1309	1428	68.58	99.53	1.73
150	23	1310	1429	68.58	99.53	1.73
200	23	1312	1431	68.58	99.53	1.73
200	23	1306	1425	68.58	99.53	1.73

PartialFanOut transaction costs (with native tokens)

Largest chunk of native-token outputs that can be distributed in one partial fanout step, computed dynamically. The last row is the maximum total UTxO count where at least one output can still be distributed.

Total UTxO	Distributed	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
11	10	1040	1521	42.27	68.96	1.30
25	21	2436	2698	76.69	99.30	1.84
30	21	2583	2852	76.71	99.35	1.85
40	21	2184	2434	76.71	99.25	1.83
50	21	2037	2281	76.69	99.20	1.83
100	21	2142	2391	76.71	99.25	1.83
150	21	2184	2435	76.71	99.25	1.83
200	21	2289	2545	76.69	99.25	1.84
200	21	2268	2523	76.71	99.25	1.84

FinalPartialFanOut transaction costs (with native tokens)

Terminal partial fanout step (FanoutProgress → Final) with outputs carrying a native token. Burns all head tokens and proves accumulator exhaustion via BLS proof.

Distributed	UTxO (bytes)	Tx size	% max Mem	% max CPU	Min fee ₳
1	104	5524	22.51	44.43	1.14
5	580	5915	35.93	55.93	1.34
10	1230	6460	54.18	70.78	1.62
10	1190	6421	54.18	70.78	1.62

End-to-end benchmark results

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 2026-09-01 17:01:20.75485874 UTC

Baseline Scenario

Number of nodes	1
Number of txs	300
Load mode	open-loop
Avg. Confirmation Time (ms)	194.9
P99	197.1ms
P95	197.0ms
P50	195.1ms
Tx validation time p50 (ms)	124.6
End-to-end TPS	1481.33 tx/s
Backlog drain time (s)	0.2
Snapshots observed	3
Snapshots per second	14.81 /s
Avg txs per snapshot	100.0
Peak node RSS (MB)	142.5
Number of Invalid txs	0
Fanout outputs	2

Three local nodes

Number of nodes	3
Number of txs	900
Load mode	open-loop
Avg. Confirmation Time (ms)	940.0
P99	981.0ms
P95	979.9ms
P50	954.4ms
Tx validation time p50 (ms)	451.8
End-to-end TPS	909.56 tx/s
Backlog drain time (s)	0.9
Snapshots observed	3
Snapshots per second	3.03 /s
Avg txs per snapshot	300.0
Peak node RSS (MB)	145.9
Number of Invalid txs	0
Fanout outputs	4

Scenario benchmark results

Scenario benchmark results

This page collects results from the scenario matrix: every combination of cluster size, UTxO shape, and incremental-ops mode is exercised by CI from the latest master code and reported below.

Numbers are approximate. They come from cloud VMs rather than controlled hardware, so the useful signal is the relative change between cells and between commits, not the absolute throughput.

Generated at 2026-09-01 17:13:15.143767301 UTC

Summary across cells

TPS columns are rates (transactions per second); Wall clock (s) is the measured elapsed time from the first tx submission to the last confirmation. Times are rounded to one decimal.

Scenario	Txs	Wall clock (s)	End-to-end TPS (tx/s)	Sustained TPS (tx/s)	Avg conf (ms)	P95 conf (ms)
Nodes=1, Constant, fire and forget	30	0.0	1046.87	n/a	27.7	28.4
Nodes=1, Constant, wait for tx valid	30	0.2	158.90	156.13	6.1	7.9
Nodes=1, Growing, fire and forget	30	0.0	935.99	n/a	30.9	31.7
Nodes=1, Growing, wait for tx valid	30	0.2	162.23	163.26	6.1	7.8
Nodes=1, Mixed, fire and forget	30	0.0	978.03	n/a	29.8	30.4
Nodes=1, Mixed, wait for tx valid	30	0.2	173.79	168.31	5.7	7.1
Nodes=2, Constant, fire and forget	60	0.1	938.95	n/a	61.7	63.6
Nodes=2, Constant, wait for tx valid	60	0.4	141.31	142.91	14.0	17.5
Nodes=2, Growing, fire and forget	60	0.1	829.59	n/a	70.6	71.3
Nodes=2, Growing, wait for tx valid	60	0.6	102.82	101.87	19.2	23.3
Nodes=2, Mixed, fire and forget	60	0.1	896.21	n/a	64.7	66.6
Nodes=2, Mixed, wait for tx valid	60	0.6	105.56	102.59	18.8	23.5
Nodes=3, Constant, fire and forget	90	0.1	723.72	n/a	119.7	122.3
Nodes=3, Constant, wait for tx valid	90	0.8	113.00	112.04	26.0	33.6
Nodes=3, Growing, fire and forget	90	0.1	646.17	n/a	133.1	138.8
Nodes=3, Growing, wait for tx valid	90	1.0	87.00	85.51	33.9	43.2
Nodes=3, Mixed, fire and forget	90	0.1	742.41	n/a	118.0	120.8
Nodes=3, Mixed, wait for tx valid	90	0.9	97.58	93.83	30.2	39.9

Nodes=1, Constant, fire and forget

Number of nodes	1
Number of txs	30
Load mode	open-loop
Avg. Confirmation Time (ms)	27.7
P99	28.4ms
P95	28.4ms
P50	27.8ms
Tx validation time p50 (ms)	10.4
End-to-end TPS	1046.87 tx/s
Backlog drain time (s)	0.0
Snapshots observed	2
Snapshots per second	69.79 /s
Avg txs per snapshot	15.0
Peak node RSS (MB)	130.0
Number of Invalid txs	0
Fanout outputs	2

Nodes=1, Constant, wait for tx valid

Number of nodes	1
Number of txs	30
Load mode	closed-loop
Avg. Confirmation Time (ms)	6.1
P99	12.6ms
P95	7.9ms
P50	5.8ms
Tx validation time p50 (ms)	2.2
End-to-end TPS	158.90 tx/s
Sustained TPS	156.13 tx/s
Backlog drain time (s)	0.0
Snapshots observed	30
Snapshots per second	158.90 /s
Avg txs per snapshot	1.0
Peak node RSS (MB)	142.7
Number of Invalid txs	0
Fanout outputs	2

Nodes=1, Growing, fire and forget

Number of nodes	1
Number of txs	30
Load mode	open-loop
Avg. Confirmation Time (ms)	30.9
P99	31.8ms
P95	31.7ms
P50	31.2ms
Tx validation time p50 (ms)	12.0
End-to-end TPS	935.99 tx/s
Backlog drain time (s)	0.0
Snapshots observed	2
Snapshots per second	62.40 /s
Avg txs per snapshot	15.0
Peak node RSS (MB)	131.2
Number of Invalid txs	0
Fanout outputs	31

Nodes=1, Growing, wait for tx valid

Number of nodes	1
Number of txs	30
Load mode	closed-loop
Avg. Confirmation Time (ms)	6.1
P99	8.5ms
P95	7.8ms
P50	6.0ms
Tx validation time p50 (ms)	1.7
End-to-end TPS	162.23 tx/s
Sustained TPS	163.26 tx/s
Backlog drain time (s)	0.0
Snapshots observed	30
Snapshots per second	162.23 /s
Avg txs per snapshot	1.0
Peak node RSS (MB)	144.4
Number of Invalid txs	0
Fanout outputs	31

Nodes=1, Mixed, fire and forget

Each client first grows its UTxO set (1-in to 2-out) for half of its tx budget, then contracts it back (2-in to 1-out) for the remainder.

Number of nodes	1
Number of txs	30
Load mode	open-loop
Avg. Confirmation Time (ms)	29.8
P99	30.4ms
P95	30.4ms
P50	30.0ms
Tx validation time p50 (ms)	12.3
End-to-end TPS	978.03 tx/s
Backlog drain time (s)	0.0
Snapshots observed	2
Snapshots per second	65.20 /s
Avg txs per snapshot	15.0
Peak node RSS (MB)	123.9
Number of Invalid txs	0
Fanout outputs	2

Nodes=1, Mixed, wait for tx valid

Each client first grows its UTxO set (1-in to 2-out) for half of its tx budget, then contracts it back (2-in to 1-out) for the remainder.

Number of nodes	1
Number of txs	30
Load mode	closed-loop
Avg. Confirmation Time (ms)	5.7
P99	11.2ms
P95	7.1ms
P50	5.3ms
Tx validation time p50 (ms)	1.7
End-to-end TPS	173.79 tx/s
Sustained TPS	168.31 tx/s
Backlog drain time (s)	0.0
Snapshots observed	30
Snapshots per second	173.79 /s
Avg txs per snapshot	1.0
Peak node RSS (MB)	143.0
Number of Invalid txs	0
Fanout outputs	2

Nodes=2, Constant, fire and forget

Number of nodes	2
Number of txs	60
Load mode	open-loop
Avg. Confirmation Time (ms)	61.7
P99	63.7ms
P95	63.6ms
P50	62.2ms
Tx validation time p50 (ms)	29.4
End-to-end TPS	938.95 tx/s
Backlog drain time (s)	0.1
Snapshots observed	2
Snapshots per second	31.30 /s
Avg txs per snapshot	30.0
Peak node RSS (MB)	144.9
Number of Invalid txs	0
Fanout outputs	3

Nodes=2, Constant, wait for tx valid

Number of nodes	2
Number of txs	60
Load mode	closed-loop
Avg. Confirmation Time (ms)	14.0
P99	18.9ms
P95	17.5ms
P50	13.6ms
Tx validation time p50 (ms)	4.1
End-to-end TPS	141.31 tx/s
Sustained TPS	142.91 tx/s
Backlog drain time (s)	0.0
Snapshots observed	60
Snapshots per second	141.31 /s
Avg txs per snapshot	1.0
Peak node RSS (MB)	145.0
Number of Invalid txs	0
Fanout outputs	3

Nodes=2, Growing, fire and forget

Number of nodes	2
Number of txs	60
Load mode	open-loop
Avg. Confirmation Time (ms)	70.6
P99	71.4ms
P95	71.3ms
P50	70.9ms
Tx validation time p50 (ms)	25.3
End-to-end TPS	829.59 tx/s
Backlog drain time (s)	0.1
Snapshots observed	2
Snapshots per second	27.65 /s
Avg txs per snapshot	30.0
Peak node RSS (MB)	143.9
Number of Invalid txs	0
Fanout outputs	62

Nodes=2, Growing, wait for tx valid

Number of nodes	2
Number of txs	60
Load mode	closed-loop
Avg. Confirmation Time (ms)	19.2
P99	26.9ms
P95	23.3ms
P50	19.2ms
Tx validation time p50 (ms)	5.8
End-to-end TPS	102.82 tx/s
Sustained TPS	101.87 tx/s
Backlog drain time (s)	0.0
Snapshots observed	60
Snapshots per second	102.82 /s
Avg txs per snapshot	1.0
Peak node RSS (MB)	145.7
Number of Invalid txs	0
Fanout outputs	62

Nodes=2, Mixed, fire and forget

Each client first grows its UTxO set (1-in to 2-out) for half of its tx budget, then contracts it back (2-in to 1-out) for the remainder.

Number of nodes	2
Number of txs	60
Load mode	open-loop
Avg. Confirmation Time (ms)	64.7
P99	66.7ms
P95	66.6ms
P50	65.1ms
Tx validation time p50 (ms)	23.9
End-to-end TPS	896.21 tx/s
Backlog drain time (s)	0.1
Snapshots observed	2
Snapshots per second	29.87 /s
Avg txs per snapshot	30.0
Peak node RSS (MB)	143.6
Number of Invalid txs	0
Fanout outputs	3

Nodes=2, Mixed, wait for tx valid

Each client first grows its UTxO set (1-in to 2-out) for half of its tx budget, then contracts it back (2-in to 1-out) for the remainder.

Number of nodes	2
Number of txs	60
Load mode	closed-loop
Avg. Confirmation Time (ms)	18.8
P99	26.1ms
P95	23.5ms
P50	18.5ms
Tx validation time p50 (ms)	6.3
End-to-end TPS	105.56 tx/s
Sustained TPS	102.59 tx/s
Backlog drain time (s)	0.0
Snapshots observed	60
Snapshots per second	105.56 /s
Avg txs per snapshot	1.0
Peak node RSS (MB)	145.4
Number of Invalid txs	0
Fanout outputs	3

Nodes=3, Constant, fire and forget

Number of nodes	3
Number of txs	90
Load mode	open-loop
Avg. Confirmation Time (ms)	119.7
P99	122.6ms
P95	122.3ms
P50	120.3ms
Tx validation time p50 (ms)	71.5
End-to-end TPS	723.72 tx/s
Backlog drain time (s)	0.1
Snapshots observed	2
Snapshots per second	16.08 /s
Avg txs per snapshot	45.0
Peak node RSS (MB)	144.6
Number of Invalid txs	0
Fanout outputs	4

Nodes=3, Constant, wait for tx valid

Number of nodes	3
Number of txs	90
Load mode	closed-loop
Avg. Confirmation Time (ms)	26.0
P99	37.4ms
P95	33.6ms
P50	25.6ms
Tx validation time p50 (ms)	7.1
End-to-end TPS	113.00 tx/s
Sustained TPS	112.04 tx/s
Backlog drain time (s)	0.0
Snapshots observed	61
Snapshots per second	76.59 /s
Avg txs per snapshot	1.5
Peak node RSS (MB)	145.1
Number of Invalid txs	0
Fanout outputs	4

Nodes=3, Growing, fire and forget

Number of nodes	3
Number of txs	90
Load mode	open-loop
Avg. Confirmation Time (ms)	133.1
P99	139.0ms
P95	138.8ms
P50	131.9ms
Tx validation time p50 (ms)	55.4
End-to-end TPS	646.17 tx/s
Backlog drain time (s)	0.1
Snapshots observed	2
Snapshots per second	14.36 /s
Avg txs per snapshot	45.0
Peak node RSS (MB)	145.2
Number of Invalid txs	0
Fanout outputs	0

Nodes=3, Growing, wait for tx valid

Number of nodes	3
Number of txs	90
Load mode	closed-loop
Avg. Confirmation Time (ms)	33.9
P99	45.0ms
P95	43.2ms
P50	34.1ms
Tx validation time p50 (ms)	9.6
End-to-end TPS	87.00 tx/s
Sustained TPS	85.51 tx/s
Backlog drain time (s)	0.0
Snapshots observed	61
Snapshots per second	58.97 /s
Avg txs per snapshot	1.5
Peak node RSS (MB)	146.0
Number of Invalid txs	0
Fanout outputs	0

Nodes=3, Mixed, fire and forget

Each client first grows its UTxO set (1-in to 2-out) for half of its tx budget, then contracts it back (2-in to 1-out) for the remainder.

Number of nodes	3
Number of txs	90
Load mode	open-loop
Avg. Confirmation Time (ms)	118.0
P99	120.9ms
P95	120.8ms
P50	118.3ms
Tx validation time p50 (ms)	63.3
End-to-end TPS	742.41 tx/s
Backlog drain time (s)	0.1
Snapshots observed	2
Snapshots per second	16.50 /s
Avg txs per snapshot	45.0
Peak node RSS (MB)	145.1
Number of Invalid txs	0
Fanout outputs	4

Nodes=3, Mixed, wait for tx valid

Each client first grows its UTxO set (1-in to 2-out) for half of its tx budget, then contracts it back (2-in to 1-out) for the remainder.

Number of nodes	3
Number of txs	90
Load mode	closed-loop
Avg. Confirmation Time (ms)	30.2
P99	44.2ms
P95	39.9ms
P50	29.4ms
Tx validation time p50 (ms)	8.5
End-to-end TPS	97.58 tx/s
Sustained TPS	93.83 tx/s
Backlog drain time (s)	0.0
Snapshots observed	61
Snapshots per second	66.14 /s
Avg txs per snapshot	1.5
Peak node RSS (MB)	144.6
Number of Invalid txs	0
Fanout outputs	4