Draft
Conversation
fc1a76a to
748833a
Compare
748833a to
4ff0831
Compare
|
A compile time flag seems like a great idea! With that, I think it would nice to have two flags:
That way the User can choose the precision. 😋 |
Member
Author
|
It will be checked at run-time, based on the precision configured for each matrix multiplication (see #10665 (comment)). |
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.
Using F16 math and accumulators in matrix multiplication kernels.
The prompt processing performance is improved. The perplexity is affected as follows:
Not sure if it worth it yet. Might do this as a compile-time flag#10665 (comment)GGML_METAL_F16.