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.

Sign up for GitHub

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

Jump to bottom

Commenting out loss=None causes much higher GPU memory usage in bing_bert. #547

Open
szhengac opened this issue Nov 21, 2020 · 0 comments
Open

Commenting out loss=None causes much higher GPU memory usage in bing_bert. #547

szhengac opened this issue Nov 21, 2020 · 0 comments

Comments

@szhengac
Copy link
Contributor

I found that if I comment out loss = None in https://github.com/microsoft/DeepSpeedExamples/blob/fa1d1a71c48623db8a091d9cf636a5fe3b8f43c7/bing_bert/deepspeed_train.py#L176, the GPU memory usage increases significantly. It seems the GPU memory is accumulated with the next batch without manually dereferencing the object but I don't recall that we need this line in pure pytorch training code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@szhengac