Fetching from the wire…
Infra2026-08-09 · source-backed
Released August 5, Qdrant 1.19 promotes TurboQuant from a secondary quantization layer to a primary storage datatype: Turbo4 keeps only the 4-bit representation, dropping from 36 bits per coordinate to 4. Ninefold reduction, plus fewer per-operation disk reads and writes. The post is unusually candid about the cost: without a full-precision copy Qdrant can't rescore top candidates, so Turbo4 is for disk-bound deployments while TurboQuant-over-full-precision stays correct when recall is the priority. Gain is proportionally larger for ColBERT-style multi-vector collections. Same release adds per-component memory tiers (cold/cached/pinned), prefix matching in keyword filters, per-query IDF for sparse search, deterministic sliced scroll, and a global quota API.
Each link below shares sources, entities, or timing with this story.
Mistral benchmarked against TurboQuant / Shared entity: Released August / Earlier coverage
Linked by a graph relationship (Mistral benchmarked against TurboQuant); both cover Released August; earlier Released August coverage from 2026-08-05.
TurboQuant built by Google Research / Shared entity: TurboQuant / Earlier coverage
Linked by a graph relationship (TurboQuant built by Google Research); both cover TurboQuant; earlier TurboQuant coverage from 2026-06-02.
Google released TurboQuant
Linked by a graph relationship (Google released TurboQuant).
Linked by a graph relationship (Google released TurboQuant).
TurboQuant built by Google Research
Linked by a graph relationship (TurboQuant built by Google Research).
Google released TurboQuant / Shared entity: Same / Earlier coverage
Linked by a graph relationship (Google released TurboQuant); both cover Same; earlier Same coverage from 2026-08-07.
Linked by a graph relationship (Google released TurboQuant); both cover Same; earlier Same coverage from 2026-08-05.
Linked by a graph relationship (Google released TurboQuant); both cover Same; earlier Same coverage from 2026-08-05.