LSF配置job的最大内存限制

Enforce job level memory limits in LSF

LSF enforcement of job memory limits with job termination: 
This gives LSF control over how much memory jobs can use. LSF terminates any job that reaches the configured memory limit. LSF looks at the sum of the memory all job processes consume to determine if a job has reached the memory limit.

1. Add memory limit parameters to lsf.conf:
   
   

2. LSB_MEMLIMIT_ENFORCE=Y
   LSB_JOB_MEMLIMIT=Y

3. Specify a memory limit in lsb.queues or lsb.applications:
   
   

4. MEMLIMIT = 5000 #Memory limit of 5000 KB

5. Reconfigure LSF:
   
   

6. lsadmin reconfig
   badmin reconfig
   badmin hrestart all

You can specify memory limit at the queue level (lsb.queues), application profile level (lsb.application) or at job submission. Use the –M option when submitting jobs to specify a memory limit. For example,

bsub –M 50000 myjob.sh

LSF will allow this job to consume a maximum of 5000 KB of memory before terminating it.

The difference between LSB_JOB_MEMLIMIT set to y and LSB_MEMLIMIT_ENFORCE set to y is that with LSB_JOB_MEMLIMIT, only the per-job memory limit enforced by LSF is enabled. The per-process memory limit enforced by the OS is disabled. With LSB_MEMLIMIT_ENFORCE set to y, both the per-job memory limit enforced by LSF and the per-process memory limit enforced by the OS are enabled.

LSB_JOB_MEMLIMIT disables per-process memory limit enforced by the OS and enables per-job memory limit enforced by LSF. When the total memory allocated to all processes in the job exceeds the memory limit, LSF sends the following signals to kill the job: SIGINT first, then SIGTERM, then SIGKILL.

On UNIX, the time interval between SIGINT, SIGKILL, SIGTERM can be configured with the parameter JOB_TERMINATE_INTERVAL in lsb.params.