Match each GPU generation to the quantization format that lights up its native tensor cores.
Drag each answer to line up with its matching prompt
H100 / H200 (Hopper)
Pre-Hopper baseline (A100 era); on H100 it works but loses to FP8 because FP8 keeps a wider dynamic range with similar throughput
B200 / GB200 (Blackwell)
FP4, new native tensor core floor that unlocks Blackwell's headline throughput; FP8 still runs but leaves the chip under used
INT4 weights via AWQ / GPTQ
FP8, native Hopper tensor core path, the production sweet spot with mature toolchains (TensorRT-LLM, vLLM, Marlin)
INT8 weight + INT8 activation (W8A8)
Reference precision; useful for accuracy floors and ablations, but leaves half (Hopper) to three quarters (Blackwell) of native tensor core throughput on the table
FP16 / BF16 (no quantization)
Portable across Hopper and Blackwell; activation precision stays higher (W4A16 style), good fallback when the deployment target spans GPU generations
Hopper's native floor is FP8; Blackwell adds FP4 on top. INT4-weight (AWQ/GPTQ) is portable; W8A8 is pre-Hopper; BF16 is the reference baseline.
Each new GPU generation lowers the floor of what numbers it can multiply natively. The older generation could only count down to a certain precision before it had to fake it. The new generation introduces a smaller, faster unit. Picking the right floor for your hardware is like picking the right gear in a car. Too high a gear and the engine bogs down, too low and you redline. FP8 is the right gear for Hopper. FP4 is the right gear for Blackwell. Using FP8 on Blackwell is like driving in third when fourth would be smoother. Using FP4 on Hopper does not work at all because there is no native FP4 unit, so the GPU has to simulate it slowly.
Concept explanation~2 min read
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Concept explanation~2 min read
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Quantization choice in modern LLM serving is mostly a function of what the deployment hardware natively supports. Each NVIDIA generation since Volta has lowered the tensor-core precision floor by one bit-width tier, and the production sweet spot is always the new native floor: BF16 on Ampere, FP8 on Hopper, FP4 on Blackwell.
The match question encodes this pattern plus two non-generational variants. INT4 weight-only quantization (AWQ, GPTQ) is portable across generations because it runs activations at BF16 and never relies on hardware FP4 or FP8. W8A8 is the pre-Hopper legacy that has been superseded by FP8 wherever Hopper is available.
This deep dive covers the floor by floor progression, the specific FP8 and FP4 hardware features, the portability tradeoffs of weight-only quantization, and a practical decision rule for picking the right format given the deployment hardware. By the end you should be able to walk into a production quantization review and defend a format choice in two sentences.
The generational precision-floor pattern
Every NVIDIA data-center GPU generation adds a new tensor-core path at lower precision:
- Volta (V100, 2017): FP16 / FP32 mixed precision. The original tensor cores.
- Ampere (A100, 2020): BF16 and TF32. BF16 became the LLM training default.
- Hopper (H100, 2022): FP8 in E4M3 and E5M2 variants. Doubled BF16 throughput.
- Blackwell (B100/B200, 2024): FP4 with micro-scaling. Doubled FP8 throughput.
Each new floor roughly doubles raw matmul throughput for compute-bound operations by packing more elements per tensor-core cycle. The accumulator typically runs at higher precision (FP16 or FP32) regardless of the operand precision, preserving most of the numerical stability of higher-precision inference.
The production cadence has been: as soon as a new generation arrives with a new floor, the serving stack moves to that floor within 12-18 months. BF16 to FP8 transition happened 2022-2023. FP8 to FP4 transition is happening 2024-2026 as Blackwell deploys.
Situations where this technique stops working.
2–4 min · Everything important, quickly.
Real products, models, and research that use this idea.
- Llama 4 Maverick on H200 ships with native FP8 weights via the Transformer Engine for production serving.
- DeepSeek V4 serving on H100 uses FP8 W8A8 with custom kernels for further throughput gains.
What an interviewer would ask next. Try answering before peeking at the approach.
QHow does the Transformer Engine pick per-tensor scale factors for FP8?
It profiles activation magnitudes during a small calibration pass (often using the model's own training data or a synthetic batch), computes per-tensor amax statistics, and selects scale factors that map the observed range into FP8's representable interval. Scale factors are re-evaluated periodically during training; for inference they are fixed after calibration.
Red flags & common mistakes
The phrases that signal junior thinking. Click to expand.
Red flags & common mistakes
The phrases that signal junior thinking. Click to expand.
Picking the same quantization for every GPU generation. FP8 on Blackwell wastes throughput; FP4 on Hopper has no native path; W8A8 on H100 underperforms FP8.
60 second bullets to scan on the way to the call.
Name the native low-precision floor for Hopper and Blackwell
Explain why running FP8 on Blackwell leaves throughput unused
Same topic, related formats. Practice these next.