Struct BenchIsolation 

pub struct BenchIsolation {
    pub qdrant_collection: String,
    pub sqlite_db_path: PathBuf,
}

Per-scenario storage isolation for benchmark runs.

Before each scenario starts, call reset to delete and recreate the bench-namespaced SQLite database so earlier scenario memories cannot contaminate later ones.

Collection naming

The Qdrant collection name follows the pattern bench_{dataset}_{run_id}. Production collections (zeph_memory, zeph_skills, etc.) are never touched.

Examples

use std::path::Path;
use zeph_bench::BenchIsolation;

let iso = BenchIsolation::new("locomo", "run-2026-01-01", Path::new("/data/bench"));
assert_eq!(iso.qdrant_collection, "bench_locomo_run-2026-01-01");
assert!(iso.sqlite_db_path.ends_with("bench-run-2026-01-01.db"));

Fields

qdrant_collection: String

Qdrant collection name: bench_{dataset}_{run_id}.

sqlite_db_path: PathBuf

Absolute path to the bench-namespaced SQLite database.

Implementations

impl BenchIsolation

pub fn new(dataset: &str, run_id: &str, data_dir: &Path) -> Self

Create a new isolation context for a benchmark run.

The Qdrant collection is named bench_{dataset}_{run_id} and the SQLite database is placed at {data_dir}/bench-{run_id}.db.

Note

dataset and run_id are not sanitized. Callers should use alphanumeric values (plus hyphens/underscores) to ensure a valid Qdrant collection name and a safe filesystem path component.

pub async fn reset(&self) -> Result<(), BenchError>

Reset isolation state for a fresh scenario run.

Deletes the SQLite database file at sqlite_db_path if it exists, so memories from a previous scenario cannot bleed into the next one.

Qdrant isolation is currently a no-op: zeph-bench does not depend on qdrant-client, so collection cleanup must be performed externally if needed. The collection is overwritten on the next run anyway.

Errors

Returns BenchError::Io if the SQLite file exists but cannot be deleted.