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

Fix move_metrics_to_cpu with evaluation #10631

Merged
merged 4 commits into from
Nov 22, 2021
Merged

Conversation

carmocca
Copy link
Contributor

@carmocca carmocca commented Nov 19, 2021

What does this PR do?

Fixes the bug uncovered by the analysis here: #10595 (comment)

  • The outputs are no longer moved to CPU with move_metrics_to_cpu=True. This is consistent with how the training loops work.
  • The recursive detach() call has been removed, it's not necessary as gradients arent computed during evaluation.
  • move_metrics_to_cpu=True now actually moves the metrics to CPU. This is consistent with how the training loops work.

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

  • If the user relies on the outputs being on CPU in {validation,test}_epoch_end.
  • If the user memory blows up due to this change. Keep in mind that the user is always able to do return your_tensor_on_gpu.cpu().

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?
  • [n/a] 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 list all the breaking changes introduced by this pull request?
  • Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

  • 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

cc @Borda @carmocca @edward-io @ananthsub @awaelchli

@carmocca carmocca added bug Something isn't working logging Related to the `LoggerConnector` and `log()` trainer: validate trainer: test labels Nov 19, 2021
@carmocca carmocca added this to the 1.5.x milestone Nov 19, 2021
@carmocca carmocca self-assigned this Nov 19, 2021
@github-actions
Copy link
Contributor

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

@codecov
Copy link

codecov bot commented Nov 19, 2021

Codecov Report

Merging #10631 (67b8c26) into master (5788789) will decrease coverage by 4%.
The diff coverage is 60%.

@@           Coverage Diff            @@
##           master   #10631    +/-   ##
========================================
- Coverage      92%      88%    -4%     
========================================
  Files         178      178            
  Lines       16266    16303    +37     
========================================
- Hits        14923    14339   -584     
- Misses       1343     1964   +621     

@carmocca carmocca enabled auto-merge (squash) November 19, 2021 17:03
Copy link
Contributor

@tchaton tchaton left a comment

Choose a reason for hiding this comment

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

LGTM !

@mergify mergify bot added the ready PRs ready to be merged label Nov 22, 2021
@carmocca carmocca deleted the bugfix/move-metrics-cpu-eval branch November 22, 2021 15:58
rohitgr7 pushed a commit that referenced this pull request Nov 22, 2021
awaelchli pushed a commit that referenced this pull request Nov 24, 2021
lexierule pushed a commit that referenced this pull request Nov 24, 2021
@rohitgr7 rohitgr7 mentioned this pull request Feb 7, 2022
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working logging Related to the `LoggerConnector` and `log()` ready PRs ready to be merged trainer: test trainer: validate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants