You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we only implement single thread traversal on CPU, it's not efficient and the frontiers cannot be generated on-the-fly with message passing.
Pitch
This feature is important for users who are dealing with graphs with a large number of nodes(edges), e.g. @nforest is working on program analysis where dgl traversal becomes their bottleneck.
There has been many literatures working on Graph Traversal on GPU, to name a few:
we can borrow the ideas from these papers and make a traversal on GPU that could generate frontiers on-the-fly with the execution of message function and reduce function. As the design of our built-in function is based on (a minimized) gunrock, I suppose it would not be too hard to implement a gunrock-like traversal algorithm.
The text was updated successfully, but these errors were encountered:
I mentioned this feature in my RFC #1120 here. I feel at the moment it is too early to work on this unless you have some quick and efficient solutions in mind. I will re-label it as help wanted and we could revisit this once we have more concrete ideas.
馃殌 Feature
GPU traversal (dfs/bfs/topological/...)
Motivation
Currently we only implement single thread traversal on CPU, it's not efficient and the frontiers cannot be generated on-the-fly with message passing.
Pitch
This feature is important for users who are dealing with graphs with a large number of nodes(edges), e.g. @nforest is working on program analysis where dgl traversal becomes their bottleneck.
There has been many literatures working on Graph Traversal on GPU, to name a few:
we can borrow the ideas from these papers and make a traversal on GPU that could generate frontiers on-the-fly with the execution of message function and reduce function. As the design of our built-in function is based on (a minimized) gunrock, I suppose it would not be too hard to implement a gunrock-like traversal algorithm.
The text was updated successfully, but these errors were encountered: