DeepSpeed ZeRO-3 Small Parameter Partition Bug
DeepSpeed ZeRO-3 crashes with UnboundLocalError in partition_parameters.py when the model has very small parameters (fewer elements than the number of GPUs). The partition math divides a small parameter across more GPUs than it has elements. Denpex detects the small-parameter partition failure and recommends the configuration fix.
DeepSpeed ZeRO-3 crashes with UnboundLocalError in partition_parameters.
What this failure is
DeepSpeed ZeRO-3 Small Parameter Partition Bug is a Distributed Training failure seen during ML training runs. DeepSpeed ZeRO-3 crashes with UnboundLocalError in partition_parameters.py when the model has very small parameters (fewer elements than the number of GPUs). The partition math divides a small parameter across more GPUs than it has elements. Denpex detects the small-parameter partition failure and recommends the configuration fix. Common tags: Deepspeed, Zero3, Partition, Small Parameter.
Is this what broke your run? Paste your log.
You're reading about DeepSpeed ZeRO-3 Small Parameter Partition Bug. Paste your own crash log or traceback below and get the real root cause for YOUR run, not this generic entry. No account, no card. Logs are masked at ingress and never saved to account history.
Want 14 days on the Scale plan?
Request an evaluation code. A verified workplace organization activates up to 50 diagnoses a day, alerts, history, and follow-up questions. No credit card or automatic subscription.
Why it happens (the mechanism)
ZeRO-3 partitions each parameter's elements equally across GPUs. When a parameter has fewer elements than the number of GPUs, the partition calculation produces zero or negative slice sizes. The partition_dim variable is never assigned when the parameter is too small to partition, causing the UnboundLocalError. Small parameters (e.g., a bias vector with 8 elements on 16 GPUs) cannot be meaningfully partitioned. The bug is in DeepSpeed's partition_parameters.py which doesn't handle the edge case of parameters smaller than world_size. Taken together, these mechanisms explain why the failure is reproducible, why it tends to surface on specific workloads or scales, and why generic mitigation attempts often fall short without addressing the underlying cause.
What you'll observe
- Training crashes with UnboundLocalError in DeepSpeed's partition_parameters.py
- The error occurs during ZeRO-3 initialization for models with very small parameters (e.g., bias vectors, layer norm parameters)
- The same model works with fewer GPUs but crashes when scaled to more GPUs
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| UnboundLocalError: local variable 'partition_dim' referenced before assignment in partition_parameters.py | ZeRO-3 partitions each parameter's elements equally across GPUs. When a parameter has fewer elements than the number of GPUs, the partition calculation produces zero or negative slice sizes |
| Error occurs in deepspeed/runtime/zero/partition_parameters.py around line 862 | The partition_dim variable is never assigned when the parameter is too small to partition, causing the UnboundLocalError |
| Crash happens during DeepSpeed engine initialization, before training starts | Small parameters (e.g., a bias vector with 8 elements on 16 GPUs) cannot be meaningfully partitioned |
| Reducing the number of GPUs or switching to ZeRO-2 avoids the crash | The bug is in DeepSpeed's partition_parameters.py which doesn't handle the edge case of parameters smaller than world_size |
Which systems are affected
- DeepSpeed ZeRO-3 with models containing very small parameters
- Training with 8+ GPUs where some parameters have fewer elements than GPU count
- Models with small embedding layers, bias vectors, or layer norm parameters
- DeepSpeed versions before v0.12.0
How to confirm this is the problem
Use this checklist to test the hypothesis against a small reproduction. No single line proves the root cause, so preserve the preceding events and compare one variable at a time.
- ✓Reproduce the failure from a clean checkpoint/seed: the symptom must appear without warm-up state from a previous run.
- ✓Verified signal present: UnboundLocalError: local variable 'partition_dim' referenced before assignment in partition_parameters.py
- ✓Verified signal present: Error occurs in deepspeed/runtime/zero/partition_parameters.py around line 862
- ✓Verified signal present: Crash happens during DeepSpeed engine initialization, before training starts
- ✓Verified signal present: Reducing the number of GPUs or switching to ZeRO-2 avoids the crash
- ✓A targeted fix from the "How to fix it" section eliminates or substantially reduces the symptom within one validation pass.
The fix and the prevention pattern
The root cause is on this page and stays free. A free account adds the exact remediation steps, saved history, and the fix on every entry in the encyclopedia.
Sign up free. Unlock the full analysisNo credit card. Daily allowance follows verified trust tier. Instant access.
Diagnose this failure in VS Code
Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.
Install the free VS Code extensionDeepSpeed errors in context
DeepSpeed changes when parameters, gradients and optimizer state are created, partitioned, gathered and offloaded. The hub separates ZeRO, memory, checkpoint and pipeline failures by lifecycle phase.
Compare every deepspeed error side by sideRelated failures to investigate next
Root cause
- ZeRO-3 partitions each parameter's elements equally across GPUs. When a parameter has fewer elements than the number of GPUs, the partition calculation produces zero or negative slice sizes
- The partition_dim variable is never assigned when the parameter is too small to partition, causing the UnboundLocalError
- Small parameters (e.g., a bias vector with 8 elements on 16 GPUs) cannot be meaningfully partitioned
- The bug is in DeepSpeed's partition_parameters.py which doesn't handle the edge case of parameters smaller than world_size
The fix and how to prevent it
Evaluate Denpex on your own logs
Request a Scale evaluation code. A verified workplace organization activates 14 days with up to 50 diagnoses a day. Every account keeps its current diagnosis allowance and gets a verification path. No card or automatic subscription.
Don't just read the fix, diagnose your run
The encyclopedia tells you what went wrong. Denpex tells you what went wrong in YOUR training run. With your logs, your config, and your stack.