What does low-bit quantization save and sacrifice?
Account for weights, activations and KV precision separately.
Content revision 4 · 2026-10-24
I06 · Revision 1 · 2026-10-21
- High-precision weights
- Group scale + low-bit codes
- Kernel compute / dequantize
- Separate quality and speed tests
The bottleneck
Low-bit weight codes reduce storage and read traffic, but quantization errors can change behavior. Weight, activation and KV quantization target different tensors; one “4-bit” label does not describe the entire inference process.
The mechanism
Grouped quantization stores a scale and sometimes a zero point per group. Codes are rounded and clipped, then consumed by low-bit kernels or dequantized. AWQ uses activation information to identify sensitive weights and adjust scaling, controlling losses in low-bit weight quantization.
q = clip(round(w/s)+z); ŵ = s(q−z)
Examples and evidence
For 10B weights, payload alone is about 20GB in FP16 and 5GB at 4 bits (decimal). Add scales, zero points and unquantized tensors. Fourfold weight reduction does not imply fourfold reduction in total memory or latency.
New constraints
Outliers, calibration data and task distributions affect error. Efficient kernel support determines performance. Validate long contexts, domain tasks and output behavior rather than relying on one average score.
Primary sources
- AWQ: Activation-aware Weight Quantization · 2023-06-01 · Checked 2026-10-21
Manual browser reading records and interactive calculators are available with JavaScript.
Keep exploring
I01 · Why does KV cache grow with context and concurrency?
T02 · How should a fixed compute budget split parameters and tokens?