feat(proximity): add native TurboQuant accelerator - #112
Conversation
|
Qualification update (0d1b3a9): fixed the cross-target conformance failure by replacing host-libm-generated fixture inputs with frozen IEEE-754 bit inputs; added an independent dense Gaussian-QR development oracle with retained 128/200/768/1536/3072 × 2/3/4-bit distortion and recall evidence; and added ordinal fault injection over every discovered TurboQuant publication, cold verification, forced search/rerank, and proof/closure store boundary. Focused tests and warnings-denied Clippy pass locally. Auto remains intentionally disabled and production-scale qualification/legal gates remain open. |
|
Retained qualification update (379463d): corrected accelerator sidecar accounting to exclude referenced authoritative source objects; regenerated the 1K × five-dimension × three-metric default-path runs from committed harness revision d734772; and checked in the raw CSVs plus a bounded-tier report. All 15 TurboQuant recall@10 rows are 1.0 and match PQ, but TurboQuant search and derived size are worse on this fixture, so Auto remains disabled. Production-scale, cross-host/release-command, and legal gates remain open. |
|
Performance and conformance update: 60dfaa7 replaces per-coordinate generic unpacking with canonical width-specialized 2/3/4-bit decoding. On the retained 1K L2 arm64 tier, scalar scan improved about 33–44% across dimensions (36–37% at 768/1536) with unchanged 1.0 recall. c701192 refreshes the raw evidence, and e3cd7df adds a browser-WASM test that reproduces the checked-in Rust descriptor and TurboQuant manifest CIDs. Auto remains disabled because current scan/size results still do not meet its comparative gates. |
Summary
Autodisabled and expose TurboQuant only through explicit backend selection while mandatory release gates remain open.Correctness and verification
Passed locally:
cargo fmt --all -- --checkgit diff --checkcargo clippy --all-targets --all-features -- -D warningsSchema-4 evidence
Eleven focused cells at implementation revision
729c2ffacover 10K/100K × 768, all metrics at four bits and 8× reranking, matching 16× cosine/product diagnostics, and exhaustive 10K cosine.Exhaustive 10K cosine returns 1.00 recall for both implementations. A qualification-scale Rust regression proves the default failure is unavoidable under the frozen contract: the authoritative exact top 10 all share one packed code with 222 lower-key records, while the shortlist cap is 80 and ties order by key. The approved 16× window still returns 0.00 at 10K; 100K cosine and inner product reach 1.00 at 16×.
TurboQuant builds faster than PQ in every sampled row, but search and sidecar-size gates fail. Full details and raw artifacts are in the schema-4 report.
Release status
This PR remains a draft. Open gates are:
The feature-specific proximity and fuzz checks pass. Current unrelated DynamoDB/S3 workflow failures are inherited repository issues and are not hidden by this PR.