CPU time limit
Sets the soft CPU time limit to cpu_limit for this batch job. The default is no limit.
| Job syntax (bsub) | Queue syntax (lsb.queues) | Format/Default Units |
|---|---|---|
| -c cpu_limit | CPULIMIT=[default] maximum | [hours:]minutes[/host_name | /host_model] |
This option is useful for avoiding runaway jobs that use up too many resources. LSF keeps track of the CPU time used by all processes of the job.
When the job accumulates the specified amount of CPU time, a SIGXCPU signal is sent to all processes belonging to the job. If the job has no signal handler for SIGXCPU, the job is killed immediately. If the SIGXCPU signal is handled, blocked, or ignored by the application, then after the grace period expires, LSF sends SIGINT, SIGTERM, and SIGKILL signals to the job to kill it.
You can define whether the CPU limit is a per-process limit enforced by the OS or a per-job limit enforced by LSF with the LSB_JOB_CPULIMIT parameter in the lsf.conf file.
Jobs submitted to a chunk job queue are not chunked if the CPU limit is greater than 30 minutes.
cpu_limit is in the form [hour:]minute, where minute can be greater than 59. 3.5 hours can either be specified as 3:30 or 210.