Avoiding parallel pool opening times

I am administrating a server in which I allow Matlab programs to be executed from time to time. The Matlab applications are first compiled using the mcc command and they are later executed from the command line with the help of the Matlab Runtime. However, every time an application is loaded, if it uses parfor to parallelize the code, the Matlab Runtime opens a Matlab parallel pool which takes considerably (around 25 seconds to connect to all the workers). Is it possible to have one of this Parallel Pools always open (on a separate, always open Matlab process for example) and force every application to "connect"/"use" it? What is the procedure normally used in these cases? Thanks in advance

Answer 1

[Walter Roberson]

http://www.mathworks.com/matlabcentral/answers/163438-parpool-local-too-slow

But I know there is also a way to set up a timeout with clusters so that the cluster does not need to come up every time. I am having difficulty finding that information now though.

There is also the MATLAB Production Server which must logically have some kind of mechanism to avoid having to reinitialize sessions all of the time; I have not looked at how it works.

[Nicolò Calafiore]

I'm also interested in this procedure, does anyone have any news?