Skip to content
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

Markdown table and headings for the memory report #1850

Merged
merged 4 commits into from
Feb 12, 2025

Conversation

noonio
Copy link
Contributor

@noonio noonio commented Feb 12, 2025

Fixes #1837

Copy link

github-actions bot commented Feb 12, 2025

Transaction cost differences

Script summary

Name Size (Bytes)
νInitial -
νCommit -
νHead -
μHead -
νDeposit -

Init transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 - - - -
2 - - - -
3 - - - -
5 - - - -
10 - - - -
40 - - - -

Commit transaction costs

UTxO Tx size % max Mem % max CPU Min fee ₳
1 - - - -
2 - - - -
3 - - - -
5 - - - -
10 - - - -
54 - - - -

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 - - - - -
2 - - - - -
3 - - - - -
4 - - - - -
5 - - - - -
6 - - - - -
7 - - - - -
8 - - - - -

Cost of Increment Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 - - - -
2 - - - -
3 - +0.39 +0.09 -
5 - - - -
10 - $${\color{green}-0.39}$$ $${\color{green}-0.09}$$ $${\color{green}-0.01}$$
37 - - - -

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 - - - -
2 - - - -
3 - - - -
5 - - - -
10 - - - -
40 - - - -

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 - - - -
2 - - - -
3 - - - -
5 - - - -
10 - - - -
34 - - - -

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 - - - -
2 - - - -
3 - - - -
5 - - - -
10 - - - -
27 - - - -

FanOut transaction costs

UTxO, Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
(0, 10) - - - - -
(1, 10) - - - - -
(5, 10) - - - - -
(10, 10) - - - - -
(20, 10) - - - - -
(37, 10) - - - - -

Copy link

github-actions bot commented Feb 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-02-12 10:09:32.900648088 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 0e35115a2c7c13c68ecd8d74e4987c04d4539e337643be20bb3274bd 14756
μHead 57166715eadb8d3135964325c016eea546c21e1c0aae974ca67df9a5* 5541
ν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 6093 10.80 3.35 0.53
2 6296 13.35 4.15 0.57
3 6496 15.50 4.80 0.60
5 6897 19.94 6.16 0.66
10 7907 31.06 9.57 0.82
40 13933 98.61 30.29 1.78

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 740 3.38 1.73 0.22
3 917 4.36 2.33 0.24
5 1282 6.41 3.60 0.28
10 2170 12.13 7.25 0.40
54 10049 98.61 68.52 1.88

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 525 26.44 7.58 0.44
2 114 636 34.88 9.98 0.53
3 170 747 44.80 12.75 0.64
4 228 858 52.15 14.92 0.72
5 282 969 60.76 17.38 0.81
6 341 1081 72.90 20.63 0.94
7 394 1192 88.26 24.70 1.09
8 448 1303 85.25 24.52 1.07

Cost of Increment Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 1797 25.50 8.33 0.50
2 1928 26.69 9.39 0.52
3 2018 27.59 10.25 0.54
5 2377 32.56 13.28 0.61
10 3149 42.54 19.85 0.78
39 7362 98.53 56.99 1.68

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 597 23.99 7.61 0.43
2 741 25.59 8.72 0.45
3 1007 29.47 10.46 0.51
5 1300 32.91 12.74 0.57
10 1914 39.84 17.96 0.69
39 6259 98.77 53.53 1.61

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 651 30.95 9.68 0.50
2 846 33.55 11.23 0.54
3 906 32.07 11.34 0.53
5 1309 37.31 14.52 0.61
10 2086 50.51 22.05 0.81
35 5876 99.67 54.68 1.61

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 628 35.29 10.70 0.54
2 835 38.15 12.33 0.58
3 1077 41.73 14.28 0.64
5 1233 44.59 16.26 0.68
10 2146 58.55 24.22 0.89
27 4549 98.02 47.75 1.49

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 5984 28.16 9.29 0.71
2 6159 38.40 12.71 0.82
3 6225 44.51 14.66 0.89
4 6404 56.68 18.79 1.03
5 6488 66.66 22.01 1.13
6 6694 78.22 25.87 1.26
7 6793 80.28 26.49 1.29
8 6954 98.36 32.51 1.49

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 5 285 6261 30.77 10.75 0.75
10 10 571 6432 40.96 14.72 0.87
10 20 1137 6769 62.26 22.99 1.12
10 37 2107 7350 99.40 37.34 1.55

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-02-12 10:13:04.658520917 UTC

Baseline Scenario

Number of nodes 1
Number of txs 300
Avg. Confirmation Time (ms) 4.573133156
P99 9.470246379999995ms
P95 5.7302551ms
P50 4.391218ms
Number of Invalid txs 0

Memory data

Time Used Free
2025-02-12 10:11:40.340185015 UTC 942M 3733M
2025-02-12 10:11:45.340263571 UTC 1021M 3632M
2025-02-12 10:11:50.340205506 UTC 1026M 3627M
2025-02-12 10:11:55.340215203 UTC 1027M 3626M
2025-02-12 10:12:00.340212225 UTC 1031M 3622M
2025-02-12 10:12:05.340158953 UTC 1030M 3622M

Three local nodes

Number of nodes 3
Number of txs 900
Avg. Confirmation Time (ms) 23.295633306
P99 73.18168878ms
P95 32.052332549999996ms
P50 21.069676ms
Number of Invalid txs 0

Memory data

Time Used Free
2025-02-12 10:12:17.58373908 UTC 946M 3717M
2025-02-12 10:12:22.583728214 UTC 1135M 3528M
2025-02-12 10:12:27.583736937 UTC 1135M 3527M
2025-02-12 10:12:32.583687127 UTC 1143M 3519M
2025-02-12 10:12:37.584022252 UTC 1194M 3399M
2025-02-12 10:12:42.583736457 UTC 1224M 3288M
2025-02-12 10:12:47.583719294 UTC 1224M 3286M
2025-02-12 10:12:52.583720973 UTC 1228M 3282M
2025-02-12 10:12:57.583689528 UTC 1231M 3279M
2025-02-12 10:13:02.583746325 UTC 1239M 3271M

@noonio noonio force-pushed the fix-memory-reporting-formatting branch from c51063c to 7e5eaa1 Compare February 12, 2025 10:02
@noonio noonio enabled auto-merge February 12, 2025 10:02
@noonio noonio added this pull request to the merge queue Feb 12, 2025
@noonio noonio changed the title Markdown table and headings Markdown table and headings for the memory report Feb 12, 2025
Merged via the queue into master with commit 5e55e3e Feb 12, 2025
25 checks passed
@noonio noonio deleted the fix-memory-reporting-formatting branch February 12, 2025 10:38
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.

Fix memory statistics not being printed as a comment directly
2 participants