This directory contains benchmarks implemented for usage with airspeed velocity asv benchmarking package. Refer to asv documentation for information on how to use it.

The asv.conf.json file in this directory configures asv to work correctly with QCoDeS.

If you already have a python environment set up for QCoDeS, then run the following command from this directory:

asv run --python=same

If you do not have an environment set, then asv can set it up automatically. The benchmarks are executed in the same way:

asv run

Either of the commands above will execute benchmarking for the latest commit of the main branch.

If you want to run benchmarking for a particular commit, use the same syntax as there is used for git log (commit id with ^! at the end; note that in some terminals you will need to type ^ two times like this ^^!):

asv run ed9b6fe8^!

Use the --bench option with a regular expression to tell asv which benchmarks you would like to execute. For example, use the following syntax to execute a benchmark called saving in data.py benchmark module:

asv run --bench data.saving

Refer to asv documentation for more information on the various ways the benchmarking can be executed (for example, how to run a particular benchmark, how to compare results between commits, etc).

In order to view the benchmarking results, execute the following command to generate a convenient website

asv publish

and the following command to start a simple server that could host the website locally (the generated website is not static, hence the server is needed)

asv preview -b

The -b option opens the website automatically in your default browser (the URL that it opens automatically is also printed to the terminal). In order to stop the server, press Ctrl+C in the terminal where you've started it.

Note that the benchmarking results are created locally on your machine, and they get accumulated.

In order to compare benchmarking results of two commits, use the following command (note that the benchmarking results for these two commits should already exist):

asv compare ed859c0a 8984aefb

If you would like to also profile while benchmarking in order to get more insights on the performance of the code, use either

asv run --profile

command or

asv profile

command.

In case you would like to use a visualization tool for the profile results, you can install one, for example, snakeviz, and run benchmarking with profiling as follows:

asv profile --gui=snakeviz

• host results and their html representation (GitHub pages?)