The archive · Developer & Business Tools · Technical decision · 2026
TurboQuant+ squeezed LLM KV caches 3.8-6.4x and got merged into vLLM, llama.cpp, MLX
A solo developer's open-source implementation of TurboQuant KV-cache compression became merged upstream code in vLLM, llama.cpp and Apple MLX within months.
TurboQuant+ (TheTom/turboquant_plus)
What the business is
Apache-2.0 reference implementation and research home for TurboQuant-style KV-cache compression - PolarQuant codebooks, Hadamard rotation and asymmetric key/value policies - that mainline LLM inference engines merge in.
How it started
Tom Turney created TheTom/turboquant_plus on 2026-03-25 as an implementation of TurboQuant, the KV-cache compression scheme from Google Research's ICLR 2026 paper (arXiv 2504.19874): extract each vector's norm, rotate the residual with a Walsh-Hadamard transform plus random sign flips, then Lloyd-Max scalar-quantize to 2-4 bits per value. The README targets 3.8-6.4x cache compression at near q8_0 prefill speed and ~0.9x decode throughput on long context, validated end-to-end from 1.5B to 104B models at 128K context on a MacBook (turbo3, PPL 4.024, 74 GB peak memory).
What happened
The project quickly moved from reproduction to original research. Its headline findings - value-cache compression is nearly free, all quality loss comes from key compression, and boundary layers are disproportionately sensitive - produced asymmetric configurations (q8_0 keys plus turbo values) and layer-aware protection that rescued models symmetric compression broke. It also dropped the paper's QJL error-correction stage, arguing QJL 'eliminates reconstruction bias but amplifies variance,' a conclusion five independent groups later confirmed. Distribution went upstream: vLLM merged a TurboQuant attention backend in April 2026 (PR #38479, kv-cache-dtype turboquant_k8v4), llama.cpp merged Hadamard KV-cache rotation citing TurboQuant (PR #21038) plus CPU/CUDA/Vulkan WHT kernels, and Apple merged the asymmetric scheme family into mlx-swift-lm on 2026-07-20 (PR #232, 63 tests). Community ports followed - a llama.cpp production fork with prebuilt binaries, Lablup's Rust/MLX port, an independent PyTorch implementation - and the repo passed 7k stars and 900+ forks within five months.
How it ended up
Still live as of 2026-09-05: the technique now ships inside vLLM, llama.cpp and Apple MLX; a production fork (llama-cpp-turboquant) and several community products build on the stack, and the maintainer is preparing a full PolarQuant codec PR to llama.cpp (issue #27). Funding remains bootstrapped - GitHub Sponsors plus paid inference-optimization engagements - so the bet is winning on adoption, not revenue.
Background
In early 2026 the memory cost of KV caches was the wall for long-context LLM inference, so Tom Turney created TheTom/turboquant_plus on 2026-03-25 as an implementation of TurboQuant, Google Research's ICLR 2026 KV-cache compression scheme (arXiv 2504.19874): extract each vector's norm, rotate the residual with a Walsh-Hadamard transform, then quantize to 2-4 bits per value. He targeted 3.8-6.4x cache compression at near q8_0 prefill speed and ~0.9x decode throughput on long context, validated end-to-end from 1.5B to 104B models at 128K context on a MacBook.
The bet was distribution, not product: rather than build a competing engine, the repo was a research home and reference implementation whose win condition was upstream adoption. Experiments found value-cache compression nearly free, key precision dominant for quality, and boundary layers disproportionately sensitive, yielding asymmetric q8_0-key/turbo-value configs. The project also dropped the paper's QJL error-correction stage after five independent groups confirmed it amplified attention noise.
By September 2026 the strategy had landed. vLLM merged a TurboQuant KV-cache backend in April 2026 (PR #38479, turboquant_k8v4 and friends), llama.cpp merged Hadamard KV-cache rotation (PR #21038) with WHT kernels on CPU, CUDA and Vulkan, and Apple merged the asymmetric scheme family into mlx-swift-lm on 2026-07-20 (PR #232). The repo reached 7,018 stars and 927 forks; community ports and a production llama.cpp fork orbit it, funded by GitHub Sponsors and commercial support rather than venture capital.
What has to be true
- It treated upstream adoption as the product: small patches into vLLM, llama.cpp and MLX put the technique inside engines with existing users, instead of asking anyone to adopt a new runtime.
- The asymmetric K/V finding - compress values hard, protect keys - was a defensible contribution beyond the paper, and community tests on RTX 3090/4090, M1-M5 and RX 9070 XT built credibility.
- Validating on consumer gear (up to 104B at 128K context on a MacBook) proved the compression works where users actually feel the memory wall.
- Open research hygiene - dropping QJL after independent confirmation, publishing per-model configuration guidance - made engine maintainers trust the patches.
- Light-touch monetization (GitHub Sponsors, commercial support) matched an Apache-2.0 upstream-first strategy that needed no revenue to spread.
What can be applied
Win by becoming upstream: prove the paper on real hardware, publish the corrections, and land incremental patches in engines people already run - adoption, not a product of your own, is the KPI.
Aftermath
As of 2026-09-05 the project is live: 7,018 stars, 927 forks, 342 commits and 65 watchers. vLLM ships turboquant_k8v4 and friends behind --kv-cache-dtype; llama.cpp ships Hadamard rotation and WHT kernels on CPU, CUDA and Vulkan; Apple's mlx-swift-lm carries the asymmetric family with 63 tests. Around it sit a production fork with prebuilt binaries, Lablup's Rust MLX port, an independent PyTorch implementation and community products. Still open is a full PolarQuant codec PR to llama.cpp (#27); funding is GitHub Sponsors plus paid engagements, so the bet wins on adoption, not revenue.
Sources
- TheTom/turboquant_plus - README (7.0k stars, 927 forks, upstream status)
- [Attention Backend] TurboQuant: 2-bit KV cache compression with 4x capacity
- llama : rotate activations for better quantization
- add TurboQuant KV cache compression
spotted an error? The archive wants to know.
Your turn
You just read one. Describe what you are building, and see who is betting on the same thing.
Free account · 3 free questions · no card