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
@tjruwase Currently we are doing a communication profiling with different zero stages (1,2,3) using GPT-NeoX 19M config. We enabled comms_logger to look at the actual collectives being called, their message size distribution and frequency.
As per our understanding, zero-1 should use allgather + reduce-scatter to implement gradient allreduce, however, we are seeing one large message size allreduce in our profiling results, is there a specific reason for allreduce instead of reduce-scatter + allgather?
same thing also happend with zero-2, it is only calling allreduce.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
@tjruwase Currently we are doing a communication profiling with different zero stages (1,2,3) using GPT-NeoX 19M config. We enabled comms_logger to look at the actual collectives being called, their message size distribution and frequency.
As per our understanding, zero-1 should use allgather + reduce-scatter to implement gradient allreduce, however, we are seeing one large message size allreduce in our profiling results, is there a specific reason for allreduce instead of reduce-scatter + allgather?
same thing also happend with zero-2, it is only calling allreduce.
ZeRO-1
config:
ZeRO-2
config:
@Quentin-Anthony @jahatef @BTMichalowicz
Beta Was this translation helpful? Give feedback.
All reactions