Skip to content
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

[bugfix] Reduce memory leaks #8490

Merged
merged 41 commits into from
Jul 21, 2021
Merged

[bugfix] Reduce memory leaks #8490

merged 41 commits into from
Jul 21, 2021

Conversation

tchaton
Copy link
Contributor

@tchaton tchaton commented Jul 20, 2021

What does this PR do?

This PR moves the optimizer states back to cpu on teardown and move ResultCollection Extra on cpu too.

Fixes #8463
Fixes #8430

Investigation for memory left:

from copy import _deepcopy_dispatch, deepcopy

def _deepcopy_dispatch_tensor(x, memo, deepcopy=deepcopy):
      print(x) 
      return x

_deepcopy_dispatch[torch.Tensor] = _deepcopy_dispatch_tensor

and use the deepcopy on Trainer, model

Does your PR introduce any breaking changes ? If yes, please list them.

No.

Before submitting

  • Was this discussed/approved via a GitHub issue? (not for typos and docs)
  • Did you read the contributor guideline, Pull Request section?
  • Did you make sure your PR does only one thing, instead of bundling different changes together?
  • Did you make sure to update the documentation with your changes? (if necessary)
  • Did you write any new necessary tests? (not for typos and docs)
  • Did you verify new and existing tests pass locally with your changes?
  • Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)
  • Did you list all the breaking changes introduced by this pull request?

PR review

Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

  • Is this pull request ready for review? (if not, please submit in draft mode)
  • Check that all items from Before submitting are resolved
  • Make sure the title is self-explanatory and the description concisely explains the PR
  • Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

Make sure you had fun coding 🙃

@tchaton tchaton added the bug Something isn't working label Jul 20, 2021
@tchaton tchaton added this to the v1.4 milestone Jul 20, 2021
@tchaton tchaton self-assigned this Jul 20, 2021
@pep8speaks
Copy link

pep8speaks commented Jul 20, 2021

Hello @tchaton! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻

Comment last updated at 2021-07-21 08:49:52 UTC

@codecov
Copy link

codecov bot commented Jul 20, 2021

Codecov Report

Merging #8490 (2719d03) into master (ea13f60) will decrease coverage by 4%.
The diff coverage is 84%.

@@           Coverage Diff           @@
##           master   #8490    +/-   ##
=======================================
- Coverage      92%     88%    -4%     
=======================================
  Files         217     217            
  Lines       14367   14390    +23     
=======================================
- Hits        13260   12669   -591     
- Misses       1107    1721   +614     

CHANGELOG.md Outdated Show resolved Hide resolved
pytorch_lightning/trainer/trainer.py Outdated Show resolved Hide resolved
@tchaton tchaton enabled auto-merge (squash) July 20, 2021 18:36
@mergify mergify bot removed the has conflicts label Jul 20, 2021
Copy link
Contributor

@kaushikb11 kaushikb11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR breaking TPUs training. Looking into it.

@mergify mergify bot removed the ready PRs ready to be merged label Jul 21, 2021
@mergify mergify bot added the ready PRs ready to be merged label Jul 21, 2021
# while training on 8 and more cores.
for opt in self.optimizers:
for p, v in opt.state.items():
opt.state[p] = apply_to_collection(v, torch.Tensor, move_data_to_device, self.root_device)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kaushikb11 here you are calling self.root_device anyway, despite the comment above?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, not sure to understand the reasoning too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ready PRs ready to be merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Memory leak when training multiple models sequentially OOM issues
9 participants