ZeRO Optimization › Memory Savings Across Stages
Language AI HandbookAll chapters ZeRO Optimization › Memory Savings Across StagesOne section · Sections in this chapter6 / 14 ↓
Reading tools Definitions & inline links
Choose your expertise level to adjust how many terms are explained. Beginners see more tooltips, experts see fewer to maintain reading flow. Hover over underlined terms for instant definitions.
Article links
Make inline references clickable
Let's bring all three stages together and visualize their memory savings as a function of GPU count.

The A100 80 GB line marks the feasibility boundary for an important class of hardware. The baseline never dips below 112 GB, making a 7B model impossible to train on A100s under standard data parallelism regardless of how many GPUs you add. All three ZeRO stages cross below the feasibility line at 2 GPUs in this model, but they diverge sharply as the GPU count grows. The curve for Stage 3 is a true hyperbola (linear reduction), while Stages 1 and 2 flatten out as the unpartitioned components dominate at high GPU counts.

At 64 GPUs, Stage 3 fits a 70B model into 17.5 GB per GPU, well within even older GPU hardware with 24 or 32 GB. The baseline requires 1.12 TB per GPU for a 70B model, which is impossible on any current GPU. Stage 1 reduces that footprint to about 293 GB per GPU, so parameter and gradient replication still make it infeasible. This visualization illustrates why the choice of ZeRO stage has practical consequences: Stage 1 makes moderate models practical, while Stage 3 gives you access to a completely different tier of model sizes.