A data centre operations team notices that NFS checkpoint writes from a 32-node training job are causing packet drops on the same fabric used for gradient all-reduce traffic. Which network design change best addresses this interference?
- AIncrease the MTU on the shared fabric to reduce packet overhead for both workload types simultaneously
- BEnable flow control (PFC) on the shared fabric so checkpoint traffic yields to gradient all-reduce flows
- CReplace InfiniBand with 400 GbE Ethernet so the single shared fabric has enough capacity for both traffic types
- DProvision a dedicated high-bandwidth storage network for checkpoint and dataset I/O, separate from the GPU compute fabric Correct
Why A is wrong: Increasing MTU (jumbo frames) can improve throughput for bulk transfers but does not prevent checkpoint I/O and gradient traffic from competing for the same switch buffers. When two high-bandwidth flows share a fabric, they still contend for bandwidth regardless of frame size, so the interference persists.
Why B is wrong: Priority-based flow control can prioritise gradient traffic over storage traffic on a shared link, but it does not eliminate contention for total fabric bandwidth. When the aggregate demand from both flows exceeds link capacity, PFC will pause the lower-priority flow, increasing checkpoint latency and risking deadlock if misconfigured. Separation is more reliable than priority alone.
Why C is wrong: Upgrading to a faster shared medium may reduce congestion temporarily but reintroduces the same competition at higher line rates as the cluster or checkpoint frequency grows. A single shared fabric is still a single point of contention; the architectural solution is separation of traffic planes, not simply provisioning more bandwidth on a shared medium.
Why D is correct: Separating the storage network from the compute fabric ensures that bulk checkpoint writes cannot consume bandwidth or inject congestion into the fabric that gradient all-reduce depends on. Each network can then be independently sized and tuned for its workload: low-latency, non-blocking for compute and high-throughput for storage, eliminating cross-workload interference entirely.