[Docs] Fix A100 Support for DeepSeek-R1 671B: Clarify FP8 Issue & YAML Inconsistencies #4726
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
Michaelvll
reviewed
Feb 16, 2025
There was a problem hiding this comment.
Thanks @andylizf for updating this ! It looks great. Left some comments. Could formatting the output of the model in the details as well, ie make those \n actual new lines, like we did in the distilled model example readme?
Co-authored-by: Zhanghao Wu <[email protected]>
Michaelvll
approved these changes
Feb 18, 2025
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.
Resolves #4723
A100 does not support FP8, but the current example incorrectly lists
A100as a valid accelerator.This PR removes A100 from the default accelerator list and introduces a dedicated job YAML for running DeepSeek-R1 on A100 with BF16 conversion. It also adds a documentation section explaining how to use A100 properly.
Additionally, this PR addresses several documentation inconsistencies and improves wording for clarity.