majentik/Nemotron-3-Nano-30B-A3B-RotorQuant-GGUF-IQ4_XS overview
TIP KV cache quantization without any fork recommended, 2026 : upstream llama.cpp/Ollama now cover this natively — use ctk q8 0 ctv q8 0 ~half KV memory, negli…
Runs locally from ~16.96 GB disk (24 GB VRAM class GPUs with llama.cpp / guIDE).
Repository Files & Downloads
| File | Type | Quantization | Size | Link |
|---|---|---|---|---|
| Nemotron-3-Nano-30B-A3B-RotorQuant-IQ4_XS.gguf | GGUF | IQ4_XS | 16.96 GB | Download |
Model Details
| Model ID | majentik/Nemotron-3-Nano-30B-A3B-RotorQuant-GGUF-IQ4_XS |
|---|---|
| Author | majentik |
| Pipeline | text-generation |
| License | other |
| Base model | nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B-BF16 |
| Last modified | 2026-07-20T16:09:24.000Z |
Model README
---
license: other
license_name: nvidia-open-model-license
license_link: https://developer.download.nvidia.com/licenses/nvidia-open-model-license-agreement-june-2024.pdf
base_model: nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B-BF16
tags:
- gguf
- rotorquant
- kv-cache-quantization
- nemotron
- nvidia
- mamba2
- hybrid
- moe
- llama-cpp
- quantized
library_name: gguf
pipeline_tag: text-generation
---
> [!TIP]
> KV-cache quantization without any fork (recommended, 2026): upstream
> llama.cpp/Ollama now cover this natively — use -ctk q8_0 -ctv q8_0
> (~half KV memory, negligible quality loss: perplexity +0.002–0.05) or
> -ctk q4_0 -ctv q4_0 (~quarter memory, ≈7.6% perplexity increase). In
> Ollama: OLLAMA_KV_CACHE_TYPE=q8_0 with OLLAMA_FLASH_ATTENTION=1. Keep
> K and V types symmetric to stay on the fast fused Flash-Attention path.
> Since April 2026, mainline llama.cpp also applies Hadamard rotation to
> KV activations (PR #21038),
> which greatly improves low-bit KV quality (opt-out:
> LLAMA_ATTN_ROT_DISABLE=1).
>
> The RotorQuant/TurboQuant fork flow below is experimental/legacy: the
> TurboQuant llama.cpp PR was closed without merging (June 2026) and the fork
> is unmaintained relative to mainline. It is NOT required to use this model.
<!-- kv-upstream-note -->
Nemotron-3-Nano-30B-A3B-RotorQuant-GGUF-IQ4_XS
GGUF IQ4_XS weight-quantized variant of nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B-BF16 optimised for use with RotorQuant KV cache compression via a dedicated llama.cpp fork.
> Important: RotorQuant KV cache types (planar3, iso3) are not available in upstream llama.cpp, standard Ollama, or LM Studio.
> They require a specific llama.cpp fork.
> The GGUF file itself is a standard GGUF and works with any llama.cpp-compatible runtime using normal KV cache types (f16, q8_0, q4_0, etc.).
Hardware compatibility
| Device | VRAM / RAM | Recommendation |
| --- | --- | --- |
| CPU host with ≥16 GB RAM | ~16.5 GB | works via llama.cpp; slower than GPU but no accelerator required |
| Apple Silicon (Metal) | ~18.0 GB | llama.cpp Metal backend; fast on M-series unified memory |
| NVIDIA GPU (partial offload) | split between GPU + RAM | offload as many layers as VRAM allows; rest on CPU |
Overview
This model combines two independent compression techniques:
| Technique | What it does | Requirement |
|-----------|-------------|-------------|
| GGUF IQ4_XS weight quantization | Reduces model size from ~60 GB (BF16) to ~15.0 GB | Any llama.cpp-compatible runtime |
| RotorQuant KV cache compression — block-diagonal Clifford-algebra rotors for 3-bit KV cache (--cache-type-k iso3 --cache-type-v iso3) | Block-diagonal rotations / random rotation for compressed KV cache | llama-cpp-turboquant fork only |
Quickstart
Option A — RotorQuant KV cache (experimental fork — not required)
You must build from the RotorQuant-enabled llama.cpp fork:
# Clone and build the fork
git clone https://github.com/johndpope/llama-cpp-turboquant.git
cd llama-cpp-turboquant && git checkout feature/planarquant-kv-cache
# CUDA (Windows/Linux)
cmake -B build -DGGML_CUDA=ON -DCMAKE_BUILD_TYPE=Release && cmake --build build -j
# Metal (Apple Silicon)
cmake -B build -DGGML_METAL=ON -DGGML_METAL_EMBED_LIBRARY=ON -DCMAKE_BUILD_TYPE=Release && cmake --build build -j
# Run with RotorQuant KV cache
./build/bin/llama-cli -m Nemotron-3-Nano-30B-A3B-RotorQuant-GGUF-IQ4_XS.gguf \
--cache-type-k iso3 --cache-type-v iso3 \
-ngl 99 -fa \
-p "Explain quantum computing"
# Or run as a server
./build/bin/llama-server -m Nemotron-3-Nano-30B-A3B-RotorQuant-GGUF-IQ4_XS.gguf \
--cache-type-k iso3 --cache-type-v iso3 \
-ngl 99 -fa --jinja
Option B — With standard llama.cpp / LM Studio / Ollama
The GGUF works as a normal quantised model. You won't get RotorQuant-specific KV cache benefits, but standard KV cache quantization (q8_0, q4_0) still reduces VRAM significantly.
llama.cpp (upstream)
llama-cli -m Nemotron-3-Nano-30B-A3B-RotorQuant-GGUF-IQ4_XS.gguf \
--cache-type-k q8_0 --cache-type-v q8_0 \
-ngl 99 -fa \
-p "Explain quantum computing"
LM Studio
- Download the GGUF file and load in LM Studio.
- Enable Developer Mode (Settings → Developer).
- In the model loader's advanced settings, set Flash Attention to ON.
- Set K Cache Quantization and V Cache Quantization to
q8_0(orq4_0for more aggressive VRAM savings). - Note: LM Studio does not currently support RotorQuant's
iso3cache types. Track this feature request for updates.
Ollama
# Standard Ollama does not support RotorQuant cache types.
# Use with default or q8_0 KV cache via OLLAMA_KV_CACHE_TYPE=q8_0
OLLAMA_KV_CACHE_TYPE=q8_0 OLLAMA_FLASH_ATTENTION=1 ollama run majentik/Nemotron-3-Nano-30B-A3B-RotorQuant-GGUF-IQ4_XS
Specifications
| Property | Value |
|----------|-------|
| Base Model | nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B-BF16 |
| Architecture | Mamba-2 + Transformer hybrid Sparse MoE |
| Parameters | 30.7B total, 3.2B active per token |
| Context Length | 1M |
| Weight Quantization | GGUF IQ4_XS (importance-weighted 4-bit, smallest 4-bit) |
| Original Size (BF16) | ~60 GB |
| Quantized File Size | ~15.0 GB |
| KV Cache (RotorQuant) | 3-bit via --cache-type-k iso3 --cache-type-v iso3 (fork only) |
| KV Cache (standard) | q8_0, q4_0, f16, etc. (any llama.cpp runtime) |
| License | other |
| Modalities | Text only |
| Compatible Runtimes | llama.cpp, LM Studio, Ollama, koboldcpp |
About the RotorQuant / TurboQuant labels
RotorQuant and TurboQuant are this project's release labels, not distinct
quantization algorithms — for any given tier, both brand repos carry
byte-identical weights produced with the standard MLX / llama.cpp quantizers.
No brand-specific speedup is claimed or measured. The KV-cache fork these
labels originally referred to is legacy; for KV-cache memory savings use the
upstream options described above (-ctk/-ctv q8_0, OLLAMA_KV_CACHE_TYPE).
Current Status of RotorQuant in the Ecosystem
| Runtime | RotorQuant Support | Standard KV Quant |
|---------|---------------------|-------------------|
| llama.cpp (upstream) | ❌ Not merged | ✅ q8_0, q4_0, q4_1, iq4_nl, q5_0, q5_1 |
| llama-cpp-turboquant fork | ✅ planar3, iso3 | ✅ All standard types |
| LM Studio | ❌ Requested | ✅ Via advanced settings |
| Ollama | ❌ Not supported | ✅ Via OLLAMA_KV_CACHE_TYPE |
| koboldcpp | ❌ Not supported | ✅ Standard types |
Recommended Settings
For VRAM-constrained setups, standard q8_0 KV cache quantization already halves KV cache memory with negligible quality impact. Flash Attention should always be enabled — it is required for V cache quantization and improves memory efficiency regardless.
| VRAM | Suggested Configuration |
|------|------------------------|
| 24 GB (RTX 4090) | IQ4_XS + q8_0 KV cache + Flash Attention, 8K–16K context |
| 16 GB | IQ4_XS + q4_0 KV cache + Flash Attention, 4K–8K context |
| 48+ GB | IQ4_XS + f16 KV cache, full 32K+ context |
See Also
Run majentik/Nemotron-3-Nano-30B-A3B-RotorQuant-GGUF-IQ4_XS with guIDE
Download guIDE — the AI-native code editor with local LLM inference and 69 built-in tools.
Source: Hugging Face · Compare models