DeepSpeed assumes model returns just one variable: loss
See original GitHub issueAs you can see in line 596 above in the forward()
call for the DeepSpeedLight
engine, self.module
(which gets initialized earlier with the model
passed to deepspeed.initialize()
by the client) is assumed to be returning just one output: loss
. However, as a model developer, I can have many outputs being returned by my model, including several different losses. An example of such a model would be the GPT2DoubleHeadsModel
in Hugging Face’s transformers repo, which returns two different losses, one for each head/task.
The consequence of this is that I won’t be able to integrate DeepSpeed as-is to work with such models. Could you please make the necessary changes to be able to support this use-case?
I suspect what you need to do is:
- Move lines 599-600 (which perform loss scaling based on gradient accumulation steps) into your implementation of
backward()
. - Update line 596 to reflect the fact that
self.module
could return a generic tuple ofoutputs
instead of aloss
.
This, in turn, will allow the client to define a customized loss
by leveraging all the outputs
, and then call your implementation of backward()
with this loss
as input. And things should be fine because the loss scaling is still happening, only in backward()
instead of forward()
. Does this make sense?
Issue Analytics
- State:
- Created 4 years ago
- Comments:17 (9 by maintainers)
Top GitHub Comments
@tjruwase I think instead of 2, you could just change the signature of
backward()
to also return the loss. The returned loss would be scaled, and typically users log their loss after forward+backward anyway, not just forward.So it sounds like the consensus is
Is this correct? I can start preparing the PR.