Interview with RaBitQ Authors: The TurboQuant Dispute and Why the Storage Selloff Was a False Alarm
Apr 17, 2026Cheng Long, Jianyang Gao, Li Liu

Summary
This post details the technical debate surrounding vector quantization, specifically comparing RaBitQ and TurboQuant. It highlights RaBitQ's theoretical optimality and its adoption in Milvus (as IVF_RABITQ) and other systems. The post also critiques TurboQuant's benchmark methodology and claims, emphasizing the importance of fair comparisons and the foundational role of random rotation in RaBitQ. It discusses how vector quantization impacts AI infrastructure costs by enabling efficient compression for vector search and KV cache compression.
More from the AI Data Storage Engine trail
- Milvus Snapshots: Point-in-Time Collection Views Without Copying Data
- Announcing Milvus 3.0: Lake-Native Vector Search and a More Powerful Retrieval Engine
- How to Recover Milvus Data After etcd Corruption Without a Backup
- Open Tag: An Open-Source Claude Tag for Claude Code and Codex
- How Force Merge Compaction Nearly Doubled Milvus Search QPS