[DOCS] Limitation of BF16 inference precision for LLMs #24501
Merged
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
sgolebiewski-intel
added
WIP
sgolebiewski-intel
force-pushed
the
b16-inference-precision-limitation-for-master
branch
from
381651e
to
19917a6
Compare
usstq
reviewed
May 20, 2024
docs/articles_en/openvino-workflow/running-inference/optimize-inference/precision-control.rst
Show resolved
Hide resolved
docs/articles_en/openvino-workflow/running-inference/inference-devices-and-modes/cpu-device.rst
Show resolved
Hide resolved
docs/articles_en/openvino-workflow/running-inference/optimize-inference/precision-control.rst
Show resolved
Hide resolved
…inference/precision-control.rst
sgolebiewski-intel
deleted the
b16-inference-precision-limitation-for-master
branch
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.
Creating
Limitation of the bf16 inference precisionsection to describe an issue of higher accuracy loss than the pre-determined threshold of 0.5% and present possible solutions.This PR addresses JIRA ticket: 138832.