-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete extra tensor objects after restoring float8 tensors #1500
base: main
Are you sure you want to change the base?
Delete extra tensor objects after restoring float8 tensors #1500
Conversation
Signed-off-by: Sudhakar Singh <[email protected]>
for more information, see https://pre-commit.ci
self._data = None | ||
self._transpose = None |
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.
@pggPL IIRC you removed these during a numerics debugging effort, do you remember why?
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.
If weight is in fp8 I want to have it in save_for_backward() - for offloading. If there is forward, but backward is not invoked, it will result in removing the weight. I discussed it with @ptrendx and he proposed some solution with flag internal
in prepare_for_saving
- to set it True if tensor is not owned and remove tensors iff they are internal. It seems that we forgot about this.
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.
Ok, so that would be solved by overriding this function in Float8Tensor and MXFP8Tensor to just return self and None instead.
Also, in https://github.com/NVIDIA/TransformerEngine/blob/main/transformer_engine/pytorch/tensor/quantized_tensor.py#L30 why do we check for exactly Tensor or Param and not just isinstance(torch.Tensor)? This should solve this as well, right?
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.
Now logic of restoring tensor is inside the tensor object. If tensor object is None, we assume that this was standard torch.tensor. If it is QuantizedTensor, then it object is responsible for restoring itself, so we need to somehow save it.
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.
Well, QuantizedTensor is in a way a standard tensor - at least it can be passed whole through save_for_backward, so there is nothing to restore afterwards.
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.
ok, it makes sense
Signed-off-by: Sudhakar Singh <[email protected]>
…ingh27/TransformerEngine into fix_memory_leak_te_2.0
/te-ci |
Description
After restoring the
float8
tensors in the backward passes ofLayernormMLP
,LayernormLinear
andLinear
, the tensor objects are not needed butctx.tensor_objects
still holds the reference and hence it results in extra memory usage. This fixes it.Fixes # (issue)
Type of change
Changes
Please list the changes introduced in this PR:
tensor_objects
once they're used in the backwards ofLayernormMLP
,LayernormLinear
andLinear
modules.Checklist: