pylibwholegraph
WholeGraph supports PyTorch and provides a distributed graph and kv store.
cuGraph-PyG can leverage WholeGraph for even greater scalability.
Using an RMM memory resource
WholeGraph can use RMM's current per-device memory resource for distributed and hierarchy tensors stored on the device. Configure RMM after selecting the process's CUDA device, then enable RMM allocation before creating WholeMemory tensors:
import rmm
import pylibwholegraph.torch as wgth
rmm.reinitialize(pool_allocator=True, initial_pool_size=2**30)
wgth.set_rmm_enabled(True)
WholeMemory looks up RMM's current resource when each supported allocation is created, so normal
RMM per-device resource configuration applies. Call wgth.set_rmm_enabled(False) to use
WholeMemory's default allocator for future allocations.
Chunked, continuous, and NVSHMEM device tensors require specialized CUDA allocation mechanisms. When RMM is enabled, these tensors emit a warning and use their existing allocation path.
Metadata
Release files for pylibwholegraph-cu13 26.10.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pylibwholegraph_cu13-26.10.0-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl | CPython 3.11 | abi3 | Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 | Details for pylibwholegraph_cu13-26.10.0-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
| pylibwholegraph_cu13-26.10.0-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl | CPython 3.11 | abi3 | Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 | Details for pylibwholegraph_cu13-26.10.0-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
Total release size: 595.5 kB
Release files / pylibwholegraph_cu13-26.10.0-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pylibwholegraph_cu13-26.10.0-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 307.9 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
4a64697822d206d307595286ef3ab885fad7945a1c3da6d8ebb595f05b3aec10
|
|
BLAKE2b-256 checksum How to use checksums |
cb420ed9f2938a6f3ededb0e16ca93814c71530d174c857308fca923e1e2c476
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Release files / pylibwholegraph_cu13-26.10.0-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pylibwholegraph_cu13-26.10.0-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 287.6 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
6054a4a8fbf595d1e7f228fd508126d7e1a8b83d4f8f50e50b76d93ff8ffcbbe
|
|
BLAKE2b-256 checksum How to use checksums |
c6112e1fc6c3b7355c3f949b92a28c77d90bd3e87cdbd72e0cca91b40127fb45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Security for pylibwholegraph-cu13 26.10.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
