Difference between revisions of "Ada:Batch Job Files"
m (→Job files)
m (→Job files)
|Line 23:||Line 23:|
===Example Job 1===
===Example Job 1===
Revision as of 10:42, 4 August 2016
A user's request to do processing via the batch system is commonly, though not exclusively, expressed
in a text file, called from here on, job file, job script, or just job. This file contains LSF directives and
executable lines: user-specified UNIX commands/scripts and other program executables. The directives, one per line, are all prefaced by the #BSUB string. The rest
of the directive can include the specification of any number of job parameters/options,
many of which have values associated with them. The user-specified commands can be any combination of
user-supplied executables and UNIX Shell commands.
Unless otherwise specified, a job inherits the environment of the submitting process. First and foremost in that regard are: the shell (captured by the $SHELL environment variable) that will execute your batch script, the current working directory ($CWD), and the command search path ($PATH). If desired, you can change these and other environment settings. We recommend that you not change the default bash shell, unless for some good reason you must. All this concerns the inherited settings. LSF does add, however, several new environment variables. For more details, please see the Environment Variables subsection.
Recommended Job File Format
#BSUB -option1 value1 -option2 value2 ... #BSUB ... more options ... # # ... end of BSUB directives: a blank or comment line # ## 1st non-BSUB executable line: You can change here the default environment settings: SHELL, CWD, PATH, etc. # Executable line 1 Executable line 2 ...
Example Job 1
#BSUB -J myjob1 # sets the job name to myjob1. #BSUB -L /bin/bash # uses the bash login shell to initialize the job's execution environment. #BSUB -W 12:30 # sets to 12.5 hours the job's runtime wall-clock limit. #BSUB -n 1 # assigns 1 core for execution. #BSUB -o stdout1.%J # directs the job's standard output to stdout1.jobid ## # <--- at this point the current working directory is the one you submitted the job from. # module load intel # loads the INTEL software tool chain to provide, among other things, # needed runtime libraries for the execution of prog.exe below. # (assumes prog.exe was compiled using INTEL compilers.) # prog.exe < input1 >& data_out1 # both input1 and data_out1 reside in the job submission dir ##
In the above job, memory specification is missing. In this case, LSF will schedule the job on any node with one idle core. The per-process memory limit will be 2.5GB, the default. If it is exceeded, the job will fail. Even if this process limit is not exceeded, since the job does not specify how much memory to reserve, it risks running slowly because of memory contention from other jobs scheduled on the same node. Job memory specification is an important issue. Please read the Memory Specifications subsection for more information.
Example Job 2
#BSUB -J myjob2 # sets the job name to myjob1. #BSUB -L /bin/bash # uses the bash login shell to initialize the job's execution environment. #BSUB -W 12:30 # sets to 12.5 hours the job's runtime wall-clock limit. #BSUB -n 3 # assigns 3 cores for execution. #BSUB -R "span[ptile=3]" # assigns 3 cores per node. #BSUB -R "rusage[mem=5000]" # reserves 5000MB per process/CPU for the job (i.e., 15,000 MB for job/node) #BSUB -M 5000 # sets to 5,000MB (~5GB) the per process enforceable memory limit. #BSUB -o stdout1.%J # directs the job's standard output to stdout1.jobid #BSUB -P project_ID # This is the project number against which the used service units (SUs) are charged. #BSUB -u e-mail_address # sends email to the specified address (e.g., firstname.lastname@example.org, # email@example.com) with information about main job events (next line). #BSUB -B -N # send emails on job begin (-B) and end (-N) ## cd $SCRATCH/myjob1 # makes $SCRATCH/myjob1 the job's current working directory where all # the needed files (e.g., prog.exe, input1, data_out1) are placed. module load intel # loads the INTEL software tool chain to provide, among other things, # needed runtime libraries for the execution of prog.exe below. # (assumes prog.exe was compiled using INTEL compilers.) # # The next 3 lines concurrently execute 3 instances of the same program, prog.exe, with # standard input and output data streams assigned to different files in each case. This style # of concurrent execution can be extended up to 20-way or 40-way on nodes with 20 cores # and 40 cores, respectively. # (prog.exe < input1 >& data_out1 ) & (prog.exe < input2 >& data_out2 ) & (prog.exe < input3 >& data_out3 ) wait ##
The above manner of squeezing into a node as many execution instances as possible is a good way to gain efficiencies all the way around and should be adopted as common practice, provided:
- The duration of each execution is about the same;
- Each execution either requires about the same amount of memory, or the cumulative amount of memory does not exceed core_count * memory_per_process.
You can alternatively, but also more compactly, specify multiple #BSUB options per line, if you want:
#BSUB -J myjob1 -W 12:30 -n 3 -L /bin/bash -o stdout1.%J -P project1
Memory Specifications are IMPORTANT
#BSUB -R "rusage[mem=process_alloc_size]" -M process_size_limit
Both of these should be set in a job and, typically, to the same amount.
- The process_alloc_size specifies the amount of memory to allocate/reserve per process on a node. Omitting this specification,
will cause LSF to select nodes on the basis of available cores only, regardless, that is, of whether such nodes have sufficient memory to
run the job efficiently. Hence, this omission can cause the job to be swapped out onto the local drive (big delay) and/or memory contention
from other jobs running on the same node, thereby bringing a general and dramatic slowdown. If, in addition to this option, one specifies
a value (=core_count_per_node) for the ptile parameter, LSF will allocate/reserve core_count_per_node* process_alloc_size MB of memory per node.
- The -M process_size_limit setting specifies the memory size limit (in MBs) per process, which when exceeded will cause the process and
the job to fail. The default value for process_size_limit is 2.5 GB. Both of these settings should reflect the run-time needs of your job.
- The total available memory per node for jobs is about 10 GB less than the maximum: 54 GB for nxt type nodes; 246 GB for the mem256gb type; etc.
One should not rely on default memory limit settings. The latter may be too large or too small. A realistic picture of job's memory can be obtained
from the information given by one (e.g., bjobs) or more job tracking commands. (See Job tracking and control commands subsection).