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

Refactor benchmark setup and enhance CSV generation logging #112

Merged
merged 14 commits into from
Mar 29, 2024

Conversation

SmetDenis
Copy link
Member

This refactor splits the benchmark setup into two separate jobs for better handling of individual configurations: one for Docker-based benchmarks and another for PHP-based benchmarks. The jobs now support testing with varying numbers of columns. In addition, the CSV generation process now includes better-riched logs for easier debugging.

This refactor splits the benchmark setup into two separate jobs for better handling of individual configurations: one for Docker-based benchmarks and another for PHP-based benchmarks. The jobs now support testing with varying numbers of columns. In addition, the CSV generation process now includes better-riched logs for easier debugging.
@coveralls
Copy link

coveralls commented Mar 29, 2024

Pull Request Test Coverage Report for Build 8485840239

Details

  • 4 of 4 (100.0%) changed or added relevant lines in 3 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.009%) to 97.002%

Totals Coverage Status
Change from base Build 8485098629: -0.009%
Covered Lines: 2491
Relevant Lines: 2568

💛 - Coveralls

This change allows the value of BENCH_COLS to be overridden from the environment. If BENCH_COLS isn't set in the environment, its value defaults to 10. Thus, this improvement provides more flexibility in setting up the benchmark tests.
The BENCH_COLS variable now takes the value from the Github Actions strategy matrix. The default value in the Makefile has also been changed to 10. This allows for better control and flexibility in setting up the benchmark tests.
Updated the benchmark job names from "via Docker" to "Docker" and from "via PHP" to "Phar" for better clarity. Also, adjusted all references from PHAR to Phar in workflows and Makefile for consistency. BigInteger
Updated the benchmark job names from "via Docker" to "Docker" and from "via PHP" to "Phar" for better clarity. Also, adjusted all references from PHAR to Phar in workflows and Makefile for consistency. BigInteger
Made improvements to the .github/workflows/benchmark.yml file. Restructured job names and actions for clarity, and updated the rules for handling local and latest versions of Phar files.
Made improvements to the .github/workflows/benchmark.yml file. Restructured job names and actions for clarity, and updated the rules for handling local and latest versions of Phar files.
The changes in the .github/workflows/benchmark.yml file include updating the reference to use github.event.inputs.branch instead of github.event.pull_request.head.ref. Additionally, the command to build local Phar file has been modified and now includes running the built php archive file.
The changes in the .github/workflows/benchmark.yml file include updating the reference to use github.event.inputs.branch instead of github.event.pull_request.head.ref. Additionally, the command to build local Phar file has been modified and now includes running the built php archive file.
Renamed the workflow from 'Stress Test' to 'Speed Test' in benchmark.yml. Also, unnecessary triggers like Pull Request and Release have been removed to clean up and streamline the testing workflow.
@SmetDenis SmetDenis merged commit c2444c7 into master Mar 29, 2024
9 checks passed
@SmetDenis SmetDenis deleted the bechmark-workflow branch March 29, 2024 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants