It is now possible to specify the default base branch for analysis of a repository. It no longer has to be the default branch set on the repository provider.
This changelog will allow us to keep you updated with the latest features we implement! 🚀
It's now possible to zoom in on the benchmark history graph. Making it possible to dive precisely in the history.
It is now possible to list all the runs of a repository independently from their branch using the new runs page: This page also come with individual run pages, allowing for example to dive into the runs made on push on a default branch:
We just released the beta of the CodSpeed CLI! 🥳
This CLI tool allows to make local runs, upload them to CodSpeed, and compare the results to a remote base run. All without having to push your code to a remote repository.
This will help you shorten the feedback loop on performance, you will not have to push your code and wait for the GH Action to complete to see the impact of your changes.
At the moment it only works on Ubuntu 20.04/22.04 and Debian 11/12.
To get started, you can run the following commands:
# Install the codspeed cli curl -fsSL https://github.com/CodSpeedHQ/runner/releases/download/v3.0.0/codspeed-runner-installer.sh | bash source "$HOME/.cargo/env" # Authenticate the CLI with your CodSpeed account codspeed auth login # Inside a repository enabled on CodSpeed # By default, the local run will be compared to the latest remote run of the default branch # If you are checked out on a branch that has a pull request and a remote run on CodSpeed, the local run will be compared to the latest common ancestor commit of the default branch that has a remote run codspeed run [BENCHMARK_COMMAND]
You can now see system calls in the flamegraphs by ticking the "Include system calls" checkbox.
We also now detect benchmarks mostly composed of system calls and display a flakyness warning.