-
Notifications
You must be signed in to change notification settings - Fork 31.1k
[TP] Fix parameter detection issue and some invalid TP-plans #42129
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
ArthurZucker
left a comment
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.
Missing a big test ! mega important!
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
|
[For maintainers] Suggested jobs to run (before merge) run-slow: apertus, aria, deepseek_v2, doge, flex_olmo, gemma3, glm4v_moe, qwen3_next, t5gemma |
What does this PR do?
Fixes #42016. Currently, we replace any number in a parameter name with a
*to match the tp_plan. However, params may contain numbers naturally in their name, such as Mixtral's MLPs containingw1,w2andw3param names. This means that they were replaced, and thus not detected as needing sharding. So basically they would be invisible from the tp_plan and never sharded 🥵🥵The regex now checks for
.(dots) on each side of the numbers, to only match layers or list names as we need.Also fixes a few TP-plans, that were detected wrong by the test 🙃🙃