Skip to content

cardano-api: 10.17 #2061

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from
Draft

cardano-api: 10.17 #2061

wants to merge 3 commits into from

Conversation

locallycompact
Copy link
Contributor

No description provided.

@locallycompact locallycompact force-pushed the capi-10.17 branch 10 times, most recently from 8d124ff to 4a0dccd Compare June 16, 2025 10:47
@locallycompact locallycompact marked this pull request as draft June 18, 2025 09:42
@locallycompact locallycompact force-pushed the capi-10.17 branch 13 times, most recently from d6d74f1 to 3e92092 Compare July 4, 2025 14:08
Copy link

github-actions bot commented Jul 4, 2025

Transaction cost differences

No cost or size differences found

@locallycompact
Copy link
Contributor Author

@locallycompact locallycompact force-pushed the capi-10.17 branch 2 times, most recently from 070ef3d to 12187af Compare July 12, 2025 13:22
Copy link

github-actions bot commented Jul 12, 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-07-15 08:50:58.829012946 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 11.04 3.52 0.52
2 6038 12.92 4.11 0.55
3 6239 14.86 4.71 0.58
5 6638 18.84 5.95 0.64
10 7646 28.92 9.11 0.79
43 14281 98.97 30.93 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 923 4.36 2.33 0.24
5 1275 6.41 3.60 0.28
10 2173 12.13 7.25 0.40
54 10061 98.61 68.52 1.88

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 525 24.46 7.13 0.42
2 113 636 33.41 9.68 0.52
3 170 747 42.61 12.28 0.62
4 227 858 47.80 13.87 0.67
5 282 969 61.90 17.66 0.82
6 338 1085 73.68 20.91 0.94
7 394 1196 72.86 21.16 0.94
8 451 1307 98.26 27.50 1.20

Cost of Increment Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 1794 24.24 8.05 0.48
2 1920 25.77 9.19 0.51
3 2127 28.17 10.70 0.55
5 2406 32.19 13.35 0.61
10 3250 42.35 20.13 0.78
41 7854 99.81 59.52 1.73

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 629 22.82 7.37 0.42
2 743 23.62 8.24 0.43
3 952 26.13 9.62 0.47
5 1286 30.00 12.03 0.54
10 1938 38.12 17.65 0.67
40 6540 98.75 54.48 1.63

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 680 27.37 8.80 0.46
2 792 30.83 10.47 0.51
3 1038 31.48 11.53 0.53
5 1181 36.09 14.10 0.60
10 2077 47.49 21.38 0.78
36 5996 96.30 54.84 1.59

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 678 33.73 10.50 0.53
2 764 35.10 11.49 0.55
3 899 37.07 12.75 0.58
5 1292 42.28 15.89 0.66
10 1981 52.99 22.58 0.83
29 5062 98.82 50.25 1.53

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 5698 22.97 7.58 0.64
2 5897 34.96 11.72 0.78
3 6068 42.70 14.33 0.87
4 6265 54.58 18.38 1.00
5 6459 64.80 21.87 1.12
6 6608 74.36 25.08 1.22
7 6658 80.31 27.07 1.29
8 7036 94.66 32.01 1.46
9 6916 93.89 31.60 1.44

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 0 0 5834 19.19 6.41 0.61
10 5 285 6004 28.47 10.13 0.72
10 10 570 6174 38.20 14.00 0.83
10 30 1708 6855 80.09 30.47 1.32
10 37 2103 7088 94.45 36.13 1.49

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-07-15 08:53:45.72933129 UTC

Baseline Scenario

Number of nodes 1
Number of txs 300
Avg. Confirmation Time (ms) 4.588738840
P99 7.840551149999988ms
P95 5.510568350000001ms
P50 4.364052ms
Number of Invalid txs 0

Memory data

Time Used Free
2025-07-15 08:52:24.101339214 UTC 0m 0;
2025-07-15 08:52:29.101301256 UTC 5 0;
2025-07-15 08:52:34.101387105 UTC 7 0;
2025-07-15 08:52:39.101348212 UTC 1 0;
2025-07-15 08:52:44.101265329 UTC 1 0;
2025-07-15 08:52:49.101388426 UTC 1 0;

Three local nodes

Number of nodes 3
Number of txs 900
Avg. Confirmation Time (ms) 35.803381731
P99 70.95126454999999ms
P95 58.158298349999995ms
P50 32.838794ms
Number of Invalid txs 0

Memory data

Time Used Free
2025-07-15 08:53:02.802807755 UTC 0m 0;
2025-07-15 08:53:07.80313162 UTC 4 0;
2025-07-15 08:53:12.804575023 UTC 4 0;
2025-07-15 08:53:17.804755964 UTC 20 0;
2025-07-15 08:53:22.802914237 UTC 14 0;
2025-07-15 08:53:27.803091506 UTC 7 0;
2025-07-15 08:53:32.80344092 UTC 2 0;
2025-07-15 08:53:37.803080446 UTC 2 0;
2025-07-15 08:53:42.802889406 UTC 2 0;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Triage 🏥
Development

Successfully merging this pull request may close these issues.

1 participant