Main Content

Run Batch Parallel Jobs

Run a Batch Job

To offload work from your MATLAB® session to run in the background in another session, you can use the batch command inside a script.

  1. To create the script, type:

    edit mywave
  2. In the MATLAB Editor, create a for-loop:

    for i = 1:1024
      A(i) = sin(i*2*pi/1024);
    end
  3. Save the file and close the Editor.

  4. Use the batch command in the MATLAB Command Window to run your script on a separate MATLAB worker:

    job = batch('mywave')

    MATLAB client passing a batch command to the MATLAB worker.

  5. batch does not block MATLAB and you can continue working while computations take place. If you need to block MATLAB until the job finishes, use the wait function on the job object.

    wait(job)
  6. After the job finishes, you can retrieve and view its results. The load command transfers variables created on the worker to the client workspace, where you can view the results:

    load(job,'A')
    plot(A)
  7. When the job is complete, permanently delete its data and remove its reference from the workspace:

    delete(job)
    clear job

batch runs your code on a local worker or a cluster worker, but does not require a parallel pool.

You can use batch to run either scripts or functions. For more details, see the batch reference page.

Run a Batch Job with a Parallel Pool

You can combine the abilities to offload a job and run a loop in a parallel pool. This example combines the two to create a simple batch parfor-loop.

  1. To create a script, type:

    edit mywave
  2. In the MATLAB Editor, create a parfor-loop:

    parfor i = 1:1024
      A(i) = sin(i*2*pi/1024);
    end
  3. Save the file and close the Editor.

  4. Run the script in MATLAB with the batch command. Indicate that the script should use a parallel pool for the loop:

    job = batch('mywave','Pool',3)

    This command specifies that three workers (in addition to the one running the batch script) are to evaluate the loop iterations. Therefore, this example uses a total of four local workers, including the one worker running the batch script. Altogether, there are five MATLAB sessions involved, as shown in the following diagram.

    MATLAB client sending the batch command to the lead MATLAB worker to instruct three other workers to execute the script.

  5. To view the results:

    wait(job)
    load(job,'A')
    plot(A)

    The results look the same as before, however, there are two important differences in execution:

    • The work of defining the parfor-loop and accumulating its results are offloaded to another MATLAB session by batch.

    • The loop iterations are distributed from one MATLAB worker to another set of workers running simultaneously ('Pool' and parfor), so the loop might run faster than having only one worker execute it.

  6. When the job is complete, permanently delete its data and remove its reference from the workspace:

    delete(job)
    clear job

Run Script as Batch Job from the Current Folder Browser

From the Current Folder browser, you can run a MATLAB script as a batch job by browsing to the file’s folder, right-clicking the file, and selecting Run Script as Batch Job. The batch job runs on the cluster identified by the default cluster profile. The following figure shows the menu option to run the script file script1.m:

Context menu that appears after you right-click a MATLAB script in the Current Folder browser. The context menu shows the option to Run Script as Batch Job.

Running a script as a batch from the browser uses only one worker from the cluster. So even if the script contains a parfor loop or spmd block, it does not open an additional pool of workers on the cluster. These code blocks execute on the single worker used for the batch job. If your batch script requires opening an additional pool of workers, you can run it from the command line, as described in Run a Batch Job with a Parallel Pool.

When you run a batch job from the browser, this also opens the Job Monitor. The Job Monitor is a tool that lets you track your job in the scheduler queue. For more information about the Job Monitor and its capabilities, see Job Monitor.

See Also

Related Topics