cc49704791
Topology ablation bench: read YAMS_BENCH_DAEMON_DATA_DIR so multiple daemon spawns can share a stable data_dir. Lets the topology tuner's persisted MAB state carry over between bench reps; without this, every fresh DaemonHarness spawn cold-starts UCB1 and picks the alphabetically- first arm. Pairs with the TopologyTuner persistence (already on HEAD). Bench also gains per-surface vector-leg counters (vec_unique_doc_counts, topology_weak_routing_applied, vector_tier_skip_reason, embedding_status, vector_db_dim/query_embedding_dim) and a modeOf reducer for categorical metrics — Phase F1-era richer attribution carried forward. Docs: AGENTS.md / daemon_architecture / retrieval_precision_optimization / PROMPT-eng-codex updates from the parallel sessions. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| e1_per_component_telemetry.md | ||
| e7_adaptive_threshold.md | ||
| longmemeval_s_baseline.md | ||
| multi_client_optimization_loop.md | ||
| performance_report.md | ||
| README.md | ||
| retrieval_precision_optimization.md | ||
| storage_backends.md | ||
Benchmarks
This section is the public benchmark index for YAMS.
Each page should answer three things:
- what workload or dataset was measured,
- what the latest published results are,
- how to run the benchmark locally.
Benchmark Docs
- Performance Report - canonical ingestion, metadata, IPC, and multi-client baseline tables plus run commands.
- LongMemEval_S Retrieval Quality Baseline - dataset statistics, retrieval-quality baselines, and the benchmark command.
- Storage Backends Benchmark - local vs R2 CLI CRUD and multi-client benchmark results.
- Multi-Client Optimization Loop - throughput/stability runbook plus summary and regression commands.
- Retrieval Precision Optimization - ranking-quality tuning loop and summary workflow.
Scope
- Public benchmark docs focus on benchmark data, workload context, and reproducible commands.
- Internal harness plumbing and generated artifacts are intentionally omitted from public docs.
testedmeans the path is validated in this repository.supportedmeans the path exists but is not currently part of automated validation here.
When in doubt, treat tested paths as the default reference point.