Copy engine vs SM mode
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.6k
- Forks
- 2.4k
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
I find in SM Mode(for example, write a copy kernel), memcpy's bandwidth is higher than copy engine(cudaMemcpy) in H20. 3.3T/s vs 2T/s, is this reasonable?
Contributor guide
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.
Research direction
Start by reviewing the reported comparison between an SM-mode copy kernel using memcpy and the CUDA copy engine via cudaMemcpy on H20. Reproduce the stated 3.3T/s versus 2T/s measurements and determine whether the difference is expected; the issue does not name a source file, test, or benchmark entry point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100