-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] Implement distributed graph store to train giant graph on machines with limited memory #869
Comments
Hey @futurely , thanks for your interests in the system optimization. If you have no objection I'd like to re-organize some of your feature requests into few RFCs so we could have more focused discussion. |
It's okay. Thanks! |
Thanks for your request. In the next release, we will have distributed training capability. Please stay tuned. |
We are also interested in distributed training across multiple machines and want to profile the communication cost. Is there a rough tentative date for the new release supporting this feature? Thanks. |
Baidu's Paddle Graph Learning (PGL) supports distributed graph store with Redis. https://github.com/PaddlePaddle/PGL/blob/master/pgl/redis_graph.py https://github.com/PaddlePaddle/PGL/blob/master/examples/distribute_graphsage/reader.py |
This issue has been automatically marked as stale due to lack of activity. It will be closed if no further activity occurs. Thank you |
This issue is closed due to lack of activity. Feel free to reopen it if you still have questions. |
🚀 Feature
Implement distributed graph store to train giant graph on machines with limited memory.
Motivation
Many graphs need hundreds of GB or more memory to load into graph store. It's common that a single machine cannot load such graphs. So this problem is a serious blocker for large scale applications of DGL. Some other frameworks such as PyTorch-BigGraph and Euler partition the graph into smaller files for fully distributed training.
Pitch
Efficient distributed training with arbitrarily large graphs. Wider adoption of DGL especially in the industry.
The text was updated successfully, but these errors were encountered: