optimize moe_align_kernel cuda #3347
Merged
+29
−21
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.
Thanks to @tim-zou help in #3339.
DeepSeek V3 end2end benchmark
After starting the service, I ran
benchmark/gsm8k/bench_sglang.py
twice. The results shown below are from the second run.main branch:
pr:
It's possible that the number of tokens in this dataset did not trigger the bad case for the moe_align_block_size kernel, meaning the token count was less than 4096. Therefore, this offline benchmark shows little difference, but it can verify the consistency of accuracy.
micro benchmark in H200
main branch:
pr:
The pr has solved all the badcase performace, we can consider remove triton moe_align_block_size now.
@zhyncs