MATLAB Answers

Parallel Computing Toolbox - Java object transfer from client to workers

12 views (last 30 days)
Stefano C
Stefano C on 21 Jul 2015
Edited: Stefano C on 27 Jul 2015
My problem regards the usage of the Parallel Computing Toolbox functions, and in particular the variable transfer from client to workers when the "variable" is a Java object. I have experieced that, without multithreading, passing a Java object from a main script to a function is not a problem, while using (for instance) parfeval to implement multithreading, the object is not passed correctly resulting in the error "Attempt to reference field of non-structure array", because the object structure is lost. Something similar happens to me also trying to implement multithreading exploiting a parfor cycle, therefore I suspect it may be a generalized issue with the usage of Matlab multithreading tools. May I kindly have any clarification with this regards?

  0 Comments

Sign in to comment.

Accepted Answer

Edric Ellis
Edric Ellis on 21 Jul 2015
When you pass any MATLAB variables (including those that refer to Java objects) into parfor, parfeval, etc., then the contents of those variables need to be transmitted to a separate MATLAB process. The effect is the same as if you saved the variables to a .mat file and then loaded them. Not all MATLAB variables can be saved and loaded successfully - and those same variables will not function correctly with parfor, parfeval etc.
I recommend that you should construct such objects on the workers (i.e. inside parfor, parfeval, ...).
You might wish to use the Worker Object Wrapper to avoid constructing the same object multiple times on the workers.

  4 Comments

Show 1 older comment
Edric Ellis
Edric Ellis on 23 Jul 2015
You should call
CV(fold) = parfeval(p, @CVloop, 2, wrapperData, numFolds, fold);
to send the whole wrapper to the worker, and then only on the worker pick out the .Value field. (And just to be sure - you should be creating the WorkerObjWrapper and calling parfeval at the client).
Stefano C
Stefano C on 26 Jul 2015
Thanks a lot Edric, sending the whole wrapper I now get a different error:
Error using WorkerObjWrapper
Too many input arguments.
Error in main (line 62)
wrapperData = WorkerObjWrapper(@generateDataset, WPATH, fName, numFolds);
It seems there is a sort of issue calling the wrapped function with multiple arguments, do you know why?
EDIT:
I have been able to solve this last question looking at the code of WorkerObjWrapper:
% W = WORKEROBJWRAPPER( FCN, ARGSCELL ) creates a WorkerObjWrapper by
% invoking FCN inside an SPMD block, supplying ARGSCELL as
% arguments. I.e., W.Value has the value obtained from running
% FCN(ARGSCELL{:}) on the workers.
Hence, for the posterity, in case the wrapped function has multiple inputs, WorkerObjWrapper has to be called in this way:
FcnArgs = {arg1, arg2, arg3, ...};
wrapperData = WorkerObjWrapper(@Fcn, FcnArgs);
Stefano C
Stefano C on 27 Jul 2015
Excuse me Edric, despite having (I think) correctly instantiated the objects wrappers on the client and picked out the .Value on the workers, still WorkerObjWrapper does not seem to work, I now get the error:
Error in main (line 90)
[completedFold,value] = fetchNext(CV);
Caused by:
Error using WorkerObjWrapper/get.Value (line 109)
Assertion failed.
kindly, would you know what it may depend upon?

Sign in to comment.

More Answers (0)

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by