-
Notifications
You must be signed in to change notification settings - Fork 2k
[None][perf] TRTLLM MoE maps to lower tuning buckets when ep>1 #9998
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
rosenrodt
wants to merge
3
commits into
NVIDIA:main
Choose a base branch
from
rosenrodt:autotune-sep-bucket-mapper
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+232
−94
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @rosenrodt , For TRTLLM Gen MoE, why should we disable
apply_map_to_tuning_bucketswhen do autotuning? Does this affect other operators?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After discussion with @hyukn , I understand the case for TRTLLM Gen now. The problem is that
full_workload/ep_sizeNormally, we close this gap by
inputs_hook, which modifies the inputs when do autotuning. Specific to your case, you can modify the inputs so that the workload is divided byep_size.You may refer to the CuteDSL implementation:
TensorRT-LLM/tensorrt_llm/_torch/custom_ops/cute_dsl_custom_ops.py
Lines 85 to 96 in 237fd0e
Currently, this PR introduces inconsistency between the autotuning and inference shapes, which is a bit concerning.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@syuoni provides a better option here. Thanks a lot for the suggestion!
Current process of assembling autotuner cache key is:
map_to_tuning_bucketmethod.By defining
input_pre_hook, we always generate the tensors with the shapes corresponding to the correct workloads for runner.forward. And the shapes stored in the cache remain to be the original bucket shapes (beforeinput_pre_hook). This means we can also keepmap_to_tuning_bucketto a simple bucket mapping method instead of dividing it with ep_size to adjust the workload model.This actuall extends the usage of
input_pre_hook(originally I only want to use it to manipulate the tensor data), but it trully works. I think we should also revise the docstring to clarify this usage.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@syuoni I fully agree with the
input_pre_hook()approach used in cuteDSL but I think it's not directly applicable to TRTLLM MoE.Let's look at the two main changes in this PR:
First,
map_to_tuning_bucket()should not be applied during tuning and this PR addresses that by applying it only during inference. Do you agree that we should keep this change, @syuoni?gen_tuning_bucketswithout involvingmap_to_tuning_bucket(). Themap_to_tuning_bucket()then maps the buckets to cache keys which is not the intended behavior as discussed with @hyukn.Second—this is the controversial part—the TRTLLM MoE repurposes
map_to_tuning_bucket()to account for workload sparsity in a convenient/confusing way depending on how you look at it. Long story short is routing information is not exposed in TRTLLM MoE interface and would require rewrites to fully adopt CuteDSL's approach. I would suggest we defer your suggested approach to a later PR if that's necessary. @syuoni @hyukn let me know what you think :D