perf: use f16 as split-k partial output data type #900
Conversation
This file contains 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
10 tasks
|
If the input and output are bf16, is the accuracy still sufficient without using fp32 for partial output? |
|
Hi @muoshuosha FlashMLA official implementation uses bf16 as partial output, when inputs and outputs are bf16. Here we just align with the official design. |
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.
We use f32 as split-k partial output data type, mainly for accuracy concern.
However, the official FlashMLA implementation uses 16-bit partial data type, so I guess 16bit split-k is enough for production.
This PR changes flashinfer mla implementation's intermediate data type to 16bit.
This is the third piece (4 in total) of split-k related optimizations.