Skip to content

Conversation

@noonio
Copy link
Contributor

@noonio noonio commented Jun 24, 2025

@github-actions
Copy link

github-actions bot commented Jun 24, 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-06-26 15:17:01.762564991 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 be6ebc744208c660bf0fdc1cfbb5157477cd305de5b1777e575cbb4c 14665
μHead 1f47a42d1d6edc32ccd834acb19d5db3b2a5232f0bd7eaa8908dc519* 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 5836 10.35 3.28 0.51
2 6037 12.41 3.92 0.54
3 6238 14.64 4.63 0.58
5 6641 18.80 5.94 0.64
10 7647 29.44 9.29 0.79
43 14281 98.53 30.78 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 737 3.38 1.73 0.22
3 920 4.36 2.33 0.24
5 1283 6.41 3.60 0.28
10 2174 12.13 7.25 0.40
54 10059 98.61 68.52 1.88

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 56 528 25.20 7.30 0.43
2 114 636 34.23 9.85 0.53
3 171 751 41.36 11.94 0.60
4 226 858 51.16 14.70 0.71
5 282 969 56.37 16.37 0.77
6 337 1085 67.49 19.39 0.88
7 394 1192 82.91 23.53 1.04
8 451 1303 85.79 24.72 1.08

Cost of Increment Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 1802 23.78 7.94 0.48
2 1882 24.66 8.79 0.50
3 2059 26.85 10.23 0.53
5 2441 31.91 13.29 0.61
10 3228 41.31 19.75 0.77
42 7986 99.01 59.91 1.73

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 609 22.46 7.26 0.41
2 726 23.51 8.19 0.43
3 957 27.03 9.86 0.48
5 1219 30.06 12.02 0.53
10 1953 38.49 17.71 0.67
41 6548 98.32 55.03 1.63

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 677 29.00 9.25 0.48
2 827 29.03 9.99 0.49
3 963 30.77 11.20 0.52
5 1312 35.36 14.16 0.60
10 2083 48.30 21.70 0.79
37 6158 98.07 56.12 1.62

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 670 33.66 10.49 0.53
2 810 35.77 11.79 0.56
3 993 38.33 13.35 0.60
5 1392 43.47 16.47 0.68
10 2037 54.05 23.04 0.84
30 4862 96.45 49.56 1.50

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 5774 26.97 9.03 0.69
2 5950 36.69 12.33 0.80
3 6025 44.60 14.91 0.88
4 6115 50.27 16.77 0.95
5 6305 64.17 21.47 1.10
6 6425 72.36 24.24 1.19
7 6581 79.03 26.51 1.27
8 6680 91.97 30.90 1.41
9 6898 99.83 33.68 1.50

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 5868 20.78 7.06 0.63
10 5 284 6003 28.92 10.28 0.72
10 10 569 6174 38.64 14.15 0.84
10 30 1708 6855 79.64 30.32 1.31
10 39 2221 7160 99.44 38.05 1.54

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-06-26 15:20:11.634391966 UTC

Baseline Scenario

Number of nodes 1
Number of txs 300
Avg. Confirmation Time (ms) 4.301284086
P99 8.372218339999982ms
P95 5.10982245ms
P50 4.1360885ms
Number of Invalid txs 0

Memory data

Time Used Free
2025-06-26 15:18:50.293485802 UTC 0m 0;
2025-06-26 15:18:55.293304283 UTC 2 0;
2025-06-26 15:19:00.293406963 UTC 7 0;
2025-06-26 15:19:05.293397529 UTC 1 0;
2025-06-26 15:19:10.293378679 UTC 1 0;
2025-06-26 15:19:15.293409427 UTC 1 0;

Three local nodes

Number of nodes 3
Number of txs 900
Avg. Confirmation Time (ms) 34.947646282
P99 73.29900472ms
P95 60.44702249999999ms
P50 31.0532125ms
Number of Invalid txs 0

Memory data

Time Used Free
2025-06-26 15:19:28.599612384 UTC 0m 0;
2025-06-26 15:19:33.599618511 UTC 2 0;
2025-06-26 15:19:38.600630539 UTC 4 0;
2025-06-26 15:19:43.601292982 UTC 20 0;
2025-06-26 15:19:48.599696683 UTC 15 0;
2025-06-26 15:19:53.599622867 UTC 5 0;
2025-06-26 15:19:58.599722445 UTC 2 0;
2025-06-26 15:20:03.599710882 UTC 2 0;
2025-06-26 15:20:08.599621006 UTC 2 0;

@github-actions
Copy link

Transaction cost differences

No cost or size differences found

@noonio noonio force-pushed the 0.22-stalled-investigation branch from d42b1dd to 7c8d145 Compare June 25, 2025 09:51
@ch1bo ch1bo force-pushed the 0.22-stalled-investigation branch from 7c8d145 to ef6da6e Compare June 25, 2025 10:34
@ch1bo ch1bo force-pushed the 0.22-stalled-investigation branch from ef6da6e to 5b21269 Compare June 25, 2025 10:37
@noonio noonio mentioned this pull request Jun 25, 2025
@noonio noonio linked an issue Jun 25, 2025 that may be closed by this pull request
@ffakenz ffakenz force-pushed the 0.22-stalled-investigation branch from d3610e9 to 9aec0d7 Compare June 26, 2025 14:19
@noonio noonio force-pushed the 0.22-stalled-investigation branch from 15a2bb7 to 5358e31 Compare June 26, 2025 14:58
@noonio
Copy link
Contributor Author

noonio commented Jun 27, 2025

Closing, as we've moved on to #2088 .

But I'll leave the branch/commits here, so we can look back over it for a while until we fix #2086 .

@noonio noonio closed this Jun 27, 2025
@github-project-automation github-project-automation bot moved this from Triage 🏥 to Done ✔ in ☕ Hydra Team Work Jun 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done ✔

Development

Successfully merging this pull request may close these issues.

Deadlock in logging

2 participants