[QST] Why cutlass profiler not profile all kernels?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.5k
- Forks
- 2.1k
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 7
Description
Hello, with some modification such as ElementC, LayoutA, LayoutB, I can run the exmaple https://github.com/NVIDIA/cutlass/blob/main/examples/70_blackwell_gemm/70_blackwell_fp8_gemm.cu successfully. But with the same problem size, the cutlass profiler does not profile the kernel which is executed in the modified 70_blackwell_fp8_gemm.cu. And I would like to know in which way I can profile all possible kernels?
Similarly, I execute the following test, which I think is same as the kernel in the modified 70_blackwell_fp8_gemm.cu, and return nothing.
cutlass_profiler --operation=Gemm --m=${m} --n=${n} --k=${k} --alpha=1.0 --beta=0.0 --A=f8:row --B=f8:row --C=f16:row --D=f16:row --batch_count=1 --raster_order=heuristic --accum=f32 --profiling-iterations=100 --cluster_m=2 --cluster_n=2 --cluster_k=1 --inst_m=256 --inst_n=128 --inst_k=64
By the way, I compile cutlass profiler with -DCUTLASS_LIBRARY_KERNELS=all -DCUTLASS_UNITY_BUILD_ENABLED=ON
Thanks
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 reproducing the command against the modified examples/70_blackwell_gemm/70_blackwell_fp8_gemm.cu configuration and compare it with the profiler's reported operations. Check how -DCUTLASS_LIBRARY_KERNELS=all and the supplied GEMM parameters affect kernel selection; done means identifying why the equivalent kernel is omitted and documenting or correcting the way to profile it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100