Walltime instrument and Macro runners
We're happy to announce a new instrument called "Walltime" that allows you to measure the wall time of your benchmarks. For now, this instrument is only available with CodSpeed Macro Runners, CodSpeed hosted bare metal runners that are optimized for running macro benchmarks, isolated from other noisy workloads.
Running Walltime measurements is as simple as changing the execution runner to
codspeed-macro in GitHub Actions. Here's an example of how to do it:
jobs:
benchmarks:
name: Run benchmarks
runs-on: ubuntu-latest
runs-on: codspeed-macro
steps:
- uses: actions/checkout@v4
# ...
- name: Run benchmarks
uses: CodSpeedHQ/action@v3
with:
token: ${{ secrets.CODSPEED_TOKEN }}
run: "<Insert your benchmark command here>"Then, you can see the wall time results in the CodSpeed dashboard:
More info on the WallTime instrument can be found in the documentation.
This feature is still in closed beta, but if you're interested in trying it out, please reach out to us on Discord or by email at support@codspeed.io.
Customize Default Branch For Analysis
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.
Add this changelog
This changelog will allow us to keep you updated with the latest features we implement! 🚀
Zoom in the benchmark history
It's now possible to zoom in on the benchmark history graph. Making it possible to dive precisely in the history.
New runs page
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: 
CodSpeed CLI Beta
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.
Trying it out
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]Include system calls in the flamegraphs
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.
