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.

Sign up for GitHub

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

Jump to bottom

Change Era from BabbageEra to ConwayEra #1338

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Change Era from BabbageEra to ConwayEra #1338

wants to merge 1 commit into from

Conversation

locallycompact
Copy link
Contributor

@locallycompact locallycompact commented Mar 5, 2024 •
edited
Loading

Switch hydra from BabbageEra to ConwayEra. A Conway compatible hydra-node can be built using

nix build .#hydra-node

or a docker image with

nix build .#docker-hydra-node
  • CHANGELOG updated or not needed
  • Documentation updated or not needed
  • Haddocks updated or not needed
  • No new TODOs introduced or explained herafter

@locallycompact
Copy link
Contributor Author

@ch1bo Here is the withoutProtocolUpdates error. https://github.com/input-output-hk/hydra/actions/runs/8161289799/job/22309727685?pr=1338#step:5:2151

@ch1bo ch1bo self-assigned this Mar 6, 2024
@ch1bo
Copy link
Collaborator

ch1bo commented Mar 6, 2024

@ch1bo Here is the withoutProtocolUpdates error. https://github.com/input-output-hk/hydra/actions/runs/8161289799/job/22309727685?pr=1338#step:5:2151

Protocol updates in the tx body seem to be bound only up to protocol version 8 (= babbage) as they (most likely) are done differently in conway (= protocol version 9)

image

Consequently, let's not clear that field (i.e. the updateTxBodyL) in the generator, but see whether the normal arbitrary transactions are fine within our tests. If not, we might need to tweak the generator to exclude any of the governance actions - the equivalents of protocol updates.

@locallycompact locallycompact force-pushed the lc/conway-support branch 3 times, most recently from b3c46c8 to e29ccc4 Compare March 13, 2024 13:48
@locallycompact locallycompact marked this pull request as draft March 13, 2024 14:06
@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 13, 2024 •
edited
Loading

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 2024-07-24 11:48:48.676050744 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial 2fac819a1f4f14e29639d1414220d2a18b6abd6b8e444d88d0dda8ff 3799
νCommit 2043a9f1a685bcf491413a5f139ee42e335157c8c6bc8d9e4018669d 1743
νHead 7ae23bc9f0833a5689b9fc812dd92fbe9dac881a632f14b28e8eb8db 10193
μHead 3ebfb5b268e0c94200e2c8a8eeebf704aabf303a769af602edb3603a* 4607
  • 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 5193 5.79 2.29 0.44
2 5394 7.31 2.90 0.47
3 5597 8.59 3.40 0.49
5 6000 11.12 4.39 0.54
10 7005 18.02 7.12 0.66
56 16251 81.47 32.22 1.76

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 569 10.52 4.15 0.29
2 758 13.86 5.65 0.34
3 947 17.33 7.20 0.38
5 1319 24.65 10.44 0.48
10 2254 45.22 19.36 0.75
20 4139 95.99 40.76 1.40

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 56 559 22.17 8.68 0.42
2 114 671 33.11 13.12 0.54
3 169 786 47.38 18.92 0.70
4 227 893 60.29 24.32 0.85
5 283 1009 76.90 31.22 1.04
6 336 1116 93.00 38.03 1.22

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 650 17.93 7.88 0.38
2 783 19.11 9.07 0.40
3 987 21.40 10.68 0.44
5 1296 25.16 13.60 0.51
10 1981 31.81 19.76 0.64
48 7834 97.31 72.91 1.81

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 602 20.56 9.05 0.41
2 838 22.75 11.09 0.45
3 919 23.88 12.18 0.47
5 1234 27.12 15.29 0.53
10 2076 35.53 23.28 0.70
50 7996 98.50 83.32 1.90

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 634 26.76 11.34 0.48
2 903 29.24 13.51 0.52
3 950 30.68 14.68 0.55
5 1238 34.11 17.68 0.61
10 2075 44.85 26.67 0.80
38 6346 97.93 72.32 1.74

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 5080 17.47 7.60 0.57
2 5148 27.52 11.98 0.69
3 5311 41.74 18.39 0.85
4 5478 58.45 25.90 1.05
5 5683 78.19 34.87 1.28
6 5765 97.30 43.35 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 ₳
5 0 0 5033 8.15 3.45 0.46
5 1 57 5067 8.49 3.82 0.47
5 5 285 5203 13.60 6.92 0.54
5 10 569 5373 19.06 10.39 0.62
5 20 1139 5712 30.58 17.60 0.78
5 30 1707 6052 41.70 24.63 0.93
5 40 2278 6394 52.84 31.67 1.09
5 50 2844 6730 64.17 38.80 1.24
5 81 4611 7784 99.14 60.84 1.73

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 2024-07-24 11:51:28.260433236 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 5.093697569
P99 12.87487679999984ms
P95 6.088881099999999ms
P50 4.294359ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 24.023160058
P99 88.91332342000047ms
P95 33.70649104999998ms
P50 21.495482ms
Number of Invalid txs 0

