Gradient Checkpointing Tradeoff
Gradient checkpointing trades compute for memory; misconfiguration can either not save memory or drastically slow training.
Gradient checkpointing trades compute for memory.
What this failure is
Gradient Checkpointing Tradeoff is a Memory failure seen during ML training runs. Gradient checkpointing trades compute for memory; misconfiguration can either not save memory or drastically slow training. Common tags: Gradient Checkpointing, Activation Memory, Memory Vs Compute, Training Stability.
Is this what broke your run? Paste your log.
You're reading about Gradient Checkpointing Tradeoff. 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 a work-email trial for up to 50 diagnoses a day, alerts, history, and follow-up questions. No credit card or automatic subscription.
Why it happens (the mechanism)
Gradient checkpointing not applied to all layers. Checkpointing enabled but use_reentrant=True (default) might not work in torch.compile. Activation memory not actually freed during backward. Checkpointing on small layers adds overhead with no memory benefit. 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
- Memory savings not realized with gradient checkpointing
- Training is 2x slower with checkpointing
- Checkpointing not actually enabled
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| Memory still high after enabling checkpointing | Gradient checkpointing not applied to all layers |
| Training is much slower with checkpointing | Checkpointing enabled but use_reentrant=True (default) might not work in torch.compile |
| Gradient checkpointing not in eval mode | Activation memory not actually freed during backward |
Which systems are affected
- Large model training with limited memory
- LLM training with checkpointing
- Activation memory optimization
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: Memory still high after enabling checkpointing
- ✓Verified signal present: Training is much slower with checkpointing
- ✓Verified signal present: Gradient checkpointing not in eval mode
- ✓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, keeps your diagnoses instead of discarding them, and unlocks the fix on every entry in the encyclopedia.
Sign up free. Unlock the full analysisNo credit card · 3 free diagnoses · 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 extensionRelated failures to investigate next
Root cause
- Gradient checkpointing not applied to all layers
- Checkpointing enabled but use_reentrant=True (default) might not work in torch.compile
- Activation memory not actually freed during backward
- Checkpointing on small layers adds overhead with no memory benefit
The fix and how to prevent it
Unlock the full remediation runbook
14 days on the Scale plan, up to 50 diagnoses a day. Step-by-step remediation, the RMA evidence payload, and multi-node correlation on your own logs. No card, and it does not roll into a 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.