[graphcast] Prepare for jax_pmap_shmap_merge=True.
#5168
+12
−8
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
This change: - Inlines `jax.device_put_sharded` to take an `axis_name` so we can make sure the resulting axis name in the `NamedSharding` matches what the new pmap expects. `_device_put_sharded` falls back to the original `jax.device_put_sharded` when `jax_pmap_shmap_merge=False`. - Strips sharding metadata from RNG keys after pmapped `split_rng_fn` calls. There is a small performance penalty and not ideal, but is less intrusive of a change than making sure all user `predictor_fn`s `pmap` with the same devices. See https://docs.jax.dev/en/latest/migrate_pmap.html for more information. PiperOrigin-RevId: 846566054
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
[graphcast] Prepare for
jax_pmap_shmap_merge=True.This change:
jax.device_put_shardedto take anaxis_nameso we can make sure the resulting axis name in theNamedShardingmatches what the new pmap expects._device_put_shardedfalls back to the originaljax.device_put_shardedwhenjax_pmap_shmap_merge=False.split_rng_fncalls. There is a small performance penalty and not ideal, but is less intrusive of a change than making sure all userpredictor_fnspmapwith the same devices.See https://docs.jax.dev/en/latest/migrate_pmap.html for more information.