-
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
Clean up last ModelCheckpoint
makedirs
call to IOPlugin
#11035
Conversation
@property | ||
def should_rank_save_checkpoint(self) -> bool: | ||
return self.training_type_plugin.should_rank_save_checkpoint | ||
|
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.
since this is publicly exposed, this needs to go through a deprecation process
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.
noted in summary with context
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.
thanks for adding the context! i believe the initial removal was incorrect, and we should honor the deprecation process
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.
What does this PR do?
see comment:
now that we have XLACheckpointIO:
makedirs
call inModelCheckpoint
to IOPluginshould_rank_save_checkpoint
property from Trainer #9433 directly removed trainer propertyshould_rank_save_checkpoint
. It was added back in PR [2/n] Directly call TrainingTypePlugin APIs instead of going through the Accelerator #9901, though it's not used anywhere, I think just from a merging issue. This time should we remove or deprecate it?-- if deprecate, definitely separate PR
SingleTPUPlugin.save()
which is not used/needed anymore as its functionality moved toXLACheckpointIO
.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 Review guidelines. In short, see the following bullet-list:
Did you have fun?
Make sure you had fun coding 🙃