Only bench what matters with Partial Runs
With your projects becoming larger, you might end up with long-running benchmark workflows, degrading the performance feedback loop and using a lot of resources in your CI.
Now you can solve this with Partial Runs and only run a subset of the benchmarks that are defined in your codebase.
For example you can only run benchmarks relevant to the code changes in a pull request, or run a subset of long-running benchmarks on a schedule.
Partial Runs
From now on, you can run only a subset of your benchmarks in a CI workflow. You will still keep a complete performance history of your codebase, since the benchmarks that are not run will be marked as "skipped" and use the results from the base run.
Handling removed benchmarks with Benchmark Archival
To keep your reports clean and relevant, you will now be able to archive benchmarks that were removed from your codebase.
When you remove a benchmark from your codebase and make a new commit, it will first be marked as "skipped" due to the Partial Runs feature. You can then archive it to remove it from from future reports, while still keeping its history for reference.
Learn more about Partial Runs and Benchmark Archival!