docs: note CUDA_VISIBLE_DEVICES workaround for multi-GPU systems#75
Merged
Conversation
Importing gpu4pyscf allocates memory on every visible CUDA device, which conflicts with PyTorch and with other processes sharing those GPUs (e.g. in MPI-parallel workloads). Document the CUDA_VISIBLE_DEVICES workaround and link to the upstream tracking issue. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
awvwgk
approved these changes
May 26, 2026
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.
Adds a short note to the GPU getting-started section: importing
gpu4pyscfallocates memory on every visible CUDA device, which conflicts with PyTorch and with other processes sharing those GPUs (e.g. in MPI-parallel workloads).Documents the
CUDA_VISIBLE_DEVICES=0workaround (and the MPI per-local-rank variant) and links to the upstream tracking issue pyscf/gpu4pyscf#435.