

CodSpeed will then aggregate the corresponding results into a single report.
You can speed up your CI even further by combining sharded benchmarks with
partial runs. This way, you can run only the
benchmark suites that are relevant to the code changes in your pull request.
How to split the execution of benchmark suites?
Sharding allows you to run your benchmarks in several commands, with each command running a subset of your benchmarks. There are two main ways of sharding your benchmarks:- splitting them in several files, and running each file or folder independently
- using a sharding tool provided by your benchmarking framework
Configure your CI workflow to use sharded benchmarks
Once you’ve sharded your benchmarks, you can run using several CI jobs within the same workflow, depending on your CI provider:Multiple languages benchmarks
With benchmarks written in several languages, it can be difficult to get a unified performance overview of your project. With CodSpeed, you can run benchmarks written in multiple languages. When run in the same CI workflow, CodSpeed will aggregate the results of these benchmarks into a single report. For example, usingpytest
and vitest
:
.github/workflows/codspeed.yml