[Triton] add fused_routing_from_topk switch#725
Merged
Conversation
Collaborator
|
let me konw once the ruff issue fixed |
Contributor
Author
|
fixed ruff |
Contributor
Author
|
updates: performance further increased after splitting the routing topk fusion into 3 kernels |
valarLip
approved these changes
May 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR depends on ROCm/aiter#3096
The inter-decode-layer "bubbles" are due to poorly captured multi-stream trace, in which the MOE path is not correctly captured, the topk routing is within that path and it's composed of +10 small torch kernel. This contributes to the ~275 us "bubble" seen in the trace:

after fusing all those ops into a single triton fused kernel, the gap closes down to ~160 us:

lm_eval with fused topk
+15% total token throughput end-to-end
baseline
fused topk