Skip to content

Chapter 14: GPU Hardware Generations and Network Implications · Part 2 of 11

Act 1 -- Why GPU generations drive fabric decisions

The standard framing of GPU generations focuses on compute: TFLOPS, tensor core counts, HBM capacity. None of that determines fabric architecture. What determines fabric architecture is the interconnect stack that ships with the GPU.

Three parameters change with every generation and cascade into infrastructure decisions:

Intra-node bandwidth: how fast can a GPU communicate with its siblings inside the same DGX node? This is NVLink territory. Higher NVLink bandwidth means larger batch sizes can be processed with tensor parallelism inside a single node, reducing the amount of inter-node AllReduce traffic that has to cross the fabric. The network engineer's job gets easier as NVLink bandwidth grows -- fewer jobs need inter-node scale-out for a given model size.

PCIe interface bandwidth: how fast can the GPU talk to the host CPU and to PCIe-attached NICs? This is the binding constraint for any GPU that isn't in an SXM form factor. A 400 Gbps ConnectX-7 in PCIe Gen 4 is already close to the one-directional PCIe ceiling. Gen 5 doubles the ceiling, but the ceiling still exists and still matters.

NVLink Switch support: not all GPUs can participate in an external NVLink Switch fabric. Only SXM-form-factor GPUs have the full NVLink port count required. PCIe-form-factor GPUs either have no NVLink or a reduced implementation. This is the form factor choice that determines whether a GPU can join a scale-up NVLink cluster at all.

NVLink & NVSwitch generations
Select a GPU generation to see the interconnect stack and DGX configuration
NVLink 4 — GPU interconnect
Links per GPU
18
BW per link
25 GB/s
Total per GPU
900 GB/s
Form factor
SXM5
Bidirectional bandwidth vs B200
900 GB/s / 1800 GB/s
NVSwitch 3th gen — node fabric
Agg. switch BW
13.6 Tb/s
GPUs per node
8
DGX product
DGX H100
Architecture
Hopper
Switch aggregate BW vs B200
13.6 Tb/s / 28 Tb/s
NVLink gen ≠ NVSwitch gen — separate counters. NVSwitch silicon generation always matches the DGX product generation it ships in, not the NVLink protocol number.