-
Notifications
You must be signed in to change notification settings - Fork 113
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
Multi-GPU training #9
Comments
Hi, I believe the multi-GPU issue is fixed since torch==1.4.0, but I am not 100% sure, see pytorch/pytorch#15716. If you want to try multi-GPU training you could try the nn.DataParallel wrapper for the model. I did not bother yet with multi-GPU training as training time is much shorter than with the original Tacotron. Keep me posted if you try it! |
Hi, I managed to get multi-GPU training working using nn.DataParallel, but I should be missing something. Performance decreased from ~4.0 steps/s on single-GPU to 0.46 steps/s on 2-GPUs (same batch size, just split into 2). I basically added this to train_tacotron.py
It also uses significantly more GPU memory (specially on GPU 1) |
If my implementation is correct, I think the multi-GPU training introduces a big overhead. Unfortunately I have no more clues. I have gone for gradient accumulation to enable using larger batch sizes on small GPUs. Thanks for your help :) |
Hi, thanks for sharing your work!
Do you have any idea how to get multi-GPU training working? I looked at how it is implemented on fatchord's original repo, but doesn't seem to work well:
Thanks in advance!
The text was updated successfully, but these errors were encountered: