-
Notifications
You must be signed in to change notification settings - Fork 20.4k
Sched: Reintroduce less synchronizations between token, with fixed pipeline parallelism. #20793
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
ggerganov
merged 6 commits into
ggml-org:master
from
aendk:akieslinger/rework-reduce-per-token-syncs
Jun 26, 2026
+27
−7
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
9657cbf
CUDA: Improve performance via less synchronizations between token (#…
aendk abb4948
Apply suggestions from @johannesgaessler code review
aendk c497965
Adds single-GPU synchronizations to multi-GPU settings to fix hip bac…
aendk ede1d0e
Scheduler Hardening: Exclude hip/MUSA from copy_from_host CPU split ->
aendk 2150d7d
Scheduler Hardening: Re-adding original additional synchronizations for
aendk 0234bb9
Adds disclaimer to hip/musa exclusion of copy_from_host. Highlights t…
aendk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add comment here referencing related discussion(s) and TODO for performing tests on the affected hardware to narrow down what was causing the issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be clear, excluding this hip path is not a bug fix. It is only a precaution. In the previous PR, my assumption was that CUDA and hip/MUSA behavior was identical, and that testing on one is identical to testing on the other.
For this PR, I do not want to make any assumptions, and I do not have hip HW to test. Parts like hipMemcpyPeerAsync appear to be be less stable than their CUDA counterparts, depending on the rocm-version.
Since @IMbackK has already summarized that this PR has no meaningful impact on hip (#20793 (comment)), excluding hip and musa from this micro-optimization to reduce the possibility of any bugs makes sense in my eyes.
I'll add these references in the code.