-
-
Notifications
You must be signed in to change notification settings - Fork 11k
[Misc] Add override for allreduce fusion thresholds #23639
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
Conversation
Signed-off-by: Julien Lin <jullin@nvidia.com>
Signed-off-by: Julien Lin <jullin@nvidia.com>
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.
Code Review
This pull request introduces an environment variable to override allreduce fusion thresholds, which is a good feature for benchmarking. However, the implementation lacks robust error handling for the user-provided configuration. My review includes suggestions to prevent application crashes from malformed JSON or invalid data types in the environment variable, improving the overall robustness of this new feature.
Signed-off-by: Julien Lin <jullin@nvidia.com>
Signed-off-by: Julien Lin <jullin@nvidia.com>
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.
LGTM, thank you!
| # { <world size>: <max size in mb> } | ||
| # Unspecified world sizes will fallback to | ||
| # { 2: 64, 4: 1, <everything else>: 0.5 } | ||
| "VLLM_FLASHINFER_ALLREDUCE_FUSION_THRESHOLDS_MB": |
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.
Could we make this a CompilationConfig.PassConfig variable? It might be good to be tunable even after #22086 lands
| _FI_MAX_SIZES.update({ | ||
| int(k): int(float(v) * MiB) | ||
| for k, v in | ||
| envs.VLLM_FLASHINFER_ALLREDUCE_FUSION_THRESHOLDS_MB.items() |
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.
I think reading this will only run at startup but we generally want to read envs during init in case they change between different LLM instantiations. Putting it in config and reading it at pass init time would be best.
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.
@ProExpertProg @ilmarkov Should we just replace fi_allreduce_fusion_max_token_num with something like fi_allreduce_fusion_thresholds_mb? Why do we need to check both num_tokens and message size?
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.
|
@nvjullin did not realize this was on automerge, can you address comments in a follow-up please? |
Signed-off-by: Julien Lin <jullin@nvidia.com> Signed-off-by: tc-mb <caitianchi@modelbest.cn>
Signed-off-by: Julien Lin <jullin@nvidia.com>
Signed-off-by: Julien Lin <jullin@nvidia.com> Signed-off-by: Xiao Yu <xiao.yu@amd.com>
Signed-off-by: Julien Lin <jullin@nvidia.com>
Signed-off-by: Julien Lin <jullin@nvidia.com>
Signed-off-by: Julien Lin <jullin@nvidia.com>
Purpose
Long term plan is being discussed at #22086, but it is not easy and will take some more time.
Meanwhile, add an override so we can benchmark the effect of tuning the thresholds and unblock people.
Test Plan
Test Result
Essential Elements of an Effective PR Description Checklist
supported_models.mdandexamplesfor a new model.