Should I close the matlabpool

I have an external application open an MCR, call "matlabpool open", run parallel code and quit the matlab. The above may occur several times before a complete shutdown.

Should I run "matlabpool close" before quiting matlab? Or is the matlabpool automatically being closed?

I'm using version 2012a.

Answer 1

[Richard Alcock]

The pool should notice when the client MCR (or client MATLAB) goes away and will effectively be closed at that point - the cluster's resources will be released. But calling matlabpool close makes it clearer what your intent is and gives the pool the chance to close cleanly.