Benchmark

[oduameh]

---

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

[github-actions]

Test Results

437 tests  ±0   425 ✅ ±0   16m 29s ⏱️ +38s
143 suites ±0    12 💤 ±0 
  5 files   ±0     0 ❌ ±0 

Results for commit b5f2db3. ± Comparison against base commit 384fd04.

♻️ This comment has been updated with latest results.

[olgahryniuk]

For some reason, I cannot find certain files in the repo. The benchmarks folder does not include all the child sections visible on the docs site.

The following changes need to be applied before merging please:
Second file: 'Plutus Merkle tree contract'; 'On-chain Merkle tree costs'
Third file: 'Transaction costs'; '...the actual script is unique per head'; 'Init transaction costs'; 'Commit transaction costs'; 'This uses ada-only outputs for better comparability.' 'CollectCom transaction costs'; 'Close transaction costs'; 'Contest transaction costs'; 'Abort transaction costs'; 'There is some variation due to the random mixture of initial and already committed outputs.'; 'FanOut transaction costs'.
Fourth file: '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.'; 'Baseline scenario'.

The final folder should be renamed to 'Test results'.

[oduameh]

For some reason, I cannot find certain files in the repo. The benchmarks folder does not include all the child sections visible on the docs site.

The following changes need to be applied before merging please: Second file: 'Plutus Merkle tree contract'; 'On-chain Merkle tree costs' Third file: 'Transaction costs'; '...the actual script is unique per head'; 'Init transaction costs'; 'Commit transaction costs'; 'This uses ada-only outputs for better comparability.' 'CollectCom transaction costs'; 'Close transaction costs'; 'Contest transaction costs'; 'Abort transaction costs'; 'There is some variation due to the random mixture of initial and already committed outputs.'; 'FanOut transaction costs'. Fourth file: '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.'; 'Baseline scenario'.

The final folder should be renamed to 'Test results'.

Hi @olgahryniuk that is true, most of the files are not in the benchmark folder, most of the files are embedded in the dev file as partial markdown scripts, which was why I had to revert the changes I made in those sections.

I will make the other changes you have highlighted. Also, did you mean changing the final folder from "Test Results" to "Test results" ?

[olgahryniuk]

Yes, Emmanuel, that's correct. As long as you just change some wording/letters without messing with scripts, it should work. Thank you

[olgahryniuk]

I don't see a commit renaming 'Test Results' to 'Test results'. Can you please address this?