Can I call `backward()` several times before calling `optim.step()` with AMP?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9k
- Forks
- 1.5k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 3
Description
I'm sorry for asking here, but I'm not sure which is the preferred location for Q&A regarding apex.
Sometimes when batches that fit in GPU memory are not big enough to keep gradient variance at reasonable level, it is possible to call loss.backward() on several consecutive batches (therefore averaging the batch gradients) before executing a single step of the optimizer. My question is whether I can do the same when training with amp. The reason why I am not sure is that amp.scale_loss takes both the loss and optimizer and I am not exactly sure what are the implications of its operation on the optimizer - are all operations it does on the optimizer "averageable" or will the second run of backward incorrectly overwrite some state set in the first run?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the AMP usage around amp.scale_loss, loss.backward(), and optim.step(). Determine whether repeated backward calls before one optimizer step are supported, then document the expected behavior and any optimizer-state implications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- machine-learning
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100