The Python Speed Center is the public performance dashboard for CPython. Every night it builds the current development branch and the maintenance branches from source, runs the pyperformance benchmark suite on dedicated hardware, and records the results here so that anyone can see how the interpreter's speed changes commit by commit.
On this site an executable is a particular way of building CPython and an environment is the machine it ran on. The names below are the ones that can be selected in the sidebars.
| Environment | Machine | Results |
|---|---|---|
speed-python |
x86-64: HP ProLiant DL380 G7 at OSUOSL | October 2021 to present |
ampere-one |
AArch64: Ampere One server hosted by Arm | August 2025 to present |
arm-neoverse |
AArch64: the previous Arm Neoverse machine, replaced by
ampere-one |
May 2023 to August 2025 |
bb-benchmark-machine |
A separate, short-lived benchmark worker | October 2021 to March 2023 |
speed-python-historical |
Results from before the current speed-python
environment was set up, kept for reference |
November 2020 to October 2021 |
Retired environments no longer receive results but are kept so that old data stays reachable through the Timeline and Comparison pages.
speed-python)Nicknamed "the beast", this server was donated to the Python Software Foundation by the HP Open Source Program Office in 2011. The acquisition was announced on Jesse Noller's blog.
Racking, hardware administration and all bandwidth are donated by the Oregon State University Open Source Lab (OSUOSL), long-standing supporters of open source and of the PSF. We are very grateful to both HP and OSUOSL.
ampere-one)This server was donated to the PSF by Arm Ltd, who also host it.
We cannot thank Arm enough for the hardware, the hosting and the administration.
The Speed Center started as a shared project between the CPython, PyPy,
IronPython and Jython teams. At the PyCon 2011 VM and language summits the
maintainers of the major implementations agreed to move to a common benchmark
suite and a single performance-oriented site, modelled on the PyPy team's
speed.pypy.org and using the Codespeed software they had adopted. HP donated
the first machine the same year. Today the site focuses on CPython, results
for PyPy can be found on speed.pypy.org.
This site runs on Codespeed,
a Django application for tracking and analysing the performance of a code
base over time. The Speed Center's own fork, including the templates and
styling you are looking at, is maintained at
python/codespeed,
currently at commit d84c6dfc8bca.
Questions, problems and suggestions about this site are welcome in the Core Development category on discuss.python.org. Problems with the site's code can be reported on the python/codespeed issue tracker, and problems with the benchmarks themselves on the pyperformance tracker.