Skip to content

Conversation

@locallycompact
Copy link
Contributor

No description provided.

@locallycompact locallycompact requested a review from noonio November 4, 2025 14:46
@github-actions
Copy link

github-actions bot commented Nov 4, 2025

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 2025-11-04 15:48:22.085542061 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial c8a101a5c8ac4816b0dceb59ce31fc2258e387de828f02961d2f2045 2652
νCommit 61458bc2f297fff3cc5df6ac7ab57cefd87763b0b7bd722146a1035c 685
νHead a1442faf26d4ec409e2f62a685c1d4893f8d6bcbaf7bcb59d6fa1340 14599
μHead fd173b993e12103cd734ca6710d364e17120a5eb37a224c64ab2b188* 5284
νDeposit ae01dade3a9c346d5c93ae3ce339412b90a0b8f83f94ec6baa24e30c 1102
  • 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 5834 10.59 3.36 0.52
2 6035 12.99 4.13 0.55
3 6236 14.31 4.52 0.57
5 6646 18.60 5.87 0.64
10 7646 28.71 9.03 0.78
43 14279 98.56 30.79 1.80

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 561 2.44 1.16 0.20
2 743 3.38 1.73 0.22
3 917 4.36 2.33 0.24
5 1277 6.41 3.60 0.28
10 2179 12.13 7.25 0.40
54 10076 98.61 68.52 1.88

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 525 24.42 7.12 0.42
2 114 636 33.33 9.64 0.52
3 170 751 42.23 12.15 0.61
4 226 858 48.89 14.13 0.68
5 283 969 59.87 17.21 0.80
6 339 1085 72.47 20.54 0.93
7 394 1192 77.87 22.27 0.99
8 448 1303 94.51 26.75 1.16

Cost of Increment Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 1797 23.92 7.60 0.48
2 2001 26.50 8.99 0.52
3 2055 26.94 9.77 0.53
5 2426 32.19 12.57 0.61
10 3104 40.70 18.28 0.75
44 7948 99.26 57.23 1.71

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 635 22.84 7.38 0.42
2 767 23.62 8.25 0.43
3 853 24.07 9.03 0.45
5 1230 29.58 11.93 0.53
10 1985 39.79 18.09 0.69
41 6752 98.90 55.20 1.64

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 648 29.13 8.90 0.48
2 778 30.98 10.08 0.51
3 993 33.32 11.42 0.55
5 1254 36.99 13.77 0.60
10 2085 48.52 20.39 0.78
36 5966 96.39 51.16 1.56

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 629 33.15 9.95 0.52
2 857 36.52 11.59 0.57
3 1004 38.63 12.83 0.60
5 1330 43.36 15.49 0.67
10 2183 56.31 22.49 0.86
30 5029 99.34 47.76 1.52

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 5817 26.92 9.04 0.69
2 5960 35.79 12.03 0.79
3 6014 43.79 14.65 0.87
4 6167 50.05 16.77 0.95
5 6381 62.74 21.15 1.09
6 6368 67.71 22.61 1.14
7 6721 80.72 27.19 1.29
8 7004 92.92 31.39 1.44
9 6950 96.91 32.50 1.47

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 1 57 5869 20.34 6.91 0.62
10 5 285 6004 28.02 9.98 0.71
10 10 570 6174 39.25 14.36 0.84
10 20 1137 6511 60.17 22.59 1.09
10 30 1708 6854 80.48 30.61 1.32
10 38 2164 7126 96.88 37.08 1.51

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 2025-11-04 15:53:53.781337376 UTC

Baseline Scenario

Number of nodes 1
Number of txs 300
Avg. Confirmation Time (ms) 9.212086390
P99 45.65324267999952ms
P95 10.503199700000003ms
P50 5.3196270000000005ms
Number of Invalid txs 0

Memory data

Time Used Free
2025-11-04 15:52:25.893724854 UTC 1349M 6668M
2025-11-04 15:52:26.893629819 UTC 1349M 6668M
2025-11-04 15:52:27.893633897 UTC 1362M 6654M
2025-11-04 15:52:28.893507931 UTC 1394M 6622M
2025-11-04 15:52:29.89351066 UTC 1431M 6557M
2025-11-04 15:52:30.893465385 UTC 1433M 6554M
2025-11-04 15:52:31.893486047 UTC 1453M 6531M
2025-11-04 15:52:32.893650854 UTC 1445M 6536M
2025-11-04 15:52:33.893536356 UTC 1424M 6558M
2025-11-04 15:52:34.893504379 UTC 1440M 6540M
2025-11-04 15:52:35.893528488 UTC 1440M 6540M
2025-11-04 15:52:36.89353154 UTC 1440M 6540M
2025-11-04 15:52:37.893547695 UTC 1440M 6540M
2025-11-04 15:52:38.893508147 UTC 1440M 6540M
2025-11-04 15:52:39.89359527 UTC 1440M 6540M
2025-11-04 15:52:40.893511363 UTC 1440M 6540M
2025-11-04 15:52:41.893523358 UTC 1440M 6540M
2025-11-04 15:52:42.893517898 UTC 1440M 6540M
2025-11-04 15:52:43.893611028 UTC 1440M 6539M
2025-11-04 15:52:44.893500704 UTC 1440M 6539M
2025-11-04 15:52:45.893557152 UTC 1440M 6539M
2025-11-04 15:52:46.893576003 UTC 1440M 6539M
2025-11-04 15:52:47.893530052 UTC 1442M 6537M
2025-11-04 15:52:48.893560369 UTC 1442M 6537M
2025-11-04 15:52:49.893583846 UTC 1442M 6537M
2025-11-04 15:52:50.893496702 UTC 1442M 6536M
2025-11-04 15:52:51.893522375 UTC 1442M 6536M
2025-11-04 15:52:52.893530104 UTC 1442M 6536M
2025-11-04 15:52:53.893494068 UTC 1442M 6536M
2025-11-04 15:52:54.893509875 UTC 1442M 6536M