@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 14, 2024 •
edited
Loading

Test Results

460 tests   450 ✅  19m 5s ⏱️
147 suites   10 💤
  5 files      0 ❌

Results for commit 9f62d84.

♻️ This comment has been updated with latest results.

@ch1bo ch1bo linked an issue Mar 15, 2024 that may be closed by this pull request
Switch L2 ledger to Conway #1178
Open
2 tasks
@locallycompact locallycompact changed the title Era = ConwayEra Change Era from BabbageEra to ConwayEra May 13, 2024
@locallycompact locallycompact force-pushed the lc/conway-support branch 6 times, most recently from 4f54a45 to 25866ad Compare June 4, 2024 15:18
@locallycompact locallycompact force-pushed the lc/conway-support branch 5 times, most recently from 609d38c to 9578aed Compare July 12, 2024 06:25
@locallycompact locallycompact force-pushed the lc/conway-support branch 7 times, most recently from add33b1 to 0fdc71b Compare July 17, 2024 10:45
@locallycompact locallycompact force-pushed the lc/conway-support branch 3 times, most recently from c983f3b to 0385165 Compare July 22, 2024 08:34
@github-actions GitHub Actions
Copy link

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 2024-07-22 08:37:18.679558094 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial e6685648e63ab510b49d2ce632c570d2ef53f44f3cbdf82ed553906c 4081
νCommit fce3b967fb72f4a3be8dfa30defe413258ff453e5d32d6752d83f9cf 2060
νHead 10a116037de398d6b0721152336d602f0ea653eb3dfe540d5da63fe4 9367
μHead 4f93fdfeda690e005d3f5a180208edd3f65ddd0892466ad7f4dd678b* 4236
  • 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 4825 5.75 2.27 0.43
2 5030 7.18 2.84 0.45
3 5231 8.55 3.38 0.47
5 5627 11.12 4.39 0.52
10 6634 18.24 7.22 0.64
58 16282 84.33 33.36 1.79

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 567 9.25 3.68 0.28
2 756 11.94 4.93 0.32
3 944 14.70 6.20 0.36
5 1323 20.44 8.83 0.44
10 2253 36.05 15.86 0.66
26 5258 98.14 42.75 1.48

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 555 14.13 5.69 0.33
2 113 666 22.50 9.15 0.43
3 171 777 32.95 13.50 0.55
4 228 888 44.62 18.40 0.68
5 282 999 56.63 23.53 0.82
6 336 1111 72.48 30.21 1.00
7 394 1222 89.90 37.57 1.20

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 602 8.04 4.51 0.27
2 756 8.74 5.59 0.29
3 830 9.02 6.29 0.31
5 1147 10.81 8.74 0.35
10 1979 15.21 14.96 0.47
50 8254 49.75 63.32 1.37

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 653 8.35 4.65 0.28
2 794 9.04 5.71 0.30
3 924 9.72 6.76 0.32
5 1340 12.62 10.07 0.38
10 1978 16.15 15.30 0.48
50 7651 46.16 59.83 1.29

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 4623 13.49 5.63 0.50
2 4870 28.04 12.39 0.68
3 5059 42.10 18.72 0.85
4 5148 57.35 25.48 1.02
5 5204 69.05 30.52 1.16
6 5366 95.03 42.21 1.46

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 ₳
5 0 0 4661 7.63 3.20 0.44
5 1 57 4695 9.14 4.07 0.46
5 5 285 4832 13.81 6.96 0.52
5 10 567 4998 18.61 10.13 0.59
5 20 1138 5339 29.99 17.24 0.75
5 30 1710 5683 41.17 24.26 0.91
5 40 2278 6021 52.17 31.21 1.06
5 50 2849 6362 63.56 38.32 1.22
5 82 4667 7444 99.62 60.94 1.72

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 2024-07-22 08:39:48.128471634 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.157384863
P99 7.20362825999994ms
P95 5.249309099999996ms
P50 3.90223ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 22.327715191
P99 112.65735542000004ms
P95 31.0648675ms
P50 19.867236ms
Number of Invalid txs 0

