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
After some fixes, the develop branch now supports MPI clusters (I haven't really had a good place to check this before). However, it's not very optimal, because currently there's no efficient resolved() implementation, because I don't know yet how to do a non-blocking MPI check to see whether a particular worker is ready or not. In the meanwhile, resolved() calls value(..., signal = FALSE) and then return TRUE. This means that resolved() is blocking for MPI-based cluster futures.
After some fixes, the develop branch now supports MPI clusters (I haven't really had a good place to check this before). However, it's not very optimal, because currently there's no efficient
resolved()
implementation, because I don't know yet how to do a non-blocking MPI check to see whether a particular worker is ready or not. In the meanwhile,resolved()
callsvalue(..., signal = FALSE)
and then return TRUE. This means thatresolved()
is blocking for MPI-based cluster futures.Example:
The text was updated successfully, but these errors were encountered: