share memory pools between torch and cupy#96
Merged
Conversation
JensWehner
marked this pull request as ready for review
July 23, 2026 08:17
Contributor
There was a problem hiding this comment.
Copilot encountered an error: Your billing is not configured or you have Copilot licenses from multiple standalone organizations or enterprises. To use premium requests, select a billing entity via the GitHub site, under Settings > Copilot > Features.
szbernat
previously approved these changes
Jul 23, 2026
szbernat
left a comment
Contributor
There was a problem hiding this comment.
Thanks Jens, makes sense to me!
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
szbernat
approved these changes
Jul 23, 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.
from @tvogels
This should fix that. @szbernat
My agent wrote a script to profile the code to
evaluate the memory impact of enabling the PFN allocator bridge
(pytorch_pfn_extras CUDA mempool in CuPy) for the Skala GPU4PySCF gradient
workload, and compare it to the default CuPy allocator.
Benchmark Script
The script is now intentionally limited to one built-in benchmark molecule: naphthalene.
It executes both allocator modes in isolated child processes and reports only the peak
metrics used in this comparison:
Full script:
Workload
Command used (sequential execution, no concurrent runs):
Results
Per-run values (MiB)
Maxima across repeats (MiB)
Numerical consistency check:
Conclusions
Smoke Test
A lightweight allocator smoke test was added to:
The smoke test:
graphics card was my local one
NVIDIA-SMI 595.61 NVIDIA RTX PRO 2000 Driver Version: 595.95 CUDA Version: 13.2