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

Add tip about jq and round-tripping bug #1682

Merged
merged 2 commits into from
Oct 4, 2024
Merged

Conversation

noonio
Copy link
Contributor

@noonio noonio commented Oct 4, 2024

Fixes #1679

@noonio noonio requested a review from a team October 4, 2024 12:08
@noonio noonio force-pushed the tip-jq-large-integers branch from db4fee2 to f9d0e97 Compare October 4, 2024 12:19
Copy link
Member

@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.

That's helpful for the tutorial, but would not catch the problem when using seed-devnet.sh.

I can approve this change already, but maybe we can do a version check in that script too?

Copy link

github-actions bot commented Oct 4, 2024

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-10-04 13:05:34.541566837 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 2ee477c60839936be49a50030690865b5bed4db8cd2f05bf255ac680 10068
μHead a1610f6e64843161f4a88229c0286176f5325de3e2f773eec2b1d818* 4508
νDeposit c2117fd9ebdee3e96b81fd67ff7092d638926415c10f1f7e5a267ad0 2791
  • 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 5097 5.81 2.30 0.44
2 5297 7.17 2.84 0.46
3 5496 8.46 3.34 0.48
5 5901 11.17 4.41 0.53
10 6910 18.06 7.14 0.65
57 16355 82.85 32.77 1.78

Commit transaction costs

This uses ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 566 10.52 4.15 0.29
2 759 13.86 5.65 0.34
3 944 17.33 7.20 0.38
5 1315 24.65 10.44 0.48
10 2250 45.22 19.36 0.75
20 4132 95.99 40.76 1.40

CollectCom transaction costs

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 56 563 21.46 8.41 0.41
2 114 671 32.14 12.75 0.53
3 170 782 45.28 18.14 0.68
4 228 893 57.78 23.39 0.82
5 284 1004 75.40 30.66 1.02
6 338 1120 93.63 38.27 1.23

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 624 17.95 7.88 0.38
2 773 18.51 8.77 0.40
3 918 20.44 10.33 0.43
5 1231 24.25 13.25 0.50
10 2012 32.16 19.90 0.64
50 7817 94.69 73.45 1.79

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 598 19.69 8.69 0.40
2 776 21.49 10.39 0.43
3 955 23.30 12.10 0.47
5 1255 26.18 14.92 0.52
10 1873 33.56 21.92 0.66
50 8173 98.26 83.84 1.91

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 685 25.93 11.15 0.47
2 867 28.14 13.02 0.51
3 1011 29.79 14.49 0.54
5 1209 32.91 17.14 0.59
10 1971 42.46 25.34 0.76
40 6520 99.30 74.27 1.77

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 4990 17.43 7.58 0.57
2 5162 29.46 12.99 0.71
3 5227 41.85 18.44 0.85
4 5445 59.48 26.44 1.06
5 5406 68.96 30.48 1.17
6 5662 97.96 43.62 1.51

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 4934 7.50 3.17 0.45
5 1 57 4968 8.63 3.88 0.47
5 5 284 5103 13.35 6.81 0.53
5 10 570 5275 19.01 10.37 0.61
5 20 1138 5612 30.52 17.57 0.77
5 30 1706 5953 42.04 24.77 0.93
5 40 2274 6290 53.17 31.82 1.09
5 50 2845 6631 64.51 38.94 1.24
5 81 4612 7685 99.28 60.90 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-10-04 13:08:15.482259952 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.549646211
P99 8.442952569999955ms
P95 5.574859149999999ms
P50 4.375622ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 24.407011430
P99 117.75127907000001ms
P95 32.35050974999997ms
P50 21.719691500000003ms
Number of Invalid txs 0

Copy link

github-actions bot commented Oct 4, 2024

Test Results

503 tests  ±0   497 ✅ ±0   22m 43s ⏱️ +21s
160 suites ±0     6 💤 ±0 
  7 files   ±0     0 ❌ ±0 

Results for commit 7b9ecb2. ± Comparison against base commit 22b5cf3.

@noonio
Copy link
Contributor Author

noonio commented Oct 4, 2024

Done @ch1bo

@locallycompact locallycompact added this pull request to the merge queue Oct 4, 2024
Merged via the queue into master with commit ff30a60 Oct 4, 2024
28 checks passed
@locallycompact locallycompact deleted the tip-jq-large-integers branch October 4, 2024 13:30
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.

Demo hydra nodes crashing with $.costModels[175]: parsing Int64 failed errors
3 participants