Hi Tim, thank you for your response. My question is more about the communication that happens in between @async and @sync. In my case every worker has one parameter and has an old version of the parameter associated with the other workers. Say worker i updates his own parameter couple of times and then decides to send his parameter to worker j in order for worker j to update the parameter associated with worker i. Every so often there is also synchronisation event where all workers synchronise or say all the workers on one machine synchronise. It seems cumbersome to achieve this with remote references.
Sebastian On 4 Aug 2015, at 11:14, Tim Holy <tim.h...@gmail.com> wrote: > Do the @async and @sync macros cover that for you? > > --Tim > > On Tuesday, August 04, 2015 12:45:26 AM Sebastian Vollmer wrote: >> Is it possible to implement P2P parallel computing in Julia so that never >> all processes have to synchronize at the same time (except at the end of >> the computation)? >> >> In the docs it reads: >> >> Julia’s implementation of message passing is different from other >> environments such as MPI. Communication in Julia is generally “one-sided”, >> meaning that the programmer needs to explicitly manage only one process in >> a two-process operation. Furthermore, these operations typically do not >> look like “message send” and “message receive” but rather resemble >> higher-level operations like calls to user functions. >> >> Thank you, >> >> Sebastian >
