[misc] refactor deep_gemm compiler for new interface #6194
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
DeepSeek-V3-0324 gsm8k accuracy: 0.951
After this upgrade, the compilation speed of both NVCC and NVRTC is truly impressive! First, NVRTC takes about 1s per kernel to compile, while NVCC's compilation time has improved from the previous 4s per kernel to 1.2s~1.3s per kernel. Finally, we no longer have to endure long waits for precompilation!
Refer to deepseek-ai/DeepGEMM@d75b218
NVRTC may have performance loss with some cases and NVCC JIT speed is also 4x faster now. So I keep using NVCC here.
@zhyncs Dependency pipeline:
Modifications
Checklist