Fix Auto-sharding Bug for Residual blocks.#18
Closed
gaga1313 wants to merge 1 commit into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix: Prevent sharding conflicts between non-primary axes in
auto_shard.pyThe current heuristic in
auto_shard.pyonly checks for sharding conflicts against the single dominantmodel_axis. It does not account for conflicts that can arise between newly assigned non-primary axes.Problem: When testing with a Residual Block, the existing code incorrectly caused the weight parameter of the
linear3layer to be sharded on both dimensions using themodel_axis.Solution: To fix this bug, I have introduced a
dim_shardedflag. This flag tracks whether a dimension has already been sharded while assigning the sharding axis to each parameter dimension, preventing erroneous double-sharding.Reproduction script: