| Products & Services | Solutions | Academia | Support | User Community | Company |
| Download Product Updates | | | Get Pricing | | | Trial Software |
| Documentation → Parallel Computing Toolbox |
| Contents | Index |
| Learn more about Parallel Computing Toolbox |
The name of the parameter in the mdce_def file that defines the location of the job manager and worker checkpoint directories.
Location where job manager checkpoint information and worker checkpoint information is stored.
The MATLAB session that defines and submits the job. This is the MATLAB session in which the programmer usually develops and prototypes applications. Also known as the MATLAB client.
The computer running the MATLAB client.
A collection of computers that are connected via a network and intended for a common purpose.
An application for which run time is significantly greater than the communication time needed to start and stop the program. Coarse-grained distributed applications are also called embarrassingly parallel applications.
An array partitioned into segments, with each segment residing in the workspace of a different lab.
An object in a MATLAB client session that provides access to data values stored on the labs in a MATLAB pool, such as the values of variables that are assigned inside an spmd statement.
A system with one or more processors.
The same application that runs independently on several nodes, possibly with different input parameters. There is no communication, shared data, or synchronization points between the nodes. Distributed applications can be either coarse-grained or fine-grained.
Computing with distributed applications, running the application on several nodes simultaneously.
Demonstration programs that use Parallel Computing Toolbox software, as opposed to sequential demos.
Domain Name System. A system that translates Internet domain names into IP addresses.
The ability of a MATLAB worker or lab to employ all the functionality you are licensed for in the MATLAB client, while checking out only an engine license. When a job is created in the MATLAB client with Parallel Computing Toolbox software, the products for which the client is licensed will be available for all workers or labs that evaluate tasks for that job. This allows you to run any code on the cluster that you are licensed for on your MATLAB client, without requiring extra licenses for the worker beyond MATLAB Distributed Computing Server software. For a list of products that are not eligible for use with Parallel Computing Toolbox software, see http://www.mathworks.com/products/ineligible_programs/.
An application for which run time is significantly less than the communication time needed to start and stop the program. Compare to coarse-grained applications.
Usually, the node of the cluster designated for running the job manager and license manager. It is often useful to run all the nonworker related processes on a single machine.
A cluster that is not homogeneous.
A cluster of identical machines, in terms of both hardware and software.
The complete large-scale operation to perform in MATLAB, composed of a set of tasks.
The MathWorks process that queues jobs and assigns tasks to workers. A third-party process that performs this function is called a scheduler. The general term "scheduler" can also refer to a job manager.
Snapshot of information necessary for the job manager to recover from a system crash or reboot.
The database that the job manager uses to store the information about its jobs and tasks.
The process that allows clients, workers, and job managers to find each other. It starts automatically when the job manager starts.
When workers start, they work independently by default. They can then connect to each other and work together as peers, and are then referred to as labs.
The name of the parameter in the mdce_def file that defines the directory where logs are stored.
See job manager.
See client.
A collection of labs that are reserved by the client for execution of parfor-loops or spmd statements. See also lab.
See worker.
The service that has to run on all machines before they can run a job manager or worker. This is the engine foundation process, making sure that the job manager and worker processes that it controls are always running.
Note that the program and service name is all lowercase letters.
The file that defines all the defaults for the mdce processes by allowing you to set preferences or definitions in the form of parameter values.
Message Passing Interface, the means by which labs communicate with each other while running tasks in the same job.
A computer that is part of a cluster.
The same application that runs on several labs simultaneously, with communication, shared data, or synchronization points between the labs.
An array which resides in the workspaces of one or more, but perhaps not all labs. There might or might not be a relationship between the values of these arrays among the labs.
A random unprivileged TCP port, i.e., a random TCP port above 1024.
The action that happens when both worker and job manager are started and the worker contacts job manager.
An array which resides in the workspaces of all labs, and whose size and content are identical on all labs.
The process, either third-party or the MathWorks job manager, that queues jobs and assigns tasks to workers.
A block of code that executes simultaneously on multiple labs in a MATLAB pool. Each lab can operate on a different data set or different portion of distributed data, and can communicate with other participating labs while performing the parallel computations.
One segment of a job to be evaluated by a worker.
An array which resides in the workspaces of all labs, but whose content differs on these labs.
The MATLAB session that performs the task computations. Also known as the MATLAB worker or worker process.
Files required by the worker during the execution of tasks.
![]() | WorkerMachineOsType |

Includes the most popular MATLAB recorded presentations with Q&A sessions led by MATLAB experts.
| © 1984-2009- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |