[CUDA] Tune ops per buffer based on device#2761
Merged
awni merged 3 commits intoml-explore:mainfrom Nov 16, 2025
Merged
Conversation
011a737 to
43d2f55
Compare
43d2f55 to
e2694be
Compare
Member
Author
|
This will probably need more tuning in the future especially for devices that I didn't add yet. But for now I think it's good to merge. |
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.
We need a more sophisticated policy to set ops per buffer based on the device. This is a start to that.
For inference on B200 it helps a lot for inference to increase it at very little memory cost.
Pre:
generation_tps=244.456, peak_memory=16.166Post:
generation_tps=283.073, peak_memory=16.224For training 0.6B it's a double win, faster and less RAM 💪