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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While setting
self.weights_to_keep = Nonecorrectly frees up the memory, a cleaner approach would be to remove theself.weights_to_keepmember variable entirely.The tensors (
gate_data,up_data,down_data) are local to theload_weightsmethod and will remain in scope until the method returns. Sinceself.cpu_infer.sync()blocks until the C++ copy is complete, the lifetime of these local variables is sufficient to ensure the memory is valid for the C++ backend.This makes
self.weights_to_keepredundant. You could consider a refactoring to simplify the code:self.weights_to_keep = Nonefrom the__init__method (line 135).self.weights_to_keep = (gate_data, up_data, down_data)on line 182.This would make the lifetime management implicit and rely on standard Python garbage collection, resulting in cleaner, more idiomatic code.