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

Use PlutusScriptSerialised consistently instead of fromPlutusScript #1776

Merged
merged 1 commit into from
Jan 8, 2025

Conversation

locallycompact
Copy link
Contributor

No description provided.

Copy link

github-actions bot commented Jan 7, 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 - - - -
44 - - - -

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 - - - - -
10 - - - - -

Cost of Increment Transaction

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

Cost of Decrement Transaction

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

Close transaction costs

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

Contest transaction costs

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

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) - - - - -
(40, 10) - - - - -
(41, 10) - - - - -

Copy link

github-actions bot commented Jan 7, 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-01-08 11:36:59.718274666 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial 00a6ddbc130ab92f5b7cb8d1ccd8d79eca5bfe25f6843c07b62841f0 2667
νCommit 3e5a776bcee213e3dfd15806952a10ac5590e3e97d09d62eb99266b2 690
νHead 5350e9d521552ebfd9e846fd70c3b801f716fc14296134ec0fb71e97 14495
μHead 482c3ce15cde05bc905b915ccfa2546e500be1c5d722389026c37aa3* 5615
νDeposit de09cec5f84eedaf64186cb52ba4ee6e74e6fc368af25b90d457f352 1118
  • 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 6165 10.17 3.24 0.53
2 6370 12.04 3.82 0.56
3 6566 14.26 4.52 0.59
5 6969 18.52 5.87 0.65
10 7975 28.42 8.97 0.80
44 14814 98.38 30.98 1.82

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 556 2.45 1.17 0.20
2 743 3.40 1.74 0.22
3 923 4.39 2.34 0.24
5 1283 6.46 3.61 0.29
10 2177 12.24 7.28 0.40
54 10060 99.20 68.72 1.89

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 525 25.04 7.27 0.43
2 114 636 32.99 9.57 0.51
3 170 747 39.43 11.48 0.58
4 227 862 47.46 13.79 0.67
5 282 974 57.91 16.75 0.78
6 340 1081 71.25 20.37 0.92
7 393 1192 74.03 21.36 0.95
8 448 1303 97.52 27.32 1.19

Cost of Increment Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 1802 24.05 8.00 0.48
2 1983 26.49 9.51 0.52
3 2076 27.08 10.29 0.53
5 2436 30.48 12.83 0.60
10 3168 39.99 19.28 0.75
43 8071 98.61 60.69 1.74

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 594 22.68 7.31 0.41
2 799 25.14 8.68 0.45
3 942 26.80 9.81 0.48
5 1173 28.67 11.65 0.52
10 2033 40.83 18.39 0.70
43 6784 97.84 56.39 1.65

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 601 28.00 8.86 0.47
2 792 30.27 10.34 0.50
3 914 32.06 11.56 0.53
5 1233 36.16 14.27 0.60
10 2011 43.05 20.04 0.73
37 6139 94.75 55.54 1.59

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 687 33.35 10.43 0.53
2 822 35.25 11.68 0.56
3 1030 37.82 13.25 0.60
5 1304 42.39 16.06 0.67
10 1993 52.11 22.45 0.82
32 5279 99.51 52.45 1.56

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 6082 26.21 8.87 0.69
2 6117 33.79 11.37 0.77
3 6348 44.15 14.97 0.89
4 6388 48.31 16.30 0.94
5 6571 61.78 20.92 1.09
6 6830 72.44 24.66 1.21
7 6925 78.75 26.72 1.28
8 6932 87.90 29.63 1.38
9 7154 96.35 32.62 1.48

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 6162 18.03 6.15 0.61
10 1 57 6196 19.99 6.94 0.63
10 5 285 6332 27.82 10.09 0.73
10 20 1139 6842 57.20 21.90 1.07
10 30 1707 7182 77.52 30.05 1.31
10 40 2273 7518 96.02 37.53 1.53
10 42 2391 7589 99.94 39.10 1.57

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-01-08 11:38:31.642330117 UTC

Baseline Scenario

Number of nodes 1
Number of txs 300
Avg. Confirmation Time (ms) 4.214350193
P99 8.309258429999993ms
P95 5.0168154ms
P50 4.035251000000001ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 900
Avg. Confirmation Time (ms) 24.157037575
P99 119.19072603999999ms
P95 33.5363875ms
P50 21.585213500000002ms
Number of Invalid txs 0

Copy link

github-actions bot commented Jan 7, 2025

Test Results

  5 files  ±0  165 suites  ±0   30m 30s ⏱️ - 1m 12s
563 tests ±0  557 ✅ ±0  6 💤 ±0  0 ❌ ±0 
565 runs  ±0  559 ✅ ±0  6 💤 ±0  0 ❌ ±0 

Results for commit 527cc21. ± Comparison against base commit 6a0f3e3.

♻️ This comment has been updated with latest results.

@locallycompact locallycompact force-pushed the lc/remove-fromPlutusScript branch 3 times, most recently from 1475ae1 to 685f1a9 Compare January 7, 2025 19:31
Copy link
Collaborator

@ch1bo ch1bo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I liked the fromPlutusScript alias as its slightly shorter and has a better / easier to find name.

But as you already did this, lets merge.

@ch1bo ch1bo force-pushed the lc/remove-fromPlutusScript branch from 685f1a9 to 527cc21 Compare January 8, 2025 11:30
@ch1bo ch1bo added this pull request to the merge queue Jan 8, 2025
Merged via the queue into master with commit 2039d7c Jan 8, 2025
27 checks passed
@ch1bo ch1bo deleted the lc/remove-fromPlutusScript branch January 8, 2025 12:23
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.

2 participants