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

Is train loop memory-efficient? #253

Open
GLivshits opened this issue Aug 12, 2021 · 1 comment
Open

Is train loop memory-efficient? #253

GLivshits opened this issue Aug 12, 2021 · 1 comment

Comments

@GLivshits
Copy link

Hi. I've found, that you unfreeze the whole GAN, and making steps only via specific optimizer (for generator and discriminator). But when you do loss.backward, gradients are computed for the WHOLE GAN, whereas for certain optimizer only their own gradients are needed. It causes additional memory uses and increased iteration time.
Please correct me if I am wrong.

@Cads182
Copy link

Cads182 commented Sep 5, 2021

Totally not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants