-
Notifications
You must be signed in to change notification settings - Fork 47
Update MoE training in example #251
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @chenyushuo, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request enhances the configuration and documentation for training Mixture-of-Experts (MoE) models within the Megatron framework. It introduces parameters to support distributed checkpointing and clarifies the recommended methods for setting up MoE models, ensuring proper integration and successful training.
Highlights
- MoE Training Configuration: Introduced new configuration parameters,
use_dist_checkpointinganddist_checkpointing_path, to Megatron-based training examples for actor rollout and critic models. - MoE Documentation Update: Updated the documentation to provide clearer and more detailed guidance on training Mixture-of-Experts (MoE) models, outlining two distinct approaches: using MBridge or manual model conversion with the newly added distributed checkpointing options.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request updates the documentation and an example configuration to clarify the training process for Mixture-of-Experts (MoE) models with Megatron. It introduces new configuration options, use_dist_checkpointing and dist_checkpointing_path, providing a clear alternative to using MBridge. The changes are well-structured and improve the documentation's clarity. I've found one minor issue in the documentation that needs to be addressed.
Description
As the title says.
Checklist
Please check the following items before code is ready to be reviewed.