Skip to content
Snippets Groups Projects
Commit eee2f37d authored by Jan Siwiec's avatar Jan Siwiec
Browse files

Update capacity-computing.md minor formatting changes

parent 1a61be63
Branches
Tags
4 merge requests!368Update prace.md to document the change from qprace to qprod as the default...,!367Update prace.md to document the change from qprace to qprod as the default...,!366Update prace.md to document the change from qprace to qprod as the default...,!323extended-acls-storage-section
...@@ -267,7 +267,7 @@ While job arrays are able to utilize all available computational nodes, the GNU ...@@ -267,7 +267,7 @@ While job arrays are able to utilize all available computational nodes, the GNU
### GNU Parallel, Shared jobscript ### GNU Parallel, Shared jobscript
A combined approach, very similar to job arrays, can be taken. A job array is submitted to the queuing system. The subjobs run GNU parallel. The GNU parallel shell executes multiple instances of the jobscript using all of the cores on the node. The instances execute different work, controlled by the $PBS_JOB_ARRAY and the $PARALLEL_SEQ variables. A combined approach, very similar to job arrays, can be taken. A job array is submitted to the queuing system. The subjobs run GNU parallel. The GNU parallel shell executes multiple instances of the jobscript using all of the cores on the node. The instances execute different work, controlled by the `$PBS_JOB_ARRAY` and the `$PARALLEL_SEQ` variables.
Example: Example:
...@@ -315,7 +315,7 @@ cat input > output ...@@ -315,7 +315,7 @@ cat input > output
cp output $PBS_O_WORKDIR/$TASK.out cp output $PBS_O_WORKDIR/$TASK.out
``` ```
In this example, the jobscript executes in multiple instances in parallel, on all cores of a computing node. The $TASK variable expands to one of the input filenames from the tasklist. We copy the input file to local scratch memory, execute myprog.x and copy the output file back to the submit directory, under the $TASK.out name. The numtasks file controls how many tasks will be run per subjob. Once a task is finished, a new task starts, until the number of tasks in the numtasks file is reached. In this example, the jobscript executes in multiple instances in parallel, on all cores of a computing node. The `$TASK` variable expands to one of the input filenames from the tasklist. We copy the input file to local scratch memory, execute myprog.x and copy the output file back to the submit directory, under the $TASK.out name. The numtasks file controls how many tasks will be run per subjob. Once a task is finished, a new task starts, until the number of tasks in the numtasks file is reached.
!!! note !!! note
Select the subjob walltime and the number of tasks per subjob carefully Select the subjob walltime and the number of tasks per subjob carefully
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment