Ask what should change under a concrete input, then trace that expectation through the equation.
Foundation Lab
Distributed Training: Data, Tensor & Pipeline Parallelism
Large models REQUIRE distributed training—no single GPU can hold GPT-4 class models
Selected Foundation Object
Keep the equation fixed; move through the evidence.
Communication is often the bottleneck: AllReduce time can exceed compute time at scale
Use the key equation and canonical papers as the available witnesses, without implying that a runnable panel exists.
The useful learning product is the reusable mechanism you can carry into another model, paper, or engineering tradeoff.
Use prerequisites, dependents, and semantic links to repair the next gap without leaving the object behind.
Why It Matters for Modern Models
- Large models REQUIRE distributed training—no single GPU can hold GPT-4 class models
- 3D parallelism (data + tensor + pipeline) is how 100B+ models are trained
- Understanding communication patterns explains why some architectures scale better than others
What Tutorials Skip
What is still poorly explained in textbooks and papers:
- Communication is often the bottleneck: AllReduce time can exceed compute time at scale
- ZeRO stages trade memory for communication: ZeRO-3 is most memory-efficient but slowest
- Pipeline bubbles waste compute: micro-batching (1F1B schedule) minimizes idle time
Visualization Status
Core Math (Optional Deep Dive)
If you want intuition first, start with the key equation and cited sources. Come back here for the full walkthrough.
Data parallelism: Each GPU holds full model, processes different batches:
Tensor parallelism: Split matrix multiplies across GPUs:
Pipeline parallelism: Split layers across GPUs, micro-batch for efficiency:
ZeRO partitions optimizer states, gradients, parameters across ranks.