DACBench: A Benchmark Library for Dynamic Algorithm Configuration
DACBench is a benchmark library for Dynamic Algorithm Configuration. Its focus is on reproducibility and comparability of different DAC methods as well as easy analysis of the optimization process.
You can try out the basics of DACBench in Colab here without any installation. Our examples in the repository should give you an impression of what you can do with DACBench and our documentation should answer any questions you might have.
Installation
We recommend installing DACBench in a virtual environment, here with uv:
pip install uv
uv venv --python 3.10
source .venv/bin/activate
uv pip install dacbench
Instead of using pip, you can also use the GitHub repo directly:
pip install uv
git clone https://github.com/automl/DACBench.git
cd DACBench
uv venv --python 3.10
source .venv/bin/activate
git submodule update --init --recursive
make install
This command installs the base version of DACBench including the three small surrogate benchmarks. For any other benchmark, you may use a singularity container as provided by us (see next section) or install it as an additional dependency. As an example, to install the SGDBenchmark, run:
uv pip install dacbench[sgd]
You can also install all dependencies like so:
make install-dev
Containerized Benchmarks
DACBench can run containerized versions of Benchmarks using Singularity containers to isolate their dependencies and make reproducible Singularity images.
Building a Container
For writing your own recipe to build a Container, you can refer to dacbench/container/singularity_recipes/recipe_template
Install Singularity and run the following to build the (in this case) cma container
cd dacbench/container/singularity_recipes
sudo singularity build cma cma.def
Citing DACBench
If you use DACBench in your research or application, please cite us:
@inproceedings{eimer-ijcai21,
author = {T. Eimer and A. Biedenkapp and M. Reimer and S. Adriaensen and F. Hutter and M. Lindauer},
title = {DACBench: A Benchmark Library for Dynamic Algorithm Configuration},
booktitle = {Proceedings of the Thirtieth International Joint Conference on
Artificial Intelligence ({IJCAI}'21)},
year = {2021},
month = aug,
publisher = {ijcai.org},
Metadata
Release files for DACBench 0.5.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dacbench-0.5.5.tar.gz | 4.4 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dacbench-0.5.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.8 MB
Release files / dacbench-0.5.5.tar.gz
| Download URL | dacbench-0.5.5.tar.gz |
|---|---|
| Size | 4.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6b703bbd421d75a4a44bdcd38e323dbe0808c96a703c9dce7046bc267b9a77fe
|
|
BLAKE2b-256 checksum How to use checksums |
0121abe53b3171d024b8c57fb77ecbcf2a8ac71ac0d165bd1e10062a611ce8df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2026.
Transparency logRelease files / dacbench-0.5.5-py3-none-any.whl
| Download URL | dacbench-0.5.5-py3-none-any.whl |
|---|---|
| Size | 3.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
66b2a8f12b2fe137041db8568c32968c6518d90ecc5cf5eedfacdca3ce3e17a0
|
|
BLAKE2b-256 checksum How to use checksums |
d7a0dd27eee30f3a5f2be56af99cf8d8854b3c43e657267231e469d8703f230e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2026.
Transparency log