NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI · #2702 most downloaded on PyPI
Pytest plugin to create CodSpeed benchmarks
Last release 4 months ago
22 May 2026
Release timing varies
gaps range from 9 days to 4 months
Nearly every release is documented
notes for 25 of 25 stable releases
4 versions withdrawn
withdrawn after publishing
4 years old
42 releases · first in 2022
One column per quarter.
chore: move callgrind skip obj API to instrument-hooks by @not-matthias in #123
Full Changelog: v5.0.2...v5.0.3
feat: skip Python runtime objects in callgrind by @not-matthias in #122
Full Changelog: v5.0.1...v5.0.2
build: enable free-threaded wheels in cibuildwheel by @art049 in #121
Full Changelog: v5.0.0...v5.0.1
MacOS walltime profiling is now available with the codspeed cli v4.16.1 and above.
MacOS walltime profiling is now available with the codspeed cli v4.16.1 and above.
pytest-codspeed can now be used in free threaded mode. This has been tested with 3.14t and 3.15t.
For this, we have dropped usage of cffi in favor of the native extension support.
Full Changelog: v4.5.0...v5.0.0
This release adds first support for macOS walltime.
This release adds first support for macOS walltime.
Please note that profiling and other instruments are not yet available on macOS and will come in a later update.
Full Changelog: v4.4.0...v4.5.0
We now collect buildtime and runtime environment data to warn users about differences in their runtime environment when comparing two runs against one
We now collect buildtime and runtime environment data to warn users about differences in their runtime environment when comparing two runs against one another.
This data includes toolchain metadata like version and build options, as well as a list of dynamically loaded linked libraries.
Full Changelog: v4.3.0...v4.4.0
This release brings support for the memory instrument , which enables you to track memory usage, heap allocations, and memory leaks in your benchmarks
This release brings support for the memory instrument, which enables you to track memory usage, heap allocations, and memory leaks in your benchmarks.
Full Changelog: v4.2.0...v4.3.0
Support python 3.14 by @adriencaccia in #91
Nothing published for this version
fix: build on macos with instrument-hooks by @not-matthias in #90
Full Changelog: v4.1.0...v4.1.1
🚀 The new version of CodSpeedHQ/instrument-hooks will improve the quality of the walltime profiling!
🚀 The new version of CodSpeedHQ/instrument-hooks will improve the quality of the walltime profiling!
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v4.0.0...v4.1.0
This release introduces profiling to the walltime instrument and includes several key improvements to the existing benchmark fixture API! 🎉
This release introduces profiling to the walltime instrument and includes several key improvements to the existing benchmark fixture API! 🎉
[!WARNING]
Since we're now using CodSpeedHQ/instrument-hooks to control the instrument state, the performance may slightly change in tiny microbenchmarks when upgrading.
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v3.2.0...v4.0.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
This release improves the reliability of the measurement, primarily focusing on the wall-time instrument.
This release improves the reliability of the measurement, primarily focusing on the wall-time instrument.
Increase the min round time to a bigger value (+/- 1ms) by @art049
Fix the random seed while measuring with instruments by @art049 in #48
⚠️ Since the wall-time instrument is still in beta, this minor release might create unexpected performance changes for this new instrument.
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v3.1.2...v3.2.0
fix: update package_data to include header and source files for valgrind wrapper by @art049 in https://github.com/CodSpeedHQ/pytest-codspeed/pull/64
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v3.1.1...v3.1.2
Add a py3-none-any fallback wheel by @art049 in https://github.com/CodSpeedHQ/pytest-codspeed/pull/61
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v3.1.0...v3.1.1
Nothing published for this version
Nothing published for this version
Nothing published for this version
Build the native extension during packaging to avoid runtime build issues by @art049 in https://github.com/CodSpeedHQ/pytest-codspeed/pull/57
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v3.0.0...v3.1.0
Nothing published for this version
This new release includes a new wall time instrument that allows measurement of real execution timings. This will be very useful for macro benchmarks
This new release includes a new wall time instrument that allows measurement of real execution timings. This will be very useful for macro benchmarks running on properly isolated machines. You can now use our CodSpeed Macro runners without changing anything to your existing CI workflows.
Find more info on our Walltime instrument here.
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v2.2.1...v3.0.0
Send more outlier data by @art049
Also save the lower and upper fences in the json data by @art049 in #46
Also save the q1 and q3 in the json data by @art049 in #45
Send the semver version to cospeed instead of the PEP440 one by @art049 in #44
Improve table style when displaying results by @art049 in #41
fix: Loosen runtime requirements by @edgarrmondragon in https://github.com/CodSpeedHQ/pytest-codspeed/pull/21
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v2.2.0...v2.2.1
pytest-xdist is now fully supported. Thus if you have a lot of benches, you can totally leverage xdist test distribution (on the same CPU) to speed up
pytest-xdist is now fully supported. Thus if you have a lot of benches, you can totally leverage xdist test distribution (on the same CPU) to speed up benchmark execution.
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v2.1.0...v2.2.0
Relative paths are now properly handled when using the working-directory action parameter.
Relative paths are now properly handled when using the working-directory action parameter.
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v2.0.1...v2.1.0
Added support for returning values by @patrick91 in https://github.com/CodSpeedHQ/pytest-codspeed/pull/12
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v2.0.0...v2.0.1
A heads-up, this is a breaking change and it might affect your current performance baseline a bit. But here's the exciting part - it's packed with new…
Flame graph generation is now supported with Python 3.12+, allowing more granularity in the performance reports. More details can be found in the documentation.
Each benchmark is now warmed up a single time before each run to reduce the flakiness and the side effects related to the order in which the benchmarks are run.
A heads-up, this is a breaking change and it might affect your current performance baseline a bit. But here's the exciting part - it's packed with new, cool features and promises improved result stability 🎉!
We recommend you create a standalone PR to update the pytest-codspeed package, acknowledge the potential regressions, and merge it to update the baseline on your default branch.
benchmark.extra_info from pytest-benchmark by @art049 in https://github.com/CodSpeedHQ/pytest-codspeed/pull/10Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v1.2.2...v2.0.0
feat: add library metadata in the profile output by @art049 in https://github.com/CodSpeedHQ/pytest-codspeed/pull/5
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v1.2.1...v1.2.2
fix: support kwargs with the benchmark fixture by @art049 in https://github.com/CodSpeedHQ/pytest-codspeed/pull/4
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v1.2.0...v1.2.1
fix: disable automatic garbage collection to increase stability by @art049 in https://github.com/CodSpeedHQ/pytest-codspeed/pull/2
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v1.1.0...v1.2.0
feat: allow running along with pytest-benchmark by @art049 in https://github.com/CodSpeedHQ/pytest-codspeed/pull/1
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v1.0.4...v1.1.0
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v0.0.3...v1.0.4
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v0.0.3...v1.0.4
Nothing published for this version
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v1.0.1...v1.0.2
Full Changelog: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v1.0.1...v1.0.2
[4.1.0]: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v4.0.0..v4.1.0 [4.0.0]: https://github.com/CodSpeedHQ/pytest-codspeed/compare/v3.2.0..v
<!-- generated by git-cliff -->
Your coding agent can read these notes before it upgrades. Set up the MCP server →