# About speed.python.org and aarch64

**URL:** <https://discuss.python.org/t/about-speed-python-org-and-aarch64/22519>\
**Category:** Core Development\
**Created:** [January 6, 2023, 3:47pm UTC](https://discuss.python.org/t/about-speed-python-org-and-aarch64/22519 "2023-01-06T15:47:30Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![diegor](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/diegor/32/34816_2.png) [@diegor](https://discuss.python.org/u/diegor)\
**Post date:** [March 4, 2024, 2:42pm UTC](https://discuss.python.org/t/about-speed-python-org-and-aarch64/22519/21 "2024-03-04T14:42:50Z")

</div>

Hello everyone!

I bring good news with me! @ambv and I have been working in the background to properly integrate AArch64 benchmark results to [speed.python.org](http://speed.python.org).

Today I can confirm that:

- daily benchmarks are running on AArch64
- commits since May 2023 have been backfilled
- the `speed-python` and `arm-neoverse` environments have now the same commits since May 2023.
- the hack that mapped `main` and `master` branches have been removed and existent data have been migrated to use only `main` branch.
- cleaned up old and abandoned data in the database

[speed.python.org](http://speed.python.org) is far from to be perfect and we have already a list of issues that we’d like to implement: [Issues · python/codespeed · GitHub](https://github.com/python/codespeed/issues)

Have a look and give your feedback. Of course contributions are more than welcome 🙂

I want to thank @ambv for his support and patience in helping me enabling AArch64 metrics.

Cheers

---

_[View the full topic](https://discuss.python.org/t/about-speed-python-org-and-aarch64/22519)._
