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] cuML and cuGraph sharing of handle and comms #523

Closed
5 of 6 tasks
dantegd opened this issue Sep 26, 2019 · 1 comment
Closed
5 of 6 tasks

[FEA] cuML and cuGraph sharing of handle and comms #523

dantegd opened this issue Sep 26, 2019 · 1 comment
Labels
feature request New feature or request
Milestone

Comments

@dantegd
Copy link
Member

dantegd commented Sep 26, 2019

Is your feature request related to a problem? Please describe.
cuML cuGraph have many needs in common. To be more efficient across projects we should look to share not only algorithmic components but also some infrastructure ones. In particular the cuGraph team wants to adopt the cumlHandle and cumlComms, which definitely can be useful beyond just cuML. This issue is for tracking those efforts.

Describe the solution you'd like
Tasks needed:

  • Copy/move handle and required components to raft repository. Rename to raftHandle or rapidsHandle or something.
  • Create raft-comms repository: https://github.com/rapidsai/ops/issues/479
  • Copy/move cumlcomms to raft-comms repo
  • Create binary/conda package of raftComms (or rapidsComms)
  • Update cuML to use shared headers/artifact
  • Update cuGraph to use shared headers/artifact

Additional context
cuGraph team requires the comms in particular to be moved sooner rather than later, with a target of end of October.

Mirror issue in cuML: rapidsai/cuml#1151

@dantegd dantegd added ? - Needs Triage Need team to review and classify feature request New feature or request labels Sep 26, 2019
@afender afender mentioned this issue Nov 11, 2019
7 tasks
@afender afender added the OPG label Apr 6, 2020
@BradReesWork BradReesWork added this to the 0.15 milestone May 11, 2020
@BradReesWork BradReesWork removed the ? - Needs Triage Need team to review and classify label May 26, 2020
@afender
Copy link
Member

afender commented Jul 1, 2020

This was done as part of the cuGraph OPG and RAFT effort 🎉
#815 to track adoption in existing single GPU features in cuGraph

@afender afender closed this as completed Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants