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

[Question] What is the purpose of "always" checkpointing mode? #24

Open
pritamdamania87 opened this issue Nov 30, 2020 · 1 comment
Open
Assignees
Labels
question Further information is requested

Comments

@pritamdamania87
Copy link

The user guide mentions the following:

Usually, checkpointing at the last micro-batch may not be useful because the saved memory will be reconstructed immediately. That’s why we choose 'except_last' as the default option.

It seems like using the mode "always" might not have any benefit, are there some cases where it makes sense to use "always" instead of "exception_last"?

@sublee
Copy link
Contributor

sublee commented Dec 2, 2020

I agree that "always" might have no benefit for most cases. However, for a special case chunks=1, it is useful to compare performance with and without checkpointing, because every chunk is the last chunk if there is only one chunk.

@sublee sublee added the question Further information is requested label Dec 2, 2020
@sublee sublee self-assigned this Dec 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants