Einsum Benchmark Data
Benchmark data repository accompanying the paper: "Einsum Benchmark: Enabling the Development of Next-Generation Tensor Execution Engines". It includes a package to easily work with the benmark data and all methods we used to convert and create our instances so you can create new ones yourself.
Installation
Install the base package with Python 3.10 through 3.14:
pip install einsum_benchmark
Basic Usage
Now you can load and run an instance like this:
import opt_einsum as oe
import einsum_benchmark
instance = einsum_benchmark.instances["qc_circuit_n49_m14_s9_e6_pEFGH_simplified"]
opt_size_path_meta = instance.paths.opt_size
print("Size optimized path")
print("log10[FLOPS]:", round(opt_size_path_meta.flops, 2))
print("log2[SIZE]:", round(opt_size_path_meta.size, 2))
result = oe.contract(
instance.format_string, *instance.tensors, optimize=opt_size_path_meta.path
)
print("sum[OUTPUT]:", result.sum(), instance.result_sum)
For more information please read our docs.
The code for our experiments is here: https://github.com/ti2-group/einsum_benchmark_experiments
Acknowledgements
The broader data collection process included contributions from individuals whose data was transformed. We duly acknowledge the following for making their data publicly available:
- Fichte, Johannes; Hecher, Markus; Florim Hamiti: Model Counting Competition 2020
- Fichte, Johannes; Hecher, Markus: Model Counting Competition 2021 2022 2023
- Fichte, Johannes; Hecher, Markus; Woltran, Stefan; Zisser, Markus: A Benchmark Collection of #SAT Instances and Tree Decompositions
- Meel, Kuldeep S.: Model Counting and Uniform Sampling Instances
- Automated Reasoning Group at the University of California, Irvine: UAI Competitions
- Martinis, John M. et al.: Quantum supremacy using a programmable superconducting processor Dataset. Dryad.
Moreover, we thank the following authors of open source software used to generated instances:
Metadata
Release files for einsum_benchmark 0.1.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| einsum_benchmark-0.1.8.tar.gz | 75.4 kB | Without provenance | Details for einsum_benchmark-0.1.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| einsum_benchmark-0.1.8-py3-none-any.whl | Python 3 | none | any | Details for einsum_benchmark-0.1.8-py3-none-any.whl |
Total release size: 171.7 kB
Release files / einsum_benchmark-0.1.8.tar.gz
| Download URL | einsum_benchmark-0.1.8.tar.gz |
|---|---|
| Size | 75.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba8ad0d3eff39005297a4c1958d1a8c1d0d4c40c52bb0c055ccd52e566acf773
|
|
BLAKE2b-256 checksum How to use checksums |
fbca3602fa3693293ed27172344ca6573cff09ce37a26fc41b795e819f18a070
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
pdm/2.22.3 CPython/3.13.1 Darwin/25.5.0
|
Release files / einsum_benchmark-0.1.8-py3-none-any.whl
| Download URL | einsum_benchmark-0.1.8-py3-none-any.whl |
|---|---|
| Size | 96.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8285ef68a0c3388a63896d5cc4d43befac59b8a56d986c6d8ebe93c53f208731
|
|
BLAKE2b-256 checksum How to use checksums |
3849cfda411e0d15926bb2e4f44b5666cfd6367fe0b0a3452a54f6bbbbc530da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
pdm/2.22.3 CPython/3.13.1 Darwin/25.5.0
|
Security for einsum_benchmark 0.1.8
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.