Skip to content
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

[FEA] BFS #902

Closed
afender opened this issue May 26, 2020 · 3 comments
Closed

[FEA] BFS #902

afender opened this issue May 26, 2020 · 3 comments
Assignees
Labels
Epic Tracker for a relatively large body of work that is broken down into stories and issues
Milestone

Comments

@afender
Copy link
Member

afender commented May 26, 2020

Start in with a 1D distribution consistent with #485 design
C++ API accepts local CSR and RAFT handle/comms, ETL is dealt with at the python level through #812 an #813

At a high level, the first simple BFS would consist of iteratively doing:

Analyze and decide on optimizing 1D or start enabling 2D stack and ETL pipeline.

@afender afender added cuda Epic Tracker for a relatively large body of work that is broken down into stories and issues labels May 26, 2020
@afender afender added this to the 0.15 milestone May 26, 2020
@seunghwak
Copy link
Contributor

I'm worried that this work can largely be duplicate of PR838

See
https://github.com/rapidsai/cugraph/pull/838/files#diff-714d5f231f80f65a9fac0bea5636488a
for BFS implementation using the accelerator API.

If distributed CSR is passed to this and raft communication library is ready to use, turning this to OPG implementation is not a big jump.

The key part to be addressed is to build distributed graph data structure (in a way that enables further optimization) and raft handle & communicator.

@afender
Copy link
Member Author

afender commented May 28, 2020

Does PR838 come with multi-node multi-GPU? I don't see comms or an OPG python API there.

This issue is about an one process per GPU version while leveraging #838 locally as listed in the description.

@seunghwak
Copy link
Contributor

seunghwak commented May 28, 2020

Does PR838 come with multi-node multi-GPU? I don't see comms or an OPG python API there.

This issue is about an OPG version while leveraging 838 locally as listed in the description.

This does not include python binding. This PR is about the C++ part.

This has raft Handle placeholder to be replaced with real raft Handle with comms.

https://github.com/rapidsai/cugraph/pull/838/files

To extend this implementation to OPG, need to fill several places with CUGRAPH_FAIL("unimplemented.");

e.g.
https://github.com/rapidsai/cugraph/pull/838/files#diff-96430227e2a87cec4e46973c995ca24dR325

cpp/include/detail/patterns/expand_and_transform_if_e.cuh line 326

@afender afender mentioned this issue Jul 17, 2020
5 tasks
@BradReesWork BradReesWork modified the milestones: 0.15, 0.16 Aug 20, 2020
@BradReesWork BradReesWork modified the milestones: 0.16, 0.17 Oct 12, 2020
@BradReesWork BradReesWork modified the milestones: 0.17, 0.18 Dec 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic Tracker for a relatively large body of work that is broken down into stories and issues
Projects
None yet
Development

No branches or pull requests

4 participants