systemml-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Parfor semantics
Date Mon, 21 Nov 2016 23:33:26 GMT
While debugging some ParFor code it became clear that the parameters for 
parfor can be easily overwritten by the optimizer.
One example is when I write:

parfor (i in 1:10, par=10, mode=REMOTE_SPARK) {
     // some code here

Depending on the data size and cluster resources, the optimizer 
(, line 844) will recognize that the work can be 
done locally and overwrite it to local execution. This might be valid 
and definitely works (in my case) but kind of contradicts what I want 
SystemML to do.
I wonder if we should disable this optimization in case a concrete 
execution mode is given and go with the mode that is provided.


View raw message