Migrate performance benchmarks to Bazel#60
Draft
realityforge wants to merge 1 commit into
Draft
Conversation
Add a Bazel-backed performance benchmark runner for build-time, code-size, and table-rendering workflows. The new runner supports reduced smoke runs, migrated per-comparison data files, schema validation, and opt-in code-size debug archive output. Update the existing Rake task names to invoke the Bazel runner, add release validation for the new data layout, and include the benchmark test suite in the root Bazel tests. The old Buildr performance-tests module remains in place while the full all-variant manual validation gate is investigated.
realityforge
changed the title
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.
Summary
performance-benchmarks/data.Validation
bazel run //:buildifier_checkbazel test //:all_testsbazel run //performance-benchmarks:benchmark -- --mode=build-times --variant=tiny --warmup-seconds=0 --trials=1 --output-dir=tmp/perf-smoke --sting-version=0.0-smoke --dagger-version=2.25.2bazel run //performance-benchmarks:benchmark -- --mode=code-size --variant=tiny --output-dir=tmp/perf-smoke --sting-version=0.0-smoke --dagger-version=2.25.2bundle exec buildr update_build_time_statistics PERF_SMOKE=true PRODUCT_VERSION=0.0-smokebundle exec buildr update_code_size_statistics PERF_SMOKE=true PRODUCT_VERSION=0.0-smokeruby -c tasks/perf.rakeruby -c tasks/release.rakeNotes
The old Buildr
performance-testsmodule is intentionally still present while the full all-variant manual benchmark run is investigated. The default code-size run does not emit debug archives; archives are available through the explicit archive option for debugging.