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
Used the SimpleProfiler while training a model with DDP, and found that the constituent times of the functions did not add up to the total. Is this a bug?
Alternatively, do these calls each represent one GPU's worth of profiling? Like, should I multiply each of the function calls by my number of GPU's (4 in this case) to get a better estimate?
Alternatively alternatively, should I view the bulk of the 'total time' as the 'cost' of the DDP spin-up? If so, should this be documented somewhere?
This issue has been automatically marked as stale because it hasn't had any recent activity. This issue will be closed in 7 days if no further activity occurs. Thank you for your contributions - the Lightning Team!
Bug description
Used the SimpleProfiler while training a model with DDP, and found that the constituent times of the functions did not add up to the total. Is this a bug?
Alternatively, do these calls each represent one GPU's worth of profiling? Like, should I multiply each of the function calls by my number of GPU's (4 in this case) to get a better estimate?
Alternatively alternatively, should I view the bulk of the 'total time' as the 'cost' of the DDP spin-up? If so, should this be documented somewhere?
cc @carmocca @kaushikb11 @ninginthecloud @rohitgr7 @nbcsm @guotuofeng
The text was updated successfully, but these errors were encountered: