[inimaz]

Description

asv is used to run a performance test across commits, to see the evolution of a metric.
See for example:

• numpy

It is very useful to see if something is slowing down the crutial actions. In our case for instance, I have added 3 tests:

• Time for tracker.start()
• Time for tracker.stop()
• Time for full cycle of tracker.start() and tracker.stop()

See the README for some useful commands.
The script ./benchmarks/get_release_hashes.sh gets the commits of the releases, like this it is faster to run the benchmark.
By doing
uvx asv --config benchmarks/asv.conf.json run HASHFILE:release_hashes.txt --show-stderr
Then

 uvx asv --config benchmarks/asv.conf.json publish
 uvx asv --config benchmarks/asv.conf.json preview

To see the live page and explore the tests.

Screenshots (if appropriate):

Tested in my laptop

Types of changes

• New feature (non-breaking change which adds functionality)

AI Usage Disclosure

Please refer to docs/how-to/ai-policy.md for detailed guidelines on how to disclose AI usage in your PR. Accurately completing this section is mandatory.

• 🟥 AI-vibecoded: You cannot explain the logic. Car analogy : the car drive by itself, you are outside it and just tell it where to go.
• 🟠 AI-generated: Car analogy : the car drive by itself, you are inside and give instructions.
• ⭐ AI-assisted. Car analogy : you drive the car, AI help you find your way.
• ♻️ No AI used. Car analogy : you drive the car.

[SaboniAmine]

Looks good thanks! Should this run in the package release CI job ?

[inimaz]

Looks good thanks! Should this run in the package release CI job ?

We are not publishing the results anywhere for now, I was thinking on using it as a debug thing first. It is true that we can run it on each release and publish it somewhere... Creating a follow up issue for this :D