Platform LSF Administration Guide Version 6.2

Chapter 30
Load Thresholds
Administering Platform LSF
475
Exceptions
In some special cases, LSF does not automatically suspend jobs because of load levels.
◆ LSF does not suspend a job forced to run with brun -f.
◆ LSF does not suspend the only job running on a host, unless the host is being used
interactively.
When only one job is running on a host, it is not suspended for any reason except
that the host is not interactively idle (the
it interactive idle time load index is less
than one minute). This means that once a job is started on a host, at least one job
continues to run unless there is an interactive user on the host. Once the job is
suspended, it is not resumed until all the scheduling conditions are met, so it should
not interfere with the interactive user.
◆ LSF does not suspend a job because of the paging rate, unless the host is being used
interactively.
When a host has interactive users, LSF suspends jobs with high paging rates, to
improve the response time on the host for interactive users. When a host is idle, the
pg (paging rate) load index is ignored. The PG_SUSP_IT parameter in
lsb.params controls this behaviour. If the host has been idle for more than
PG_SUSP_IT minutes, the
pg load index is not checked against the suspending
threshold.