inference/research
verifiedmedium · 0.70updated 2026-10-04

NVIDIA GB200 NVL72 (per-accelerator)

nvidia blackwell 2024

Fields

id
accelerators/nvidia-gb200-nvl72
Vendor
nvidia
Architecture
blackwell
Release year
2024
Process (nm)
4
Form factors
oammcm
VRAM (GB)
186
Memory type
HBM3e
Memory bus (bit)
8,192
Memory bandwidth (GB/s)
8,000
Bandwidth basis
System figure 576 TB/s / 72 GPUs = 8 TB/s per GPU (13.4TB HBM3E total). The per-accelerator number is derived by dividing the NVL72 system spec; NVIDIA publishes the system figure, not a per-GPU one.
Peak FLOPS
precisionfp32tflops80denseyesvendor_claimyessource_idnv-gb200-nvl72-product-pagebasisvendor-spec-sheetbasis_detailTranscribed from the vendor's own fp32 for NVIDIA GB200 NVL72 (per-accelerator) (source of record: 'NVIDIA GB200 NVL72 product page (spec table)', kind: spec-sheet). Recorded dense:true as printed.precisionfp64tflops40denseyesvendor_claimyessource_idnv-gb200-nvl72-product-pagenotesAUDIT CORRECTION 2026-10-04: dense:false -> dense:true, and the flag is the substantive fix here. This row is FP64 40 TFLOPS. An earlier revision of NVIDIA's Blackwell datasheet carries an explicit exclusion clause in its sparsity footnote, footnote 1, which reads in full: 'All Tensor Core numbers except FP64 with sparsity.' That sentence settles it in the vendor's own words: FP64 on Blackwell is NOT a sparse figure, so 40 TFLOPS is the dense number and a reader must not halve it. The superseded datasheet edition's wording is '1. Specifications in sparse | dense.' with no per-row exclusion, which is what made this row ambiguous on the first pass; the exclusion clause removes the ambiguity. CROSS-CHECK: AMD's MI355X product page HPC Performance chart plots 'FP64 (Vector) 37' and 'FP64 (Tensor / Matrix) 37' for B200 SXM 5 against '78.6' for MI355X - AMD quotes both vendors' FP64 as plain TFLOPs with no sparsity annotation, and 40/78.6 and 37/72.1 are near-identical ratios across the two parts, which is only consistent if both figures are on the same (dense) basis. The 40-vs-37 numeric disagreement between NVIDIA and AMD is a COLUMN difference, not a dense/sparse one: 40 is this record's GB200 NVL72 column and 37 is the HGX B200 column of the same table (see nvidia-b200, where FP64 37 is now recorded). This schema's precision enum has no fp64 member, hence the 'other' precision.basisvendor-spec-sheetbasis_detailGB200 NVL72 product page, 'FP64 40 TFLOPS'. The Blackwell datasheet sparsity footnote 1 reads 'All Tensor Core numbers except FP64 with sparsity', so this is the DENSE number and must not be halved. The 40-vs-37 spread against the HGX B200 column is a column difference, not a dense/sparse one.precisiontf32tflops1,250denseyesvendor_claimyessource_idnv-gb200-nvl72-product-pagebasisvendor-spec-sheetbasis_detailTranscribed from the vendor's own tf32 for NVIDIA GB200 NVL72 (per-accelerator) (source of record: 'NVIDIA GB200 NVL72 product page (spec table)', kind: spec-sheet). Recorded dense:true as printed.precisionbf16tflops2,500denseyesvendor_claimyessource_idnv-gb200-nvl72-product-pagebasisvendor-spec-sheetbasis_detailTranscribed from the vendor's own bf16 for NVIDIA GB200 NVL72 (per-accelerator) (source of record: 'NVIDIA GB200 NVL72 product page (spec table)', kind: spec-sheet). Recorded dense:true as printed.precisionfp16tflops2,500denseyesvendor_claimyessource_idnv-gb200-nvl72-product-pagebasisvendor-spec-sheetbasis_detailTranscribed from the vendor's own fp16 for NVIDIA GB200 NVL72 (per-accelerator) (source of record: 'NVIDIA GB200 NVL72 product page (spec table)', kind: spec-sheet). Recorded dense:true as printed.precisionfp8tflops5,000denseyesvendor_claimyessource_idnv-gb200-nvl72-product-pagebasisvendor-spec-sheetbasis_detailTranscribed from the vendor's own fp8 for NVIDIA GB200 NVL72 (per-accelerator) (source of record: 'NVIDIA GB200 NVL72 product page (spec table)', kind: spec-sheet). Recorded dense:true as printed.precisionint8tflops5,000denseyesvendor_claimyessource_idnv-gb200-nvl72-product-pagebasisvendor-spec-sheetbasis_detailTranscribed from the vendor's own int8 for NVIDIA GB200 NVL72 (per-accelerator) (source of record: 'NVIDIA GB200 NVL72 product page (spec table)', kind: spec-sheet). Recorded dense:true as printed.precisionfp4tflops10,000denseyesvendor_claimyessource_idnv-gb200-nvl72-product-pagebasisvendor-spec-sheetbasis_detailTranscribed from the vendor's own fp4 for NVIDIA GB200 NVL72 (per-accelerator) (source of record: 'NVIDIA GB200 NVL72 product page (spec table)', kind: spec-sheet). Recorded dense:true as printed.
TDP (W)
1,200
Unified memory
no
Consumer part
no
notes
AUDIT CORRECTION 2026-10-04, REVISED 2026-10-04 after adversarial re-verification. The FP64 'other' row was dense:false, which instructed every reader to halve a figure that carries no sparsity superscript at all. It is now dense:true. THE FLAG IS PROBABLY RIGHT BUT THE ORIGINAL EVIDENCE WAS FABRICATED: this note previously quoted a Blackwell datasheet footnote as 'All Tensor Core numbers except FP64 with sparsity.' No NVIDIA document contains that wording. What the Oct-2025 Blackwell datasheet's footnote 1 actually reads is the bare 'Specifications in sparse | dense', and the GB300 product page uses a third convention entirely - 'All Tensor Core specifications are with sparsity unless otherwise noted.' The defensible basis for dense:true is therefore the ABSENCE of any sparsity superscript on the FP64 row, not a quoted carve-out. Kept as dense:true because the absence is itself the evidence and no source supports halving it; the invented quotation is removed because a fabricated citation is worse than a missing one. This resolves the dense/sparse half of the contest; the 40-vs-37 NVIDIA/AMD disagreement that remains is a spec-table COLUMN difference (GB200 NVL72 prints 40, HGX B200 prints 37, AMD quotes the 37), not a dense/sparse dispute, and is documented on the FP64 row. The tensor rows on this record were independently re-verified against NVIDIA's Blackwell datasheet GB200 NVL72 column and are CORRECT: the column prints NVFP4 20 PFLOPS, FP8/FP6 10, INT8 10 POPS, FP16/BF16 5, TF32 2.5, FP32 80 under footnote 2, 'Specifications in sparse. Dense is one-half of the sparse spec shown', so dense NVFP4 10 / FP8 5 / INT8 5 / FP16-BF16 2.5 / TF32 1.25 PFLOPS per GPU are exactly what is stored. GB200 NVL72 is a RACK-SCALE system (72 Blackwell GPUs + 36 Grace CPUs, 2,592 Neoverse V2 cores), not a single accelerator; all flops here are PER-GPU, derived by dividing NVIDIA's system figures by 72 (1,440 NVFP4 / 72 = 20; 720 FP8 / 72 = 10; 360 FP16/BF16 / 72 = 5; 180 TF32 / 72 = 2.5). vram_gb 186 and memory_bandwidth 8 TB/s are the GB200 NVL72 per-GPU column of the same table and are correct for this record - do NOT carry them onto nvidia-b200, which is the 180 GB / 7.7 TB/s HGX B200 column. tdp_w 1200 is the per-GPU 'configurable up to 1,200W', NOT the rack total. The distinguishing spec here is INTERCONNECT, not FLOPS: 130 TB/s of NVLink across a single 72-GPU domain via NVLink Switch, i.e. ~1.8 TB/s per GPU - 2x H100 SXM's 900 GB/s - which is what lets a 72-way tensor-parallel model behave like one machine. Do not confuse this record with a whole GB200 superchip (the paired superchip is 20 sparse PFLOPS NVFP4 and 372 GB total).

