Stop overriding JAX GPU memory preallocation - #1539
Merged
Merged
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
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.
Summary
Stop setting
XLA_PYTHON_CLIENT_MEM_FRACTION=1.00when selecting the JAX GPU backend on Linux. This preserves either JAX's default allocation policy or a user-provided value.Setting the fraction to 100% can produce a
RESOURCE_EXHAUSTEDmessage during CUDA initialization, even when JAX can recover and complete the operation.Impact
Public-facing:
use_backend("jax", gpu = TRUE)no longer overrides the JAX GPU memory allocation configuration.Internal: no API or Python dependency changes.
Closes #1538