Integrate CCCL runtime APIs into nvbench
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating nvbench::cuda_stream and all of its uses, then compare those call sites with the CCCL cuda::stream_ref runtime API. Check whether other nvbench internals or examples use older runtime wrappers. Done means the relevant uses are consistently integrated with the CCCL runtime APIs and the scope is verified.
Written by the indexing model from the issue text.
Description
I noticed nvbench has nvbench::cuda_stream type, we should refactor it to use cuda::stream_ref instead. There could be more examples like that or just internals could use the new CCCL runtime APIs
- Dominant language
- Cuda
- Stars
- 927
- Forks
- 123
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/nvbench
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
good first issue P1: should have python type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
bancolombia/sentinel#20 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
alunduil/woodland-generators#669 ·
-
area: tooling
Difficulty 2/5 1-3 hours Newbie friendliness 86/100