A bunch of helper functions for transferring data between worker processes. The functions are robust with safety measures built into the commands, and the package is thoroughly tested to ensure correctness (with an unsafe API coming soon). As such, this commands thus allow for rapid development and prototyping of parallel algorithms. The underlying infrustructure is Julia's native multiprocess parallelism, meaning that no dependencies are required for use other than Base Julia.
To install the package, simply use:
Pkg.add("ParallelDataTransfer") addprocs(n) # Adds n processes @everywhere using ParallelDataTransfer
For the most up to date version, checkout master by using:
For examples of usage, please see the tests.
# Creates an integer x and Matrix y on processes 1 and 2 sendto([1, 2], x=100, y=rand(2, 3)) # Create a variable here, then send it everywhere else z = randn(10, 10); sendto(workers(), z=z) # Create the variable x with a value 3 directly on process 4 @defineat 4 x=3 # Broadcast a value 3 to x on all workers @broadcast x=3 # Note that @broadcast will broadcast the expression, so @broadcast name=val # Requires val to be defined on the remote process # To pass an object to all worker processes, use @passobj 1 workers() name # Get an object from named x from Main module on process 2. Name it y y = @getfrom 2 x # Or y = getfrom(2,:x) # Get an object from named x from Foo module on process 2. Name it y y = @getfrom 2 x Foo # Or y = getfrom(2,:x,Foo) # Get an object from named foo.x from Foo module on process 2. Name it y y = @getfrom 2 foo.x Foo # Using the function will not work! # pass variable named x from process 2 to all other processes @passobj 2 filter(x->x!=2, procs()) x # Or passobj(2, filter(x->x!=2, procs()), :x) # pass variables t, u, v from process 3 to process 1 passobj(3, 1, [:t, :u, :v]) # Pass a variable from the `Foo` module on process 1 to Main on workers @passobj 1 workers() Foo.foo #Or passobj(1, workers(), [:foo]; from_mod=Foo)
Note that this form of passing variables will define the variables in the global namespace of the process. Thus, for performance reasons, it's recommended that these variables are acted on inside of a function (just like in the REPL). An example for doing this is:
# Send things to process 2 @defineat 2 a=5 @defineat 2 function usea(a) # Do your stuff here ans=a end # Use the function a on process 2 @defineat 2 ans=usea(a) # this safely uses the usea and a from process 2 # Get the answer from process 2 @getfrom 2 ans
In the "master" process this will define
ans as a global. Once again, you should
not work directly with the global since that will degrade the performance. So,
since you are working in a function, you should assert the type of the variable
so that way it's strictly typed. For example:
function test() @defineat 2 a=5 a = (@getfrom 2 a)::Int64 # This will make a stictly typed if test is type-stable # Continue in your code using b a end
Declaring the type of
a will work as well. If you put these two design principles
together (use the passed variables in a function, and type the returns), then your
code will be parallel and type-stable.
I am interested in suggestions for making this usage more "automatic". If you have design ideas / implementations to recommend, feel free to open issues and submit PRs.
This library is developed and maintained by Chris Rackauckas. However, kudos go to @spencerlyon2 and @conjectures for developing some of the original solutions which were modified and expanded upon for this library. Special thanks to @TotalVerb and @oxinabox for help via Gitter.
6 days ago