-
Notifications
You must be signed in to change notification settings - Fork 1.8k
GRPO: Scalable training with one LLM/node #3186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
- Temporarily disable optimations for multiple generations from the same prompt - Compute number of local proceses using collective - Strip FSDP checkpointing artifact from parameter names
relevant for multiple processes posting requests to the same server
Use an intra-node communicator to avoid sending large global messages
Thanks @jglaser I'm not sure to understand why FSDP requires to have one vLLM instance per node? |
It does not... FSDP changes and vllm scaling in this PR are not strictly related - however they arose in the same stream of work, as I was trying to train a 14B model which also required sharding (in addition to data parallelism). If the FSDP feature complicates review unnecessarily, this can be factored out into a separate PR. Suggestions? |
Ok, it makes more sense. To make the review easier can you split into two separate PRs 🙏 |
What does this PR do?
Truly scalable training with GRPO + 1 local vllm process per node. Also works with FSDP. Tested on 256 nodes of Frontier (2048 GPUs).
Before submitting
Pull Request section?
to it if that's the case. Scaling bottleneck in GRPO Training. #3258 Support FSDP #3259
documentation guidelines.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@qgallouedec @binary-husky
Caveat: