Optimization: refactor some memory allocation#1356
Merged
thowell merged 4 commits intoJun 3, 2026
Conversation
Collaborator
Author
|
I still need to double check that we do not have any problems in all codepaths. |
Kenny-Vilella
commented
May 14, 2026
Collaborator
Author
|
I removed the dangerous trick and re-benchmark on L40 (more consistent results there).
|
Collaborator
|
lgtm, thanks @Kenny-Vilella! |
thowell
approved these changes
May 15, 2026
Collaborator
Author
|
Thanks @thowell ! |
Collaborator
Author
|
@thowell Did the compute sanitizer run on test and a selection of benchmark, everything came clean. |
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.
Removed several zeroing in the sparse codepath.
Results on my RTX4080 running the benchmark 5 times and taking the median:
Biggest win is in the sparse case but still some small win in the dense case.