ZeRO Optimization (Zero Redundancy Optimizer) is a memory-efficient distributed training paradigm that eliminates data-parallel redundancy by partitioning model states—including optimizer states, gradients, and parameters—across parallel processes rather than replicating them. Unlike classic data parallelism where each GPU holds a full model copy, ZeRO shards these tensors across devices, communicating only the necessary slices during forward and backward passes to reconstruct full layers on demand.
Glossary
ZeRO Optimization

What is ZeRO Optimization?
ZeRO Optimization is a memory optimization strategy that partitions model states, gradients, and optimizer parameters across a distributed cluster to enable training of extremely large genomic foundation models.
ZeRO operates in three progressive stages: Stage 1 partitions only optimizer states, Stage 2 adds gradient partitioning, and Stage 3 partitions model parameters themselves. For genomic foundation models processing million-token DNA sequences, Stage 3 is critical—it enables training of billion-parameter architectures on commodity GPU clusters by trading modest inter-GPU communication overhead for an order-of-magnitude reduction in per-device memory footprint.
Key Features of ZeRO Optimization
ZeRO (Zero Redundancy Optimizer) eliminates memory redundancies across data-parallel processes by partitioning model states, gradients, and optimizer parameters. This enables training of billion-parameter genomic language models that would otherwise exceed GPU memory limits.
Three-Stage Memory Partitioning
ZeRO progressively partitions training state across three optimization stages, each reducing memory footprint further:
- Stage 1 (Optimizer State Partitioning): Shards optimizer states (e.g., Adam momentum and variance) across GPUs, reducing memory by 4x with no communication overhead increase
- Stage 2 (Gradient Partitioning): Adds gradient sharding on top of Stage 1, reducing memory by 8x with minimal communication overhead
- Stage 3 (Parameter Partitioning): Shards model parameters themselves, achieving memory reduction linear with the number of GPUs (Nx reduction for N GPUs) at the cost of modest inter-GPU communication
For a 10-billion-parameter genomic foundation model, Stage 3 can reduce per-GPU memory from over 120 GB to under 15 GB.
ZeRO-Offload to CPU and NVMe
ZeRO-Offload extends memory capacity beyond GPU limits by transparently moving optimizer states and gradients to CPU memory or NVMe storage during training:
- CPU Offload: Moves optimizer states and fp32 master weights to CPU RAM, keeping only fp16 parameters and gradients on GPU. Achieves up to 10x larger model training on the same hardware
- NVMe Offload: Extends offload to high-speed NVMe SSDs for extreme model scales, enabling training of models with over 1 trillion parameters on a single GPU
- One-Step Delayed Parameter Update: A novel scheduling technique that overlaps CPU computation with GPU computation, hiding data transfer latency
This is critical for genomic institutions with limited GPU clusters who need to train large DNA language models.
ZeRO-Infinity for Trillion-Parameter Models
ZeRO-Infinity extends the ZeRO family to support training of models with trillions of parameters—a scale relevant for genomic foundation models that must capture the full diversity of human genetic variation:
- Bandwidth-Centric Partitioning: Intelligently partitions model states across GPU, CPU, and NVMe memory tiers based on bandwidth requirements, not just capacity
- Overlap-Centric Communication: Aggressively overlaps communication with computation across all memory tiers to hide data movement latency
- Memory-Centric Tiling: Breaks large operators into smaller tiles that fit within available GPU memory, enabling forward and backward passes on models that exceed GPU memory by orders of magnitude
This architecture enables training of genomic models with up to 32 trillion parameters on 512 NVIDIA V100 GPUs.
Communication Overlap Strategies
ZeRO minimizes the communication overhead introduced by parameter sharding through aggressive overlapping of communication and computation:
- Bucketed All-Gather: Groups parameter shards into buckets and initiates all-gather communication for the next bucket while computing on the current bucket
- Reduce-Scatter Overlap: Overlaps gradient reduce-scatter operations with the backward pass computation of subsequent layers
- Prefetch Scheduling: Prefetches parameters required for upcoming computation steps, hiding network latency behind ongoing GPU operations
For genomic sequence models with long context windows (e.g., 100k+ base pairs), these overlap strategies maintain near-linear scaling efficiency even at 1,000+ GPUs.
Memory Calculation for Genomic Models
Understanding ZeRO's memory savings requires analyzing the memory breakdown of training a typical genomic transformer with Adam optimizer:
- Model Parameters (fp16): 2 bytes × P parameters
- Gradients (fp16): 2 bytes × P parameters
- Optimizer States (fp32): 12 bytes × P parameters (fp32 master weights + momentum + variance)
- Activations: Variable, dependent on batch size, sequence length, and hidden dimension
Example: A 20B-parameter DNA language model requires ~320 GB just for parameters, gradients, and optimizer states. With ZeRO Stage 3 across 8 GPUs, this drops to ~40 GB per GPU, leaving room for activations and batch data. For long genomic sequences (100k tokens), activation memory often dominates, making ZeRO's parameter reduction essential.
Integration with Genomic MLOps Pipelines
ZeRO optimization integrates into production genomic training pipelines through DeepSpeed, Microsoft's open-source deep learning optimization library:
- Configuration-Driven: Memory partitioning strategy is specified via a JSON config file, enabling experimentation without code changes
- Checkpoint Consolidation: Automatically consolidates sharded checkpoints into a single unified model for inference deployment
- Elastic Training: Supports dynamic addition and removal of GPUs during training, critical for preemptible cloud instances used in genomic workloads
- Model Registry Compatibility: Sharded checkpoints include metadata for version tracking, enabling reproducible genomic model training across heterogeneous clusters
This configuration-driven approach allows bioinformatics teams to switch between ZeRO stages based on available hardware without modifying model architecture.
Frequently Asked Questions
Clear answers to the most common technical questions about ZeRO optimization, the memory-efficient distributed training strategy that partitions model states across GPUs to enable training of massive genomic foundation models.
ZeRO (Zero Redundancy Optimizer) is a memory optimization strategy developed by Microsoft DeepSpeed that eliminates data-parallel memory redundancy by partitioning model states—optimizer states, gradients, and parameters—across data-parallel processes instead of replicating them. Unlike classic data parallelism where each GPU holds a full copy of the model, ZeRO splits these states across devices and uses dynamic communication schedules to retrieve only the required partitions during forward and backward passes. The technique operates across three progressive stages: ZeRO-1 partitions optimizer states (reducing memory by 4x with Adam), ZeRO-2 adds gradient partitioning (8x reduction), and ZeRO-3 partitions parameters themselves (memory reduction linear with GPU count). For genomic foundation models processing long DNA sequences with billions of parameters, ZeRO-3 enables training on commodity GPU clusters that would otherwise require prohibitively expensive high-memory accelerators.
ZeRO Stages vs. Traditional Distributed Training
Comparison of memory consumption patterns and scalability characteristics across ZeRO optimization stages and standard data parallelism for large genomic foundation model training.
| Feature | Data Parallelism | ZeRO Stage 1 | ZeRO Stage 2 | ZeRO Stage 3 |
|---|---|---|---|---|
Optimizer States Partitioned | ||||
Gradients Partitioned | ||||
Model Parameters Partitioned | ||||
Memory Reduction vs. Baseline | 0% | 4x | 8x | Nx (linear with GPUs) |
Communication Overhead | Low (all-reduce) | Moderate (reduce-scatter) | Moderate (reduce-scatter) | High (all-gather + reduce-scatter) |
Max Model Size (A100 80GB, 64 GPUs) | ~2B parameters | ~8B parameters | ~16B parameters | ~100B+ parameters |
Activation Memory Unchanged | ||||
Requires Model Code Changes |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Core techniques and infrastructure that complement ZeRO optimization for training massive genomic foundation models.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us