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

Monthly report January 2024 #1265

Merged
merged 16 commits into from
Feb 1, 2024
Merged

Monthly report January 2024 #1265

merged 16 commits into from
Feb 1, 2024

Conversation

ch1bo
Copy link
Member

@ch1bo ch1bo commented Jan 22, 2024

TODO:


  • CHANGELOG updated or not needed
  • Documentation updated or not needed
  • Haddocks updated or not needed
  • No new TODOs introduced or explained herafter

Copy link

github-actions bot commented Jan 22, 2024

Transactions 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-01-31 18:05:46.938456663 UTC
Max. memory units 14000000
Max. CPU units 10000000000
Max. tx size (kB) 16384

Script summary

Name Hash Size (Bytes)
νInitial 985245919fcc6c0c5cd116023cd2c947c43e80dcbb5075fe12433fbb 4072
νCommit 7cb20fa71eb4c563ca283566ebe0aa65859d96c3f8cba35c52c181fd 2043
νHead 7a36661f5c15e9f1783aeaab890812c59b7286cbbc6de762d3110772 8816
μHead 8b111ac12274e46314769295a1c5dcab1d260096fc469fd698065463* 3851
  • The minting policy hash is only usable for comparison. As the script is parameterized, the actual script is unique per Head.

Cost of Init Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 4375 10.35 3.99 0.46
2 4575 12.68 4.88 0.49
3 4774 15.02 5.77 0.52
5 5177 19.20 7.35 0.59
10 6184 30.24 11.53 0.75
41 12415 98.92 37.55 1.77

Cost of Commit Transaction

This is using ada-only outputs for better comparability.

UTxO Tx size % max Mem % max CPU Min fee ₳
1 534 11.37 4.44 0.30
2 723 15.04 6.07 0.35
3 911 18.85 7.75 0.40
5 1277 26.90 11.27 0.51
10 2222 49.55 20.97 0.80
19 3896 99.43 41.75 1.43

Cost of CollectCom Transaction

Parties UTxO (bytes) Tx size % max Mem % max CPU Min fee ₳
1 57 484 21.12 8.27 0.40
2 114 590 34.11 13.43 0.55
3 170 700 44.77 17.86 0.67
4 227 814 60.34 24.18 0.85
5 282 924 79.03 31.77 1.06
6 338 1031 92.81 37.66 1.22

Cost of Close Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 491 16.23 7.33 0.36
2 757 18.54 9.37 0.40
3 961 20.27 11.00 0.44
5 1208 23.26 13.81 0.49
10 1487 28.22 13.60 0.54
50 8949 97.06 82.96 1.93

Cost of Contest Transaction

Parties Tx size % max Mem % max CPU Min fee ₳
1 578 20.18 8.94 0.40
2 771 22.30 10.70 0.44
3 963 24.20 12.39 0.48
5 1254 27.71 15.43 0.54
10 2147 37.41 23.78 0.72
43 7641 99.42 76.98 1.84

Cost of Abort Transaction

Some variation because of random mixture of still initial and already committed outputs.

Parties Tx size % max Mem % max CPU Min fee ₳
1 4327 19.02 8.19 0.55
2 4477 31.77 13.85 0.70
3 4669 47.45 20.83 0.89
4 4812 65.96 29.03 1.10
5 4889 80.69 35.37 1.27

Cost of FanOut Transaction

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 4205 8.26 3.46 0.43
5 1 57 4239 9.28 4.13 0.44
5 5 285 4375 14.40 7.27 0.51
5 10 569 4544 20.34 10.99 0.59
5 20 1139 4884 32.43 18.53 0.76
5 30 1710 5227 44.94 26.25 0.93
5 40 2278 5565 57.33 33.92 1.10
5 50 2844 5901 69.77 41.61 1.27
5 74 4211 6716 99.34 59.96 1.68

End-To-End Benchmark Results

This page is intended to collect the latest end-to-end benchmarks results produced by Hydra's Continuous Integration system from the latest master code.

