Gemma 4 E4B — ~3× lower KL than Google's official W4A16 QAT
2
18 commits
1 linked in READMEs
updated Oct 15, 2026
Native QUASAR W4A16-G64 checkpoint for vLLM: 0.022 vs 0.064 KL to BF16, higher point estimates on all 8 downstream benchmarks, and +36% H100 output throughput in our vLLM configuration, versus Google's official W4A16 QAT.
| W4A16 | KL to BF16 ↓ | Top-1 agreement ↑ | Top-1 on hard tokens ↑ | quantized bpw |
|---|---|---|---|---|
| QUASAR (g64) | 0.022 | 95.5% | 86.9% | 4.25 |
| Google QAT (g32) | 0.064 | 92.6% | 78.9% | 4.5 |
Hard tokens are positions where BF16's top-1 probability is below 0.9. Same 512 held-out prompts and BF16 reference for both checkpoints.
vllm serve QUASAR-QAT/gemma-4-E4B-it-QUASAR-W4A16-G64 --dtype float16
Standard compressed-tensors W4A16. Text and image input; 128K context. For llama.cpp / Ollama / LM Studio, use the GGUF twin.
In our vLLM 0.28 test on one H100, group-64 dispatches to the Machete kernel while Google's group-32 goes to Marlin: 4,225 vs 3,111 output tokens/s at the same batch. Single-request latency is at parity.
Higher point estimates on all 8 downstream benchmarks than Google's QAT model.
| Benchmark | QUASAR | Google QAT |
|---|---|---|
| TriviaQA | 23.8 | 20.1 |
| NQ-open | 4.7 | 2.4 |
| TruthfulQA | 58.2 | 55.4 |
| ARC-Easy | 79.8 | 78.3 |
| ARC-Challenge | 56.2 | 56.0 |
| GSM8K | 82.0 | 81.5 |
| IFEval | 82.6 | 81.9 |
| MATH-hard | 60.7 | 59.4 |
| Average | 56.0 | 54.4 |
Same harness and backend for both checkpoints; full configs, BF16 results and paired-bootstrap CIs are in EVAL.md.
| Benchmark | QUASAR | Google QAT |
|---|---|---|
| HMMT 2026 (avg@32) | 29.0 | 28.6 |
| AIME 2025 (avg@32) | 37.5 | 33.3 |
| SuperGPQA | 40.5 | 39.7 |
| OJBench Python | 18.1 | 17.7 |
| MRCR | 24.4 | 21.0 |
| MRCR ≥64K | 12.0 | 8.0 |
| MRCR 8-needle | 12.7 | 11.5 |
| LongProc-2k | 53.6 | 51.1 |
| LongBench-v2 | 40.4 | 39.8 |
Native QAT checkpoint: the INT4 codes come directly from training, rather than a post-training re-quantization. export_receipt.json verifies the export per tensor. The GGUF twin carries the same codes and scales and ships a --verify script that checks the two files against each other.
vllm serve QUASAR-QAT/gemma-4-E4B-it-QUASAR-W4A16-G64 --dtype float16 (tested on vLLM 0.28.0 and 0.29.0; --dtype float16 keeps the stored fp16 scales exact), then any OpenAI-compatible client. Text and image inputs; 131,072-token context.q/k/v/o/gate/up/down) int4 symmetric, group_size 64, fp16 scales, compressed-tensors pack-quantized; embeddings, norms, per-layer-input tables and the vision/audio towers untouched (bf16). 10.2 GB.QUASAR is loss-aware quantization-aware training. It improves the low-bit reconstruction during training, then exports to standard deployment formats with zero inference overhead.
This checkpoint was healed against the BF16 teacher for 626M tokens: one epoch over ~398k prompts self-distilled from BF16 Gemma 4 E4B-it with thinking on, fp32 master weights, INT4 group-64.
Based on Gemma 4 by Google DeepMind. Upstream LICENSE/NOTICE apply.
@article{counathe2026quasar,
title={QUASAR: Lowering the Loss Floor of Quantization-Aware Training with Loss-Aware Reconstruction},
author={Counathe, Vincent and Athiwaratkun, Ben and De Sa, Christopher and Zhang, Tianyi},
journal={arXiv preprint arXiv:2608.13966},
year={2026}
}
Gemma 4 E4B — ~3× lower KL than Google's official W4A16 QAT
2
18 commits
1 linked in READMEs
updated Oct 15, 2026
Native QUASAR W4A16-G64 checkpoint for vLLM: 0.022 vs 0.064 KL to BF16, higher point estimates on all 8 downstream benchmarks, and +36% H100 output throughput in our vLLM configuration, versus Google's official W4A16 QAT.
| W4A16 | KL to BF16 ↓ | Top-1 agreement ↑ | Top-1 on hard tokens ↑ | quantized bpw |
|---|---|---|---|---|
| QUASAR (g64) | 0.022 | 95.5% | 86.9% | 4.25 |
| Google QAT (g32) | 0.064 | 92.6% | 78.9% | 4.5 |
Hard tokens are positions where BF16's top-1 probability is below 0.9. Same 512 held-out prompts and BF16 reference for both checkpoints.
vllm serve QUASAR-QAT/gemma-4-E4B-it-QUASAR-W4A16-G64 --dtype float16
Standard compressed-tensors W4A16. Text and image input; 128K context. For llama.cpp / Ollama / LM Studio, use the GGUF twin.
In our vLLM 0.28 test on one H100, group-64 dispatches to the Machete kernel while Google's group-32 goes to Marlin: 4,225 vs 3,111 output tokens/s at the same batch. Single-request latency is at parity.
Higher point estimates on all 8 downstream benchmarks than Google's QAT model.
| Benchmark | QUASAR | Google QAT |
|---|---|---|
| TriviaQA | 23.8 | 20.1 |
| NQ-open | 4.7 | 2.4 |
| TruthfulQA | 58.2 | 55.4 |
| ARC-Easy | 79.8 | 78.3 |
| ARC-Challenge | 56.2 | 56.0 |
| GSM8K | 82.0 | 81.5 |
| IFEval | 82.6 | 81.9 |
| MATH-hard | 60.7 | 59.4 |
| Average | 56.0 | 54.4 |
Same harness and backend for both checkpoints; full configs, BF16 results and paired-bootstrap CIs are in EVAL.md.
| Benchmark | QUASAR | Google QAT |
|---|---|---|
| HMMT 2026 (avg@32) | 29.0 | 28.6 |
| AIME 2025 (avg@32) | 37.5 | 33.3 |
| SuperGPQA | 40.5 | 39.7 |
| OJBench Python | 18.1 | 17.7 |
| MRCR | 24.4 | 21.0 |
| MRCR ≥64K | 12.0 | 8.0 |
| MRCR 8-needle | 12.7 | 11.5 |
| LongProc-2k | 53.6 | 51.1 |
| LongBench-v2 | 40.4 | 39.8 |
Native QAT checkpoint: the INT4 codes come directly from training, rather than a post-training re-quantization. export_receipt.json verifies the export per tensor. The GGUF twin carries the same codes and scales and ships a --verify script that checks the two files against each other.
vllm serve QUASAR-QAT/gemma-4-E4B-it-QUASAR-W4A16-G64 --dtype float16 (tested on vLLM 0.28.0 and 0.29.0; --dtype float16 keeps the stored fp16 scales exact), then any OpenAI-compatible client. Text and image inputs; 131,072-token context.q/k/v/o/gate/up/down) int4 symmetric, group_size 64, fp16 scales, compressed-tensors pack-quantized; embeddings, norms, per-layer-input tables and the vision/audio towers untouched (bf16). 10.2 GB.QUASAR is loss-aware quantization-aware training. It improves the low-bit reconstruction during training, then exports to standard deployment formats with zero inference overhead.
This checkpoint was healed against the BF16 teacher for 626M tokens: one epoch over ~398k prompts self-distilled from BF16 Gemma 4 E4B-it with thinking on, fp32 master weights, INT4 group-64.
Based on Gemma 4 by Google DeepMind. Upstream LICENSE/NOTICE apply.
@article{counathe2026quasar,
title={QUASAR: Lowering the Loss Floor of Quantization-Aware Training with Loss-Aware Reconstruction},
author={Counathe, Vincent and Athiwaratkun, Ben and De Sa, Christopher and Zhang, Tianyi},
journal={arXiv preprint arXiv:2608.13966},
year={2026}
}