[INFRA]: Compare CUB CTest runtime before and after scheduling changes
Open
needs triage
- Dominant language
- C++
- Stars
- 2.5k
- Forks
- 486
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 295
Description
Compare CUB `ctest` runtime on main versus the RAPIDS-based scheduling changes.
Contributor guide
Research direction
Start by locating the CUB ctest invocation and the RAPIDS-based scheduling changes, then establish how to run the comparison on main and on the scheduling branch. Done means reporting comparable CTest runtimes before and after the changes, with the measurement conditions recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system, performance, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100