Apply some random warpspeed tunings#8352
Merged
bernhardmgruber merged 1 commit intoNVIDIA:mainfrom Apr 14, 2026
Merged
Conversation
Contributor
🥳 CI Workflow Results🟩 Finished in 1h 44m: Pass: 100%/269 | Total: 8d 18h | Max: 1h 25m | Hits: 70%/177111See results here. |
NaderAlAwar
approved these changes
Apr 14, 2026
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.
Works towards: #8348. Those are not the result of serious tuning, just me testing the random tuning search to proof that we are ready for real tuning.
cub.bench.scan.exclusive.sum.warpspeed.baseon B200:The regression for tiny
I8problems is a bit sad, but not an issue, since warpspeed scan has not shipped publicly yet. Since this PR only changes tunings, it's not a regression in the kernel's code.I8andI16absolute results after this PR:This makes it 3x faster than the old scan implementation.