@locallycompact locallycompact force-pushed the lc/conway-support branch 4 times, most recently from 0fdc71b to 4e07337 Compare July 22, 2024 09:34
@github-actions GitHub Actions
Copy link

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 2024-07-22 09:39:40.700446126 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial e6685648e63ab510b49d2ce632c570d2ef53f44f3cbdf82ed553906c 4081
νCommit fce3b967fb72f4a3be8dfa30defe413258ff453e5d32d6752d83f9cf 2060
νHead 10a116037de398d6b0721152336d602f0ea653eb3dfe540d5da63fe4 9367
μHead 4f93fdfeda690e005d3f5a180208edd3f65ddd0892466ad7f4dd678b* 4236
  • 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 4826 5.69 2.25 0.42
2 5030 6.99 2.76 0.45
3 5226 8.56 3.39 0.47
5 5630 11.49 4.55 0.52
10 6632 18.11 7.16 0.64
58 16284 84.27 33.33 1.79

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 569 9.25 3.68 0.28
2 758 11.94 4.93 0.32
3 946 14.70 6.20 0.36
5 1315 20.44 8.83 0.44
10 2254 36.05 15.86 0.66
26 5255 98.14 42.75 1.48

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 555 14.13 5.69 0.33
2 114 666 22.50 9.15 0.43
3 170 777 32.44 13.32 0.54
4 225 888 43.29 17.91 0.67
5 281 999 57.45 23.84 0.83
6 338 1111 72.12 30.09 1.00
7 396 1222 86.57 36.38 1.17

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 609 8.08 4.53 0.28
2 694 8.36 5.25 0.29
3 867 9.40 6.61 0.31
5 1163 10.68 8.71 0.35
10 1847 14.74 14.39 0.45
50 4660 39.25 23.78 0.84

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 629 8.40 4.65 0.28
2 845 9.51 6.07 0.31
3 857 9.30 6.40 0.31
5 1316 12.44 9.92 0.38
10 2028 16.32 15.55 0.48
50 8480 54.07 65.96 1.44

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 4698 16.43 7.17 0.54
2 4804 23.87 10.35 0.63
3 5005 40.82 18.08 0.83
4 5124 53.61 23.69 0.98
5 5266 70.47 31.22 1.18
6 5359 93.87 41.61 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 ₳
5 0 0 4662 7.63 3.20 0.44
5 1 57 4695 9.14 4.07 0.46
5 5 283 4829 13.30 6.75 0.52
5 10 570 5002 19.20 10.39 0.60
5 20 1137 5338 29.99 17.24 0.75
5 30 1705 5678 41.76 24.52 0.91
5 40 2279 6023 52.36 31.29 1.06
5 50 2844 6357 63.76 38.41 1.22
5 82 4670 7447 99.82 61.02 1.72

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 2024-07-22 09:41:30.124151706 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.395327218
P99 8.298198629999995ms
P95 5.7749046ms
P50 4.1818205ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 22.237972718
P99 111.26133579000006ms
P95 30.448627399999992ms
P50 19.881816ms
Number of Invalid txs 0

@locallycompact
Change Era from BabbageEra to ConwayEra
9f62d84 
Do filter protocol updates in Arbitrary Tx anymore

Those are now represented differently in Conway and we'll see how the
fully random transactions (including governance actions that supersede
protocol updates) behave in situations where we use this generator.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ffakenz ffakenz ffakenz approved these changes

Assignees

@locallycompact locallycompact

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Switch L2 ledger to Conway
3 participants
@locallycompact @ch1bo @ffakenz