You signed in with another tab or window. Reload to refresh your 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
Hi, there are two instances of dist.all_reduce() in diff_model_train.py.
One for scale_factor using ReduceOp.AVG, and one for loss_torch, using ReduceOp.SUM.
However, one uses dist.barrier() before dist.all_reduce() and one doesn't.
I have three short questions regarding this usage in this scenario.
1, Why is dist.barrier() not needed for loss_torch SUM?
2, Is there a reason why SUM is used instead of AVG for loss?
3, If iteration-level losses are added, should dist.barrier() be added for iteration-level loss dist.all_reduce(), SUM or AVG?
Thank you.
The text was updated successfully, but these errors were encountered:
Hi, there are two instances of dist.all_reduce() in diff_model_train.py.
One for scale_factor using ReduceOp.AVG, and one for loss_torch, using ReduceOp.SUM.
However, one uses dist.barrier() before dist.all_reduce() and one doesn't.
I have three short questions regarding this usage in this scenario.
1, Why is dist.barrier() not needed for loss_torch SUM?
2, Is there a reason why SUM is used instead of AVG for loss?
3, If iteration-level losses are added, should dist.barrier() be added for iteration-level loss dist.all_reduce(), SUM or AVG?
Thank you.
The text was updated successfully, but these errors were encountered: