[QUESTION] Why `Warp`'s tile-based matmul is much slower than torch's one?
Open
@daedalus5 is already working on this.
Since Oct 2, 2025.
ci/cd
question
- Dominant language
- Python
- Stars
- 7.1k
- Forks
- 624
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 5
Description
I have tried the 1.6.0 version of warp, and tested the performance between tile-based matmul in warp and matmul of torch. I found that the performance of warp seems to be very slow. I am wondering why and in the future it is possible to solve this performance discrepancy?
TILE_M TILE_N TILE_K BLOCK Warp Time Torch Time Relative
64 64 64 256 981.684936 363.559419 2.7002049312879994
64 64 64 512 1121.447108 363.559419 3.084632248243306
64 64 64 1024 1146.522702 363.559419 3.153604726164446
64 64 128 256 1436.224992 363.559419 3.950454635312309
64 64 128 512 1050.912843 363.559419 2.890621967354393
64 64 128 1024 1039.730605 363.559419 2.859864304602159
64 128 64 256 1321.610127 363.559419 3.6351970487663254
64 128 64 512 1231.751565 363.559419 3.388033704058703
64 128 64 1024 1123.240676 363.559419 3.089565604130311
Thanks.
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.
Assessment
This issue has not been assessed yet.