...
This will submit a job to LSF. The "pwd" command will print out the job's working directory, which should be the same directory where this job is submitted. The #BSUB -W180 directive tells LSF that the job's maximum run time limit (wall clock time) is 180 minutes. After that the job will be killed. If #BSUB -Wnnn isn't specified, your job get the default, which is 30 minutes. You can but don't have to specify a batch queue. If no queue is given at the submission time, LSF will chose one for your job according to job's run time limit.
- Check job status.
$ bjobs
$ bjobs -l <job ID>
- Kill a job.
$ bkill <job ID>
SLAC batch resources consist of several generation of hardwares. They are listed at the the shakeholder's priority page. These batch nodes all have CVMFS, outbound network connectivity, and have access to SLAC networked storages. They also have large /scratch space for temporary use (please clean up your files from there after your job finishes)
Some of the batch nodes run RHEL 6 operation system, while others run CentOS 7 operation system. Singularity container technology is available on the CentOS 7 batch nodes.
- To run your job on a RHEL 6 batch node only, use bsub -R "select[rhel6]" ...
- To run your job on a CentOS 7 batch node only, use bsub -R "select[centos7]" ...
By default, your job will ask for 1 CPU core (one batch slot) and will allow maximum of 4GB of RAM. If you exceed the RAM limit, your job will be killed. If you need more CPU core or RAM, you can ask for more than one CPU cores when submitting your jobs. For example:
- bsub -n 4 -R 'span[hosts=1]' ... will submit jobs requesting 4 core and (4x 4GB = 16GB RAM), and allocate all 4 cores on one machine (This is what "span[hosts=1" is for)
Of course, the more resource you ask, the harder to schedule the jobs, and hence the pending time will be longer.
Please refer to the LSF document to get familiar with the basic usage of LSF.
...