Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
101d0f2 to
c6767c8
Compare
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
@djns99 could you fix the linter issue? |
8119d3b to
07c1a19
Compare
9a90932 to
33b2f8d
Compare
|
@nvpohanh I think this should be ready now |
|
Hmm odd it passed locally when I ran it earlier today. Must have had a out of sync local state. Pushed a fix |
| "Select DeepEP dispatcher output dtype", | ||
| NS("exec.moe"), | ||
| ] = "auto" | ||
| flashinfer_a2a_dispatch_type: A[ |
There was a problem hiding this comment.
I am wondering why we need this flag. We should always just dispatch with the lowest precision supported by the quant config, right?
There was a problem hiding this comment.
I even think SGLANG_MOE_NVFP4_DISPATCH is not needed
There was a problem hiding this comment.
I agree in most cases we want to do this. Im not familiar enough to say definitively that there are no cases that this is disadvantageous.
I can see low batch cases which are latency bound being better to use BF16 and quantizing fused into the MOE kernel operations so we dont pay the cost of a separate quantization kernel
| else: | ||
| if self.moe_runner_backend == "flashinfer_trtllm": | ||
| self.moe_runner_backend = "flashinfer_trtllm_routed" | ||
| logger.warning( |
There was a problem hiding this comment.
what is this warning for?
There was a problem hiding this comment.
This is making sure the user is warned if they ask for the wrong flashinfer_trtllm backend. Otherwise, it will get a less clear error in _handle_flashinfer_a2a_dispatch_type
We can make this an error if that would be more clear
|
@djns99 could you fix the conflicts? |
Enable BF16 flashinfer A2A tests
67f43b0 to
2bee526
Compare
|
Changes will be merged via #31470 |
Motivation
Modifications
Accuracy Tests
Speed Tests and Profiling
Checklist
Review and Merge Process
/tag-and-rerun-ci,/tag-run-ci-label,/rerun-failed-ciCI States
Latest PR Test (Base): ❌ Run #32316431606
Latest PR Test (Extra): ❌ Run #32316431413