You signed in with another tab or window. Reload to refresh you
8000
r session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Oh my God. I have trained on the multi-GPU version for one week with all of my four GPUs. In the params/flowavenet/ dir, only one checkpoint was generated.
Oops, sorry about the delayed issue post in this repo. Filed the report to the PyTorch repo about two weeks ago, so please stick to v0.4.1 until the issue is resolved.
Note: DistributedDataParallel implementation from @1ytic circumvents the multi-GPU issue, so please use train_apex.py of the master branch until the issue from DataParallel (from train.py) is resolved.
Activity
candlewill commentedon Dec 21, 2018
Oh my God. I have trained on the multi-GPU version for one week with all of my four GPUs. In the
params/flowavenet/dir, only one checkpoint was generated.Thanks for pointing out this.
L0SG commentedon Dec 21, 2018
Oops, sorry about the delayed issue post in this repo. Filed the report to the PyTorch repo about two weeks ago, so please stick to v0.4.1 until the issue is resolved.
L0SG commentedon Feb 12, 2019
Update: the issue still persists in the latest 1.0.1 release.
feat: Distributed Training implemented with Apex
L0SG commentedon Apr 23, 2019
Note:
DistributedDataParallelimplementation from @1ytic circumvents the multi-GPU issue, so please usetrain_apex.pyof the master branch until the issue fromDataParallel(fromtrain.py) is resolved.L0SG commentedon Oct 10, 2019
Update: the issue was fixed with the 1.2.0 release. We'll keep this issue open for a while for a future reference.