Skip to content
This repository has been archived by the owner on Nov 25, 2024. It is now read-only.

WholeGraph Next Refactoring #48

Open
5 of 9 tasks
BradReesWork opened this issue Aug 3, 2023 · 0 comments
Open
5 of 9 tasks

WholeGraph Next Refactoring #48

BradReesWork opened this issue Aug 3, 2023 · 0 comments
Assignees
@dongxuy04
Labels
Epic Tracker for a relatively large body of work that is broken down into stories and issues

Comments

@BradReesWork
Copy link
Member

BradReesWork commented Aug 3, 2023 •
edited
Loading

Improve the initial refactoring

Tasks
Preview Give feedback
  1. Use RAFT communicator instead of a separate communicator in WholeMemory #4
    good first issue tech-debt
    dongxuy04
  2. Use top-k from RAFT #5
    good first issue tech-debt
    dongxuy04
  3. Usage of C10 API's in WholeMemory and its implication on build #6
    dongxuy04
  4. use "random" from RAFT API #7
    good first issue tech-debt
    dongxuy04
  5. use cudart_utils.cuh/error.hpp from RAFT #8
    good first issue tech-debt
    dongxuy04
  6. WG as a FeatureStore in cugraph-pyg #47
    dongxuy04
  7. Use RAFT's RngState on APIs, DeviceState within kernels, and use specialized distributions for generating numbers #23
    feature request
    dongxuy04
  8. WG Introduction BLOG #49
    doc
    dongxuy04
  9. WG Performance BLOG #50
    doc
    dongxuy04
@BradReesWork BradReesWork added the Epic Tracker for a relatively large body of work that is broken down into stories and issues label Aug 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dongxuy04 dongxuy04

Labels
Epic Tracker for a relatively large body of work that is broken down into stories and issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@BradReesWork @dongxuy04