Wind tunnel infrastructure: design, harness, and Criterion benchmarks - #10
Merged
Conversation
…ipfian vocab, query fixtures) using rapidhash::v1
This was referenced May 30, 2026
…paths)
Completes ITER-0000 walking skeleton (T6-T9) atop the leit_wind_tunnel
harness:
- leit_wind_tunnel_index: index_build/{1k,10k} indexing-throughput benches
- leit_wind_tunnel_query: five execution paths (single/OR/AND/fielded +
BM25F cross-field) x {1k,10k}, index built once outside the timed region,
ExecutionWorkspace reused across iterations
- Criterion isolated to the two bench crates (dev-dependencies only);
primary crates and leit_benchmark untouched
- CI: exclude the three wind-tunnel crates from the no_std/wasm jobs
(std-only, mirroring leit_benchmark); no cargo bench step added
- harness docs: note the relationship to leit_benchmark (smoke test vs
performance lab)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the wind tunnel — the Phase 2 performance-measurement foundation: a deterministic synthetic corpus generator plus Criterion benchmarks over the existing Phase 1 search stack, across indexing and all five query execution paths. This is the baseline all later Phase 2 performance work measures against.
What's included
docs/2026-05-04-wind-tunnel-infrastructure-design.md) — the infrastructure spec.leit_wind_tunnel(harness,publish = false) — deterministicCorpusGenerator(seededrapidhash::v1, byte-identical from a seed), Zipfian vocabulary (s=1.0, 500 words, CDF + binary search), and query fixtures (single-term / OR / AND / fielded / BM25F cross-field).leit_wind_tunnel_index+leit_wind_tunnel_query(Criterion bench crates,publish = false) — indexing throughput (index_build/{1k,10k}) and query latency across the five execution paths at 1K/10K corpus sizes. Index built once outside the timed region;ExecutionWorkspacereused across iterations.Dependency & CI isolation
[dev-dependencies]; the primary crates andleit_benchmarkare unchanged (no Criterion in their graphs).[dependencies]; test/bench-only →[dev-dependencies]).clippy-no-std.shhook, mirroringleit_benchmark.Testing
cargo bench -p leit_wind_tunnel_index/-p leit_wind_tunnel_queryproduce Criterion statistical output + HTML reports.