The NVIDIA HGX B200 GPU supports both FP8 (8-bit floating point) and NVFP4 (4-bit floating point) quantization natively in hardware. These formats reduce memory usage and increase throughput compared to BF16, with minimal quality loss.
FP8 is the default quantization for large model inference on the NVIDIA HGX B200. Most model providers now ship official FP8 checkpoints.
All five models in this cookbook use FP8:
Separately from model weight quantization, you can quantize the KV cache to FP8. This reduces per-request memory usage and allows more concurrent requests:
FP8 KV cache is independent of model quantization. You can use FP8 KV cache with a BF16 model, or skip it with an FP8 model. Not all architectures support it: MLA-based models (DeepSeek) compress KV differently and may not benefit.
NVFP4 is NVIDIA's 4-bit floating point format, supported only on Blackwell GPUs (NVIDIA HGX B200, B100, GB200). It halves memory compared to FP8 and doubles throughput for memory-bandwidth-bound workloads.
NVFP4 enables deployment scenarios that aren't possible with FP8:
For a given model and quantization format on the NVIDIA HGX B200 (179 GB VRAM per GPU):
The biggest win from NVFP4 isn't more KV cache on the same GPU count: it's being able to drop TP entirely and run on fewer GPUs.
NVFP4 delivers 1.65x better cost efficiency than FP8 by eliminating the second GPU. On a full 8-GPU node, 8 NVFP4 instances produce ~124,000 tok/s aggregate vs ~75,000 tok/s from 4 FP8 instances. Zero failed requests across all concurrency levels for both formats.
0 Comments
Be the first to comment and share your perspective with the community.