AI Ecosystem Benchmark
Generalized framework for benchmarking AI tools that depend on database backends.
Python Package
This repository is also a Python package named ai-ecosystem-benchmark. The
package is intentionally minimal for now while the benchmark framework takes
shape.
Install and sync the development environment with uv:
uv sync
Run the local checks:
uv run pytest
uv run ruff check .
uv run ruff format --check .
uv run mypy
uv run deptry .
Install pre-commit hooks once per checkout:
uv run pre-commit install
Implementing a Workload
Benchmark workloads should subclass BaseBenchmarkWorkload and implement the
required lifecycle hooks:
setup(): prepare clients, data, or other state before benchmarks run.between_benchmarks(): reset or pause between benchmark executions.teardown(): clean up resources after benchmarks finish.
Connection strings are optional. If a connection string is omitted, that backend is assumed to be disabled for the benchmark run.
Backend-specific benchmark methods are discovered by name:
- Aerospike methods start with
aerospike - Postgres methods start with
postgres - Redis methods start with
redis
from ai_ecosystem_benchmark import BaseBenchmarkWorkload
class MyWorkload(BaseBenchmarkWorkload):
def __init__(
self,
aerospike_connection_string: str | None = None,
postgres_connection_string: str | None = None,
redis_connection_string: str | None = None,
) -> None:
super().__init__(
aerospike_connection_string=aerospike_connection_string,
postgres_connection_string=postgres_connection_string,
redis_connection_string=redis_connection_string,
)
def setup(self) -> None:
return None
def between_benchmarks(self) -> None:
return None
def teardown(self) -> None:
return None
def aerospike_test_insert(self) -> None:
...
def redis_test_lookup(self) -> None:
...
Infrastructure
The first infrastructure target is a GCP Compute Terraform stack that can provision any combination of Redis, Postgres, and Aerospike benchmark clusters. The GitHub Actions workflow in .github/workflows/terraform.yml runs Terraform manually through workflow_dispatch and prints non-sensitive endpoint details after apply.
See infra/terraform/gcp-compute/README.md for setup details.
License
This project is licensed under the Apache License 2.0. See LICENSE for details.
Metadata
Release files for ai-ecosystem-benchmark 0.0.6
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 | |
|---|---|---|---|---|
| ai_ecosystem_benchmark-0.0.6.tar.gz | 22.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ai_ecosystem_benchmark-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.8 kB
Release files / ai_ecosystem_benchmark-0.0.6.tar.gz
| Download URL | ai_ecosystem_benchmark-0.0.6.tar.gz |
|---|---|
| Size | 22.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1b68bbbea583037aa63f4c057985c1da0f64fe2ebc1acf1144dc45946e69163b
|
|
BLAKE2b-256 checksum How to use checksums |
57ce294919f8f30438be5c12e69c7aae4cfbcd0de4b629717fdd00da04981cfb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 11, 2026.
Transparency logRelease files / ai_ecosystem_benchmark-0.0.6-py3-none-any.whl
| Download URL | ai_ecosystem_benchmark-0.0.6-py3-none-any.whl |
|---|---|
| Size | 14.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d4629ae995cfcd58c7764fdea586a2fd3160e45edaccd6ae99063d4a11414c76
|
|
BLAKE2b-256 checksum How to use checksums |
8169eaf0c63e1040e8d00f90c52a5944d026c1a6daf9ba5ad8129ff27b53bf6c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 11, 2026.
Transparency logSecurity for ai-ecosystem-benchmark 0.0.6
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ai_ecosystem_benchmark-0.0.6.tar.gz
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 Jun 11, 2026.
Transparency logA 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.