[KongchangAI]
ConceptFP16 / 半精度浮点

FP16

A 16-bit half-precision floating-point format and a commonly used numerical precision standard in deep learning. Compared with FP32 it halves memory usage, while retaining a higher dynamic range than quantized formats such as INT8.

Core Facts

Timeline (last 90 days)

Oct 29

A 7B-parameter model requires about 14GB of VRAM at FP16 precision, and actual requirements are higher once KV Cache and inference framework overhead are added.

Unverified50%
Oct 27

In MoE inference, lowering weight bit width from FP16 to FP8/INT8 reduces the number of bytes proportionally, thereby shortening latency, provided that model throughput is limited by bandwidth rather than compute.

Unverified50%
Oct 23

n-gram tables are usually stored at full precision (such as FP16 or BF16), further amplifying memory usage.

Unverified50%
Oct 20

The system applies per-row range protection to FP16 outputs: before quantizing or writing out FP16, it computes the maximum value of each row and dynamically adjusts the scaling factor accordingly so that the row's values fall within FP16's safe range, then restores them on readout.

Unverified50%
Oct 20

FP16 has only 5 exponent bits, and the smallest representable normal number is about 6×10^-5, so input gradients in backward propagation easily underflow to zero, causing shallower layers to learn nothing at all.

Unverified50%
Oct 18

FP16 is the default precision for most models at release.

Unverified50%
Oct 18

Models are often trained with FP32 or mixed precision, and are usually converted to FP16 when releasing inference versions to halve the size.

Unverified50%
Oct 16

Quantization techniques can compress trained neural network weights from FP16/FP32 to INT8/INT4, significantly reducing model size, lowering memory usage, and improving inference speed, at the cost of possible accuracy loss.

Unverified50%
Oct 16

The KV cache size can be expressed with the formula cache = 2 (K and V) × layers × KV heads × head dim × tokens × 2 bytes, where 2 bytes corresponds to FP16, doubling when using FP32, and halving when using INT8 quantization.

Verified65%
Oct 15

W8A8 quantization means both weights and activations are compressed to 8-bit integers; compared with FP16 it can reduce memory usage and improve NPU throughput, at the cost of possibly introducing slight accuracy loss.

Unverified50%

14 more timeline events

All Facts (20)

Verified

In FP16 precision, large models require approximately 2 GB of VRAM per 1 billion parameters.

80%
Verified

In mixed-precision training, the forward pass uses FP16 to leverage Tensor Core acceleration while parameter updates retain FP32 to maintain numerical stability, which has become standard practice for large model training.

75%
Verified

A 35B model requires approximately 70GB of VRAM at FP16 precision, far exceeding the RTX 5090's 32GB capacity, so single-GPU deployment requires quantization.

75%
Verified

Compared to FP16, BF16 has the same 8-bit exponent width as FP32 and therefore a larger dynamic range, making it the mainstream precision choice for current large model training.

70%
Verified

The KV cache size can be expressed with the formula cache = 2 (K and V) × layers × KV heads × head dim × tokens × 2 bytes, where 2 bytes corresponds to FP16, doubling when using FP32, and halving when using INT8 quantization.

65%
Verified

Quantization compresses the storage precision of model parameters from 16-bit down to 8-bit or even 4-bit, thereby reducing memory usage, but at the cost of potential loss in model accuracy.

65%
Unverified

FP16格式下,大模型显存需求的估算公式为:参数量 × 2 = 所需显存(GB),即每个参数以16位(2字节)浮点数存储

95%
Unverified

A 7B-parameter model requires approximately 14 GB of VRAM for model weights alone in FP16 format, and the total VRAM requirement for training may balloon to 50–80 GB.

60%
Unverified

The perplexity loss of Q4_K_M quantization compared to FP16 is typically within 1%–3%

60%
Unverified

A 7B-parameter model requires about 14GB of VRAM at FP16 precision, and actual requirements are higher once KV Cache and inference framework overhead are added.

50%
Unverified

In MoE inference, lowering weight bit width from FP16 to FP8/INT8 reduces the number of bytes proportionally, thereby shortening latency, provided that model throughput is limited by bandwidth rather than compute.

50%
Unverified

n-gram tables are usually stored at full precision (such as FP16 or BF16), further amplifying memory usage.

50%
Unverified

The system applies per-row range protection to FP16 outputs: before quantizing or writing out FP16, it computes the maximum value of each row and dynamically adjusts the scaling factor accordingly so that the row's values fall within FP16's safe range, then restores them on readout.

50%
Unverified

FP16 has only 5 exponent bits, and the smallest representable normal number is about 6×10^-5, so input gradients in backward propagation easily underflow to zero, causing shallower layers to learn nothing at all.

50%
Unverified

Models are often trained with FP32 or mixed precision, and are usually converted to FP16 when releasing inference versions to halve the size.

50%
Unverified

FP16 is the default precision for most models at release.

50%
Unverified

Quantization techniques can compress trained neural network weights from FP16/FP32 to INT8/INT4, significantly reducing model size, lowering memory usage, and improving inference speed, at the cost of possible accuracy loss.

50%
Unverified

W8A8 quantization means both weights and activations are compressed to 8-bit integers; compared with FP16 it can reduce memory usage and improve NPU throughput, at the cost of possibly introducing slight accuracy loss.

50%
Unverified

Low-precision training and inference (FP16, FP8, FP4) are key to the current ability of large models to scale to trillion parameters.

50%
Unverified

Compared with FP16, 4-bit quantisation can reduce model size and memory usage to about a quarter, which is the key prerequisite for ordinary CPU machines to run local large models.

50%

Source Articles