Create alias for Accelerator.free_memory #318
Merged
Conversation
This file contains 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
|
The documentation is not available anymore as the PR was closed or merged. |
sgugger
reviewed
Apr 19, 2022
Co-authored-by: Sylvain Gugger <[email protected]>
4 tasks
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.
Create alias for
Accelerator.free_memoryWhat does this add?
This PR introduces
Accelerator.clear, an alias forAccelerator.free_memory. The reasoning for this addition is a user may be wanting to destroy all of the stored items in Accelerate, and they may instinctively search for a "clear" function.They may dig for a bit until they see that
free_memoryis what they should call, so this pr helps to aid that workflow style and expectation.(This PR is 100% opinionated ;) )