Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support for Deepspeed stage-3
See original GitHub issue🚀 Feature Request
The documentation here states that stage-3 is not yet supported.
https://docs.mosaicml.com/en/v0.10.0/notes/distributed_training.html#deepspeed
I tried passing this config to the trainer and it seems to work:
deepspeed_config = {"zero_optimization": {"stage": 3, "stage3_gather_16bit_weights_on_model_save": True}}
Exactly what is missing in stage-3 support from the trainer? Is the saving of checkpoints not configured properly for saving from state_dict of stage-3?
Motivation
Stage-3 would allow for model parameter sharding using deepspeed and allow for much larger model training with composer.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@karan6181 I wasn’t able to make bloom work with fsdp properly. I think bloom was trained using megatron LM with deepspeed and hasn’t been tested with fsdp. And it works out of the box with deepspeed stage-2 in composer. So for my current research I would prefer to stick to deepspeed and not delve into trying to make bloom work with fsdp!
@ananyahjha93 note that we just updated Composer to support the most recent deepspeed release if this is still an issue