gpu: a GEMM with 128×128 tiles to measure the Ampere strategy
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- performance
Research direction
Start from the existing v5 GEMM linked in #3400 and the copy pipeline in #3412; the issue names no files, so locate the 64x64/4-warp kernel and its benchmark first. Implement a v8 block tile of 128x128 with 8 warps, each warp taking 64x32, then benchmark on the RTX A6000 with and without the #3412 pipeline, comparing TFLOP/s and cuBLAS percentage. Done means v8 compiles and both measurements are reported; if register pressure or a compiler pass blocks the larger tile, file that as a separate issue.
Written by the indexing model from the issue text.
Description
The Vx GEMMs in #3400 compute a 64×64 tile of C in each block, with 4 warps. On an RTX A6000, v5 reaches 50 TFLOP/s, 44% of cuBLAS (https://github.com/vx-lang/Vx/issues/3400#issuecomment-6883701143). cuBLAS uses tiles of 128×128 or larger. A 64×64 tile does too little math for each byte it loads into shared memory.
Write a v8 that computes a 128×128 tile in each block, with 8 warps, each warp taking 64×32. Then measure it with and without the copy pipeline of #3412. With larger tiles, fewer blocks fit on each SM, so other blocks can no longer use the tensor cores while one block waits for its copies. That is the case where the pipeline should pay off.
If v8 hits a compiler limit, such as register use or a pass that does not fit the larger tile, file it as its own issue.
- Dominant language
- Rust
- Stars
- 35
- Forks
- 5
- Avg merge
- 12h 26m
- Merged PRs (30d)
- 799
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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 vx-lang/Vx
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug testing
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
`pub struct` gives "Expected 'fn' after 'pub'": the error should say that a struct needs no `pub`Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug devex
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
longbridge/gpui-kit#4031 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
neuralmagic/crucible#465 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
compiler P3
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
HerringtonDarkholme/hd-lang#2162 ·
Maintainers usually reply within 1 day
-
embedded SQL: pin correlated-guard behaviour when a closed variable is reassigned inside a branchOpenpriority: low
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
jonathanong/no-mistakes#3627 ·
Maintainers usually reply within 1 day