Please take those results with a grain of salt as they are currently produced from very limited cloud VMs and not controlled hardware. Instead of focusing on the absolute results, the emphasis should be on relative results, eg. how the timings for a scenario evolve as the code changes.

Generated at 2024-01-31 18:07:30.044463337 UTC

Baseline Scenario

Number of nodes 3
Number of txs 9000
Avg. Confirmation Time (ms) 22.346406939
P99 115.53627973000002ms
P95 32.59045329999999ms
P50 19.218775ms
Number of Invalid txs 0

Baseline Scenario

Number of nodes 1
Number of txs 3000
Avg. Confirmation Time (ms) 3.877396738
P99 10.14782836999995ms
P95 4.606088049999999ms
P50 3.6862760000000003ms
Number of Invalid txs 0

Copy link

github-actions bot commented Jan 22, 2024

Test Results

407 tests  ±0   400 ✅ ±0   13m 16s ⏱️ +6s
137 suites ±0     7 💤 ±0 
  5 files   ±0     0 ❌ ±0 

Results for commit 29dbba0. ± Comparison against base commit cc97c5f.

♻️ This comment has been updated with latest results.

@ch1bo ch1bo self-assigned this Jan 26, 2024
@ch1bo ch1bo force-pushed the monthly-01-2024 branch 2 times, most recently from 9533f41 to 3f9db73 Compare January 29, 2024 14:53
@ch1bo ch1bo marked this pull request as ready for review January 29, 2024 14:53
@ch1bo ch1bo removed their assignment Jan 29, 2024
@ch1bo ch1bo requested review from NeilBurgess42, olgahryniuk and a team January 29, 2024 14:54
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Minor typos

@ch1bo ch1bo linked an issue Jan 29, 2024 that may be closed by this pull request
@ch1bo ch1bo force-pushed the monthly-01-2024 branch 2 times, most recently from 65aeb99 to 173d0ae Compare January 31, 2024 17:17
Copy link
Member Author

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

@olgahryniuk @oduameh Commenting on the commit, unfortuantely without suggestions, but I feel this works much better than a separate PR which has conflicts.

Only some semantic changes needed and a few comments on aligning form between us. Please respond directly on the threads and I'll do the ammendments. Next time we can use the +- suggestions here on github or so.

ch1bo and others added 6 commits January 31, 2024 19:01
commit a473375
Author: olgahryniuk <[email protected]>
Date:   Wed Jan 31 14:00:37 2024 +0200

    Final TW review: several improvements

commit 05c117a
Merge: d1251a0 7cf5eb2
Author: oduameh <[email protected]>
Date:   Wed Jan 31 10:51:11 2024 +0000

    seventh review

commit d1251a0
Merge: e52467e 675a164
Author: oduameh <[email protected]>
Date:   Wed Jan 31 10:35:21 2024 +0000

    sixth review

commit e52467e
Merge: b9178ca d7adcc6
Author: oduameh <[email protected]>
Date:   Wed Jan 31 10:34:42 2024 +0000

    fifth review

commit b9178ca
Merge: 40eb0bb 684a3b7
Author: oduameh <[email protected]>
Date:   Wed Jan 31 10:25:32 2024 +0000

    fourth review

commit 40eb0bb
Author: oduameh <[email protected]>
Date:   Tue Jan 30 18:19:47 2024 +0000

    third review

commit 684a3b7
Author: oduameh <[email protected]>
Date:   Tue Jan 30 18:19:47 2024 +0000

    hydra monthly dev report 2
@ch1bo
Copy link
Member Author

ch1bo commented Jan 31, 2024

@olgahryniuk Addressed all your suggestions and my corrections
@oduameh feel free to also give it a review (Files tab).

I think this is finished and we can publish by approving/merging.

@v0d1ch v0d1ch merged commit 82739f7 into master Feb 1, 2024
20 of 21 checks passed
@v0d1ch v0d1ch deleted the monthly-01-2024 branch February 1, 2024 10:39
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.

Incorrect rendering of mathematical notation in web site
5 participants