Merged
Conversation
Update tsu range to relevant since lot of improvements went in
djordje-tt
requested review from
avoraTT,
johanna-rock-tt,
kpaigwar,
mtairum and
sraizada-tt
as code owners
johanna-rock-tt
approved these changes
Jun 5, 2025
Contributor
|
The perf sometimes goes up to 58.1 tps, I'd change the max perf to be 59, based on the recent demo regression CI run |
barci2
reviewed
Jun 5, 2025
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
3 participants
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.
Update tsu range to relevant since lot of improvements went in
Problem description
Llama70b on 6U full demo was not executing often and tsu range is out of date
What's changed
tsu range [49,53] -> [53,58] due to lot if improvements in the meantime
Checklist