-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Do not force sync_dist=True
on epoch end
#13364
Merged
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
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
krishnakalyan3
requested review from
tchaton,
carmocca,
williamFalcon,
Borda,
SeanNaren,
awaelchli,
justusschock,
kaushikb11 and
rohitgr7
as code owners
July 12, 2022 12:32
rohitgr7
added
logging
Related to the `LoggerConnector` and `log()`
breaking change
Includes a breaking change
labels
Jul 12, 2022
rohitgr7
approved these changes
Jul 12, 2022
otaj
approved these changes
Jul 12, 2022
carmocca
reviewed
Jul 12, 2022
src/pytorch_lightning/trainer/connectors/logger_connector/result.py
Outdated
Show resolved
Hide resolved
src/pytorch_lightning/trainer/connectors/logger_connector/result.py
Outdated
Show resolved
Hide resolved
tests/tests_pytorch/trainer/logging_/test_distributed_logging.py
Outdated
Show resolved
Hide resolved
tests/tests_pytorch/trainer/logging_/test_distributed_logging.py
Outdated
Show resolved
Hide resolved
tests/tests_pytorch/trainer/logging_/test_distributed_logging.py
Outdated
Show resolved
Hide resolved
tests/tests_pytorch/trainer/logging_/test_distributed_logging.py
Outdated
Show resolved
Hide resolved
…lt.py Co-authored-by: Carlos Mocholí <[email protected]>
mergify
bot
added
ready
PRs ready to be merged
and removed
ready
PRs ready to be merged
labels
Jul 16, 2022
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
rohitgr7
reviewed
Jul 18, 2022
carmocca
approved these changes
Jul 19, 2022
tests/tests_pytorch/trainer/logging_/test_distributed_logging.py
Outdated
Show resolved
Hide resolved
rohitgr7
changed the title
Do not force sync_dist=True on epoch end
Do not force Jul 19, 2022
sync_dist=True
on epoch end
mergify
bot
added
ready
PRs ready to be merged
and removed
has conflicts
ready
PRs ready to be merged
labels
Jul 22, 2022
Codecov Report
@@ Coverage Diff @@
## master #13364 +/- ##
=========================================
- Coverage 86% 76% -10%
=========================================
Files 327 327
Lines 25500 25505 +5
=========================================
- Hits 21898 19455 -2443
- Misses 3602 6050 +2448 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
breaking change
Includes a breaking change
logging
Related to the `LoggerConnector` and `log()`
pl
Generic label for PyTorch Lightning package
ready
PRs ready to be merged
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.
Fixes #13210
Just FYI, with fault-tolerant training, we need to ensure sync happens because during a failure on, let's say, a spot instance, the metrics are synced and saved to the checkpoint, so during restart, metrics on rank 0 are from the accumulated ones from the previous run, and on other ranks, they are 0. So we need to make sure they are synced in further training to ensure correct calculation.
Does your PR introduce any breaking changes? If yes, please list them.
Before submitting
PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:
Did you have fun?
Make sure you had fun coding 🙃