KV Cache Quantization in Production LLM Serving: Comparing FP8, INT8, INT4, KIVI, and KVQuant
In high-throughput large language model serving, the primary hardware bottleneck during autoregressive token generation is memory bandwidth and GPU High Bandwidth Memory (HBM) capacity rather than raw compute FLOPS. While model weights remain static and are loaded once per forward pass, the Key-Value (KV) cache grows dynamically with sequence length and batch size. For a standard model in FP16 or BF16 precision, storing the KV cache requires 4 bytes per token across all layers and heads: Memor



















