Prune CUDA static numerical libraries for specifice compute capability #3234
Conversation
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
Prune CUDA static libraries so that the binary size of the final executable is smaller. This commit will run the nvprune utility on some static libraries (cublasLt, cublas, cusolver, and cusparse) to remove unused architectures from the binary. The resulting binary is significantly smaller when targeting a single compute capability.
syurkevi
approved these changes
Mar 22, 2022
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.
Prune CUDA static libraries so that the binary size of the final executable
is smaller.
Description
Prune CUDA static libraries so that the binary size of the final executable
is smaller. This commit will run the nvprune utility on some static libraries
(cublasLt, cublas, cusolver, and cusparse) to remove unused architectures
from the binary. The resulting binary is significantly smaller when targeting
a single compute capability.
For example when targeting only compute capability 7.5 the resulting binary
is 545MB as opposed to 1100+MB without pruning.
Changes to Users
N/A
Checklist
[ ] Functions added to unified API[ ] Functions documented