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 alice blueprint commit #1627

Closed
wants to merge 2 commits into from
Closed

Conversation

locallycompact
Copy link
Contributor

Adds nix run .#alice-blueprint-commit to be used against the devnet demo.

@locallycompact locallycompact force-pushed the lc/alice-blueprint-commit branch 3 times, most recently from 54bf908 to 61fac2e Compare September 12, 2024 11:56
Copy link

github-actions bot commented Sep 12, 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-09-26 12:05:24.33032503 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 5098 5.79 2.29 0.44
2 5297 7.31 2.90 0.46
3 5499 8.46 3.34 0.48
5 5899 11.35 4.49 0.53
10 6904 18.21 7.20 0.65
57 16355 83.13 32.89 1.78

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 1320 24.65 10.44 0.48
10 2259 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 57 564 22.14 8.66 0.42
2 114 671 33.86 13.39 0.55
3 169 782 46.04 18.40 0.69
4 227 893 58.84 23.77 0.84
5 283 1004 79.23 32.08 1.07
6 337 1116 93.92 38.39 1.23

Cost of Decrement Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 629 17.70 7.78 0.38
2 724 17.82 8.52 0.39
3 981 21.34 10.66 0.44
5 1247 24.50 13.35 0.50
10 2060 33.68 20.54 0.66
49 7879 97.00 73.56 1.81

Close transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 641 20.07 9.01 0.41
2 785 21.57 10.43 0.43
3 869 22.58 11.47 0.45
5 1177 25.92 14.61 0.52
10 2098 35.19 23.29 0.69
50 8212 99.66 84.64 1.93

Contest transaction costs

Parties Tx size % max Mem % max CPU Min fee ₳
1 634 25.48 10.79 0.46
2 814 27.69 12.65 0.50
3 1056 30.33 14.87 0.55
5 1299 33.78 17.84 0.61
10 1917 41.80 24.89 0.75
40 6689 99.54 74.76 1.79

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 4973 17.36 7.55 0.56
2 5087 28.31 12.41 0.69
3 5186 37.79 16.51 0.80
4 5342 56.88 25.16 1.03
5 5460 70.87 31.38 1.19
6 5645 96.03 42.72 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 ₳
5 0 0 4935 7.70 3.25 0.45
5 1 57 4969 8.83 3.96 0.47
5 5 285 5104 13.55 6.89 0.53
5 10 569 5273 18.81 10.28 0.61
5 20 1137 5612 30.52 17.57 0.77
5 30 1709 5956 41.85 24.69 0.93
5 40 2276 6293 52.78 31.65 1.08
5 50 2842 6628 64.51 38.94 1.24
5 81 4612 7685 99.67 61.07 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-09-26 12:08:18.468540699 UTC

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 4.080788079
P99 5.689932679999983ms
P95 4.6061732ms
P50 3.84483ms
Number of Invalid txs 0

Three local nodes

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 27.640348218
P99 124.18937404000002ms
P95 39.429020399999956ms
P50 22.8947195ms
Number of Invalid txs 0

Copy link

github-actions bot commented Sep 12, 2024

Test Results

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

Results for commit 49597a4. ± Comparison against base commit 47410de.

♻️ This comment has been updated with latest results.

demo/alice-blueprint-commit.hs Outdated Show resolved Hide resolved
demo/alice-blueprint-commit.hs Outdated Show resolved Hide resolved
@locallycompact locallycompact force-pushed the lc/alice-blueprint-commit branch 7 times, most recently from 57ec196 to 238786b Compare September 13, 2024 13:14
@noonio
Copy link
Contributor

noonio commented Sep 13, 2024

Looking nice!

Would be great to have a comment somewhere describing what this is used for exactly; as it stands I don't really know what it's for.

I agree this is a significant improvement over the bash scripts. If I could have everything my way, I'd love for this to look a bit like our things in hydra-cluster/src/CardanoNode.hs; i.e. a kind of withCardanoCli $ ... style; but in any case, I think it's a good base to work from!

Copy link
Contributor

@noonio noonio left a comment

Choose a reason for hiding this comment

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

Would just be good to see a comment describing how/where this is to be used!

@locallycompact
Copy link
Contributor Author

Will keep this branch around, but closing for now.

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.

3 participants