-
Notifications
You must be signed in to change notification settings - Fork 453
[JAX] Support Flax sharding constraints #1933
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
Open
jberchtold-nvidia
wants to merge
10
commits into
NVIDIA:main
Choose a base branch
from
jberchtold-nvidia:dev/jberchtold/support-flax-sharding-constraints
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
8fc7cd7
Support flax sharding constraints
jberchtold-nvidia 80524c1
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 209f1e6
Merge branch 'main' into dev/jberchtold/support-flax-sharding-constra…
jberchtold-nvidia 246d893
Add warning for deprecated TE logical axes
jberchtold-nvidia c333077
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] b51986f
Fix dataset package version for examples
jberchtold-nvidia 33e3cf1
Merge branch 'main' into dev/jberchtold/support-flax-sharding-constra…
jberchtold-nvidia 062a58a
Update transformer attention weight sharding axes and update example …
jberchtold-nvidia 06d3122
Merge branch 'main' into dev/jberchtold/support-flax-sharding-constra…
jberchtold-nvidia 5c98794
Merge branch 'main' into dev/jberchtold/support-flax-sharding-constra…
phu0ngng File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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.
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.
Hi,
I'm curious to learn what the difference is between having the
jax.sharding.Mesh
context before vs after thete.fp8_autocast
context.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.
Afaik it doesn't matter the order of the Mesh vs. fp8_autocast, as long as both are before your model. But the order of
te_flax.extend_logical_axis_rules
andfp8_autocast
does matter according to the docstring of the former.So the ordering needs to be:
fp8_autocast
contextte_flax.extend_logical_axis_rules
, which must be inside anfp8_autocast
.Afaik, the Mesh can come anywhere before item 3.
I just pulled up the
fp8_autocast
to the top and merged theMesh
with thewith
block for the logical axis rule context in item 2 to reduce indentation. But if a smaller diff is preferred, I can do Mesh -> fp8_autocast -> logical axis rules