RotorQuant Beats TurboQuant by 10-19x With 44x Fewer Parameters
Three days after Google's TurboQuant dropped, a community project called RotorQuant uses Clifford rotors to achieve 10-19x faster KV cache compression.
Vlad Makarovreviewed and published
44x fewer parameters. 10-19x faster execution. Three days — that's how long it took for the open-source community to take Google's TurboQuant and blow past it.
What Happened
RotorQuant appeared on r/LocalLLaMA this Wednesday and immediately grabbed attention, pulling 429 upvotes and 81 comments in its first day. The project takes Google's TurboQuant — which already cut KV cache memory by 6x with 8x speedup and zero accuracy loss — and rebuilds the core math using Clifford rotors, a technique borrowed from geometric algebra.
The result is a C++ implementation that runs 10-19x faster than TurboQuant while using 44 times fewer parameters. Where TurboQuant's rotation step relies on standard matrix operations, RotorQuant replaces them with Clifford rotor transformations that achieve the same effect through a fundamentally more compact representation.
KV cache compression remains the single biggest bottleneck for running large language models on consumer hardware. Every token a model processes adds to the cache, and that cache eats VRAM fast. Both TurboQuant and RotorQuant attack this problem, but RotorQuant's speedup means the compression step itself becomes nearly invisible in the inference pipeline.
Why This Matters
The community reaction tells the story. "Clifford rotors for quantization is genuinely clever," wrote one commenter — and the technical crowd on r/LocalLLaMA doesn't hand out compliments easily. TurboQuant benchmarks had already started appearing in llama.cpp (that post hit 280 upvotes), so RotorQuant arrives into an ecosystem already primed to adopt it.
For anyone running models locally — whether on an NVIDIA DGX Spark, a Mac Studio, or an Intel Arc Pro B70 — faster KV cache compression translates directly into longer context windows and snappier responses without buying new hardware. The 44x parameter reduction also means the compression overhead itself takes less memory, which matters when every megabyte counts on a 16GB or 32GB card.
What's Next
The most upvoted request in the thread: "Would love to see this on Apple Silicon." Given that MLX ports of TurboQuant appeared within 24 hours of its release, an Apple Silicon build of RotorQuant seems like a matter of days, not weeks. The C++ codebase should make porting straightforward, and the local LLM community has proven it moves fast when the gains are real.
