sequence parallel add tests#36
Conversation
Summary of ChangesHello @meichangsu1, 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 significantly expands the testing coverage for the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe 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 by creating a comment using either
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 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
|
There was a problem hiding this comment.
Code Review
This pull request adds comprehensive alignment tests for sequence parallelism combined with FSDP and expert parallelism. The tests are well-structured, comparing baseline configurations against sequence parallel variants to ensure correctness of logits and gradients. The change in sequence_parallel.py to remove implicit derivation of ulysses_size makes the configuration more explicit, which is a good improvement. I've added one suggestion to improve test performance.
|
|
||
| # --- SP variant: EP+FSDP+SP --- | ||
| # Note: SP does global patching; keep it after baseline in this process. | ||
| model_sp = _load_qwen3_moe_pretrained(model_id, local_files_only, device) |
There was a problem hiding this comment.
You are loading the pretrained model again here. For better test performance, you could load it once at the beginning of the test, then use copy.deepcopy to create the two model instances for the baseline and the variant. This avoids a second expensive from_pretrained call. You've already used this optimization in _run_worker_fsdp_sp_align.
Move sequence-parallel strategy construction to a lazy method `_ensure_sp_strategy` to reduce side effects during model initialization. The strategy is now created only when needed, after the underlying Hugging Face model is fully initialized and before wrapping. This improves initialization performance and avoids unnecessary overhead when sequence parallelism is not enabled.
add tests for accurancy