Add CodSpeed continuous performance testing#68
Merged
Conversation
Contributor
Author
Congrats! CodSpeed is installed 🎉
You will start to see performance impacts in the reports once the benchmarks are run from your default branch.
|
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
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
This PR integrates CodSpeed for continuous performance testing of the xml2arrow parsing benchmarks.
Changes
criterionwithcodspeed-criterion-compatinbenches/parse_benchmark.rsto enable CodSpeed's instrumentation layer. The existing Criterion API is fully preserved -- benchmarks still work withcargo benchas before..github/workflows/codspeed.ymlthat builds and runs theparse_benchmarksuite on every push tomain, on pull requests, and on manual dispatch. Uses OIDC authentication and simulation mode for reproducible, hardware-independent measurements.codspeed-criterion-compatv4.4.1 as a dev-dependency and updatedCargo.lock.How it works
CodSpeed's simulation mode uses CPU instruction counting (via valgrind) rather than wall-clock timing, which eliminates variance from CI runner load and produces fully reproducible results. The
codspeed-criterion-compatcrate is a drop-in replacement forcriterionthat hooks into this instrumentation when running under CodSpeed, and falls back to standard Criterion behavior otherwise.Next steps
mainwill establish the baseline performance data.