deepspeedai / deepspeedai/DeepSpeed
why deepspeed transformer only adjust init range on rank 0?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43.1k
- Forks
- 5k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 112
Description
Thanks for open source your deepspeed transformer code.
At deepspeed_cuda.py function init_transformer_weights, the adjust init range feature is applied to rank 0 only. Can you explain why rank 0 only? Shouldn't it be applied to all ranks? Thanks.
Contributor guide
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
Read deepspeed/pt/deepspeed_cuda.py at init_transformer_weights around line 483, then trace how the rank-0 condition relates to distributed initialization. The issue names no test or other entry point; done means providing a clear explanation of the rank-specific behavior and documenting the expected initialization semantics if needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems, machine-learning
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100