[QST] How does cutlass profiler test gemm performance?
Open
Nobody has claimed this yet.
? - Needs Triage
inactive-30d
inactive-90d
question
- Dominant language
- C++
- Stars
- 10.5k
- Forks
- 2.1k
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 7
Description
What is your question?
I would like to know how the cutlass profiler tests the performance of gemm?
Because for small matrices, the large L2 cache on the GPU will have a great impact on the measurement of its computation time. The tests of the cutlass profiler seem can avoid such interference
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.
Research direction
Start by examining the CUTLASS profiler's GEMM performance measurement path, focusing on small matrices and GPU L2-cache effects. Document how the profiler measures computation time and avoids or accounts for cache interference, with a clear explanation of the procedure as the completed result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100