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

[EPIC] Support benchmarks at scale #1382

Closed
3 tasks done
BradReesWork opened this issue Feb 4, 2021 · 1 comment
Closed
3 tasks done

[EPIC] Support benchmarks at scale #1382

BradReesWork opened this issue Feb 4, 2021 · 1 comment
Assignees
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 Feb 4, 2021

The goal is to get cuGraph running benchmarks on 128 or more GPUs.

  • Integrate R-mat generator
  • Input / output validation (may also need to be distributed due to scale)
  • identify all required components and add here
@BradReesWork BradReesWork added the Epic Tracker for a relatively large body of work that is broken down into stories and issues label Feb 4, 2021
rapids-bot bot pushed a commit that referenced this issue Mar 5, 2021
…P to use the new R-mat graph generator (#1438)

- [x] Refactor cuGraph C++ test library
- [x] Add a utility function to create a graph object from the R-mat generator
- [x] Update C++ MG PageRank and SG PageRank, Katz Centrality, BFS, and SSSP tests to use the new R-mat graph generator

This partially addresses #1382 and is a per-requsite for graph primitives performance optimization.

Authors:
  - Seunghwa Kang (@seunghwak)

Approvers:
  - Andrei Schaffer (@aschaffer)
  - Chuck Hastings (@ChuckHastings)
  - Brad Rees (@BradReesWork)

URL: #1438
@rlratzel rlratzel changed the title [EPIC] Enter Graph500 [EPIC] Support benchmarks at scale Apr 5, 2021
@rapidsai rapidsai deleted a comment from github-actions bot Apr 5, 2021
@github-actions
Copy link

github-actions bot commented May 6, 2021

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

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

2 participants