Add job size benchmark script + on-demand CI workflow - #8495
Open
TomasVotruba wants to merge 2 commits into
Open
Add job size benchmark script + on-demand CI workflow#8495TomasVotruba wants to merge 2 commits into
TomasVotruba wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a benchmark that measures Rector wall time across parallel job sizes, plus a manual CI workflow to run it.
Script
scripts/rector-jobsize-benchmark.phpruns cold Rector dry-runs across a list of job sizes and prints a markdown table of wall time, slowdown vs fastest, exit code, and file counts.CI workflow
.github/workflows/jobsize_benchmark.yamlruns onworkflow_dispatchonly (no per-PR cost). Sizes default to 50 through 300 by 15 and are overridable from the run dialog. Results go to the job summary and an uploaded artifact.Local sweep (24 cores, 20-400 by 10)
Fastest around job size 60-130 (~43-46 s flat); above ~250 it climbs to ~1.8-1.9x slower as large chunks starve cores. All runs analysed the same 2620 files.