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
In DDPStrategy / FSDPStrategy, the timeout=datetime.timedelta(seconds=1800) flag is exposed and thus allowing user to tune. However, in DeepSpeedStrategy, which is a subclass of DDPStrategy, this flag is not exposed, which makes it hard to change the timeout behavior.
Is there any workaround? Otherwise, I think it might be worth adding kwargs to the __init__() function of DeepSpeedStrategy, and pass along those parameters to the parent class DDPStrategy.
Outline & Motivation
In DDPStrategy / FSDPStrategy, the
timeout=datetime.timedelta(seconds=1800)
flag is exposed and thus allowing user to tune. However, in DeepSpeedStrategy, which is a subclass of DDPStrategy, this flag is not exposed, which makes it hard to change the timeout behavior.Is there any workaround? Otherwise, I think it might be worth adding
kwargs
to the__init__()
function of DeepSpeedStrategy, and pass along those parameters to the parent class DDPStrategy.Pitch
No response
Additional context
No response
cc @Borda @awaelchli @justusschock
The text was updated successfully, but these errors were encountered: