|Matlab Distributed Computing Engine (DCE) - Known Errors and Limitations|
Page 7 of 7
In the log file output there is an expected error that can be ignored, the MATLAB core dump. The core dump is a debug message that will be turned off in the a future release:MATLAB core dump: Exit on fatal error (no core) enabled.
A limitation in the current Matlab parallel submissions is the inability to mix use of the "Matlab parallel" calls, i.e., labindex, labnum, labBroadcast, etc., with the use of the new automatically distributed parfor call. This limitation will hopefully be fixed in upcoming releases.
If you do image processing in Matlab and wish to parallelize the code, please note that both the interactive (pmode) and noninteractive (cluster) environments start with "-noFigureWindows" option, so much of the printing code behaves differently. There are a few workarounds but do not always perform as expected.
The Matlab DCE also does not communicate over the Infiniband high speed network on the cluster. This should not impact the performance of your parallel code too much because Matlab's main parallel scheme is independent distribution (i.e., the parfor loop distribution relies on the independence of the loop variables). Possibly in future releases we can incorporate the high speed network.