Three local nodes

Number of nodes 3
Number of txs 900
Avg. Confirmation Time (ms) 42.870114681
P99 74.39940458000001ms
P95 65.48405515ms
P50 40.055741ms
Number of Invalid txs 0

Memory data

Time Used Free
2025-11-04 15:53:06.60147958 UTC 1347M 6670M
2025-11-04 15:53:07.601453792 UTC 1347M 6670M
2025-11-04 15:53:08.60142249 UTC 1358M 6659M
2025-11-04 15:53:09.601497725 UTC 1362M 6655M
2025-11-04 15:53:10.601446715 UTC 1362M 6654M
2025-11-04 15:53:11.601461041 UTC 1363M 6654M
2025-11-04 15:53:12.6014193 UTC 1363M 6653M
2025-11-04 15:53:13.601424419 UTC 1420M 6568M
2025-11-04 15:53:14.601361461 UTC 1482M 6477M
2025-11-04 15:53:15.601459162 UTC 1550M 6381M
2025-11-04 15:53:16.601466745 UTC 1594M 6336M
2025-11-04 15:53:17.602334961 UTC 1607M 6323M
2025-11-04 15:53:18.601660519 UTC 1642M 6280M
2025-11-04 15:53:19.604453079 UTC 1650M 6262M
2025-11-04 15:53:20.603455142 UTC 1663M 6238M
2025-11-04 15:53:21.603832258 UTC 1683M 6209M
2025-11-04 15:53:22.602490333 UTC 1683M 6202M
2025-11-04 15:53:23.601604556 UTC 1688M 6191M
2025-11-04 15:53:24.601443358 UTC 1708M 6165M
2025-11-04 15:53:25.604297612 UTC 1710M 6156M
2025-11-04 15:53:26.602987853 UTC 1732M 6127M
2025-11-04 15:53:27.60230834 UTC 1732M 6120M
2025-11-04 15:53:28.601625468 UTC 1744M 6100M
2025-11-04 15:53:29.605548658 UTC 1746M 6090M
2025-11-04 15:53:30.601400844 UTC 1759M 6066M
2025-11-04 15:53:31.601512581 UTC 1758M 6065M
2025-11-04 15:53:32.601369732 UTC 1759M 6064M
2025-11-04 15:53:33.60140178 UTC 1768M 6055M
2025-11-04 15:53:34.601467738 UTC 1765M 6057M
2025-11-04 15:53:35.601457488 UTC 1763M 6059M
2025-11-04 15:53:36.601432234 UTC 1763M 6059M
2025-11-04 15:53:37.601339368 UTC 1763M 6059M
2025-11-04 15:53:38.601360098 UTC 1764M 6058M
2025-11-04 15:53:39.601372056 UTC 1765M 6057M
2025-11-04 15:53:40.601428853 UTC 1765M 6057M
2025-11-04 15:53:41.601422383 UTC 1765M 6057M
2025-11-04 15:53:42.601425934 UTC 1764M 6057M
2025-11-04 15:53:43.601396254 UTC 1765M 6056M
2025-11-04 15:53:44.601454095 UTC 1765M 6056M
2025-11-04 15:53:45.601415589 UTC 1765M 6055M
2025-11-04 15:53:46.601365692 UTC 1766M 6055M
2025-11-04 15:53:47.601366362 UTC 1765M 6055M
2025-11-04 15:53:48.601416823 UTC 1765M 6055M
2025-11-04 15:53:49.601506596 UTC 1765M 6054M
2025-11-04 15:53:50.601418401 UTC 1765M 6054M
2025-11-04 15:53:51.601506747 UTC 1766M 6054M
2025-11-04 15:53:52.601357607 UTC 1765M 6054M
2025-11-04 15:53:53.601464304 UTC 1766M 6053M

@noonio
Copy link
Contributor

noonio commented Nov 4, 2025

Looks interesting but doesn't work:

image

@locallycompact locallycompact force-pushed the lc/cachix-push branch 2 times, most recently from c07c34c to 1b21332 Compare November 4, 2025 15:45
@locallycompact
Copy link
Contributor Author

@noonio Fixed.

@noonio
Copy link
Contributor

noonio commented Nov 5, 2025

no luck

image

@noonio
Copy link
Contributor

noonio commented Nov 11, 2025

I'm open-minded to this as a step to get us back to bringing nix flake check back; but as-is it doesn't work; it basically builds too much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants