User`s guide

parpool
11-239
More About
Tips
• The pool status indicator in the lower-left corner of the desktop shows the client
session connection to the pool and the pool status. Click the icon for a menu of
supported pool actions.
With a pool running: With no pool running:
• If you set your parallel preferences to automatically create a parallel pool when
necessary, you do not need to explicitly call the parpool command. You might
explicitly create a pool to control when you incur the overhead time of setting it up, so
the pool is ready for subsequent parallel language constructs.
• delete(poolobj) shuts down the parallel pool. Without a parallel pool, spmd and
parfor run as a single thread in the client, unless your parallel preferences are set to
automatically start a parallel pool for them.
• When you use the MATLAB editor to update files on the client that are attached to a
parallel pool, those updates automatically propagate to the workers in the pool. (This
automatic updating does not apply to Simulink model files. To propagate updated
model files to the workers, use the updateAttachedFiles function.)
• When connected to a parallel pool, the following commands entered in the client
Command Window also execute on all the workers in the pool:
• cd
• addpath
• rmpath
This behavior allows you to set the working folder and the command search path on
all the workers, so that subsequent parfor-loops execute in the proper context.
If any of these commands does not work on the client, it is not executed on the
workers either. For example, if addpath specifies a folder that the client cannot
access, the addpath command is not executed on the workers. However, if the
working directory or path can be set on the client, but cannot be set as specified on
any of the workers, you do not get an error message returned to the client Command
Window.