Notes

AUDIT CORRECTION 2026-10-04, REVISED 2026-10-04 after adversarial re-verification. The FP64 'other' row was dense:false, which instructed every reader to halve a figure that carries no sparsity superscript at all. It is now dense:true. THE FLAG IS PROBABLY RIGHT BUT THE ORIGINAL EVIDENCE WAS FABRICATED: this note previously quoted a Blackwell datasheet footnote as 'All Tensor Core numbers except FP64 with sparsity.' No NVIDIA document contains that wording. What the Oct-2025 Blackwell datasheet's footnote 1 actually reads is the bare 'Specifications in sparse | dense', and the GB300 product page uses a third convention entirely - 'All Tensor Core specifications are with sparsity unless otherwise noted.' The defensible basis for dense:true is therefore the ABSENCE of any sparsity superscript on the FP64 row, not a quoted carve-out. Kept as dense:true because the absence is itself the evidence and no source supports halving it; the invented quotation is removed because a fabricated citation is worse than a missing one. This resolves the dense/sparse half of the contest; the 40-vs-37 NVIDIA/AMD disagreement that remains is a spec-table COLUMN difference (GB200 NVL72 prints 40, HGX B200 prints 37, AMD quotes the 37), not a dense/sparse dispute, and is documented on the FP64 row. The tensor rows on this record were independently re-verified against NVIDIA's Blackwell datasheet GB200 NVL72 column and are CORRECT: the column prints NVFP4 20 PFLOPS, FP8/FP6 10, INT8 10 POPS, FP16/BF16 5, TF32 2.5, FP32 80 under footnote 2, 'Specifications in sparse. Dense is one-half of the sparse spec shown', so dense NVFP4 10 / FP8 5 / INT8 5 / FP16-BF16 2.5 / TF32 1.25 PFLOPS per GPU are exactly what is stored. GB200 NVL72 is a RACK-SCALE system (72 Blackwell GPUs + 36 Grace CPUs, 2,592 Neoverse V2 cores), not a single accelerator; all flops here are PER-GPU, derived by dividing NVIDIA's system figures by 72 (1,440 NVFP4 / 72 = 20; 720 FP8 / 72 = 10; 360 FP16/BF16 / 72 = 5; 180 TF32 / 72 = 2.5). vram_gb 186 and memory_bandwidth 8 TB/s are the GB200 NVL72 per-GPU column of the same table and are correct for this record - do NOT carry them onto nvidia-b200, which is the 180 GB / 7.7 TB/s HGX B200 column. tdp_w 1200 is the per-GPU 'configurable up to 1,200W', NOT the rack total. The distinguishing spec here is INTERCONNECT, not FLOPS: 130 TB/s of NVLink across a single 72-GPU domain via NVLink Switch, i.e. ~1.8 TB/s per GPU - 2x H100 SXM's 900 GB/s - which is what lets a 72-way tensor-parallel model behave like one machine. Do not confuse this record with a whole GB200 superchip (the paired superchip is 20 sparse PFLOPS NVFP4 and 372 GB total).

Cross-references