RRepoGEO

REPOGEO REPORT · LITE

TheTom/turboquant_plus

Default branch main · commit 7f601a13 · scanned 6/20/2026, 2:53:30 AM

GitHub: 6,951 stars · 925 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
23 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 0 warn · 1 fail
Objective metadata checks
AI knows your name
2 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface TheTom/turboquant_plus, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highabout#1
    Add a clear repository description

    Why:

    COPY-PASTE FIX
    Research and reference implementation for TurboQuant+, a KV cache compression technique for large language models (LLMs) using PolarQuant and Walsh-Hadamard rotation, achieving 3.8-6.4x compression.
  • hightopics#2
    Add relevant topics for LLM optimization

    Why:

    COPY-PASTE FIX
    llm, kv-cache, transformer, quantization, compression, machine-learning, deep-learning, vllm, llama-cpp, long-context
  • highreadme#3
    Move core value proposition to the top of the README

    Why:

    CURRENT
    # TurboQuant+
    
    > 🚀 TurboQuant KV cache compression is now in vLLM (PR #38479, merged April 2026): `--kv-cache-dtype turboquant_k8v4` and friends, with fused Triton store/decode kernels. The PR discussion drew on the asymmetric K/V findings from this repo. **Upstream llama.cpp has merged the core idea too**: Hadamard KV cache rotation (#21038, citing TurboQuant directly) with fast WHT kernels on CPU (#22631), CUDA (#23615), and Vulkan (#23687). Rotation + the stock q4_0 cache is essentially turbo4's rotation stage; the PolarQuant codebook, norm extraction, and asymmetric policies remain here and in the fork.
    
    > ### [Getting Started Guide](docs/getting-started.md) | [Configuration Recommendations](docs/turboquant-recommendations.md) | [Benchmarks](docs/benchmarks.md) | Commercial Support
    
    Implementation of TurboQuant (ICLR 2026) with implementation work, experiments, and follow-on findings beyond the base paper. Compresses transformer KV cache **3.8-6.4x** using PolarQuant + Walsh-Hadamard rotation, at near q8_0 prefill speed and ~0.9x decode throughput at long context. Validated end-to-end from 1.5B to **104B at 128K context on a MacBook** (turbo3, PPL 4.024, 74 GB peak memory).
    
    This repository is the **research home**: the Python reference implementation, the validation papers, and the benchmark data. To run TurboQuant in an inference engine, pick from the table below. Pieces that prove useful and stable get upstreamed incrementally as small, reviewable patches.
    COPY-PASTE FIX
    # TurboQuant+
    
    Implementation of TurboQuant (ICLR 2026) with implementation work, experiments, and follow-on findings beyond the base paper. Compresses transformer KV cache **3.8-6.4x** using PolarQuant + Walsh-Hadamard rotation, at near q8_0 prefill speed and ~0.9x decode throughput at long context. Validated end-to-end from 1.5B to **104B at 128K context on a MacBook** (turbo3, PPL 4.024, 74 GB peak memory).
    
    > 🚀 TurboQuant KV cache compression is now in vLLM (PR #38479, merged April 2026): `--kv-cache-dtype turboquant_k8v4` and friends, with fused Triton store/decode kernels. The PR discussion drew on the asymmetric K/V findings from this repo. **Upstream llama.cpp has merged the core idea too**: Hadamard KV cache rotation (#21038, citing TurboQuant directly) with fast WHT kernels on CPU (#22631), CUDA (#23615), and Vulkan (#23687). Rotation + the stock q4_0 cache is essentially turbo4's rotation stage; the PolarQuant codebook, norm extraction, and asymmetric policies remain here and in the fork.
    
    > ### [Getting Started Guide](docs/getting-started.md) | [Configuration Recommendations](docs/turboquant-recommendations.md) | [Benchmarks](docs/benchmarks.md) | Commercial Support
    
    This repository is the **research home**: the Python reference implementation, the validation papers, and the benchmark data. To run TurboQuant in an inference engine, pick from the table below. Pieces that prove useful and stable get upstreamed incrementally as small, reviewable patches.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface TheTom/turboquant_plus
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
huggingface/optimum
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. huggingface/optimum · recommended 2×
  2. huggingface/transformers · recommended 2×
  3. tensorflow/tensorflow · recommended 2×
  4. vllm-project/vllm · recommended 1×
  5. microsoft/DeepSpeed · recommended 1×
  • CATEGORY QUERY
    How to reduce transformer KV cache memory usage for long context LLMs?
    you: not recommended
    AI recommended (in order):
    1. vLLM (vllm-project/vllm)
    2. DeepSpeed-MII (microsoft/DeepSpeed)
    3. Hugging Face Optimum (huggingface/optimum)
    4. Triton Inference Server (triton-inference-server/server)
    5. FasterTransformer (NVIDIA/FasterTransformer)
    6. Hugging Face Transformers (huggingface/transformers)
    7. LongFormer
    8. BigBird
    9. FlashAttention-2 (Dao-AILab/flash-attention)
    10. PyTorch (pytorch/pytorch)
    11. TensorFlow (tensorflow/tensorflow)

    AI recommended 11 alternatives but never named TheTom/turboquant_plus. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for methods to efficiently run large language models on devices with limited RAM.
    you: not recommended
    AI recommended (in order):
    1. llama.cpp (ggerganov/llama.cpp)
    2. AWQ (mit-han-lab/awq)
    3. GPTQ (IST-DASLab/gptq)
    4. bitsandbytes (TimDettmers/bitsandbytes)
    5. Hugging Face Transformers (huggingface/transformers)
    6. accelerate (huggingface/accelerate)
    7. TinyLlama (PKU-YuanGroup/TinyLlama)
    8. LoRA (microsoft/LoRA)
    9. Hugging Face PEFT library (huggingface/peft)
    10. ONNX Runtime (microsoft/onnxruntime)
    11. OpenVINO (openvinotoolkit/openvino)
    12. TensorFlow Lite (tensorflow/tensorflow)
    13. Hugging Face Optimum (huggingface/optimum)

    AI recommended 13 alternatives but never named TheTom/turboquant_plus. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    fail

    Suggestion:

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of TheTom/turboquant_plus?
    pass
    AI did not name TheTom/turboquant_plus — likely talking about a different project

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts TheTom/turboquant_plus in production, what risks or prerequisites should they evaluate first?
    pass
    AI named TheTom/turboquant_plus explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo TheTom/turboquant_plus solve, and who is the primary audience?
    pass
    AI named TheTom/turboquant_plus explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of TheTom/turboquant_plus. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/TheTom/turboquant_plus.svg)](https://repogeo.com/en/r/TheTom/turboquant_plus)
HTML
<a href="https://repogeo.com/en/r/TheTom/turboquant_plus"><img src="https://repogeo.com/badge/TheTom/turboquant_plus.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

TheTom/turboquant_plus — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite