Platform LSF Administration Guide Version 6.2

About Resource Allocation Limits
Administering Platform LSF
332
Limits for resource consumers
Host groups
If a limit is specified for a host group, the total amount of a resource used by all hosts
in that group is counted. If a host is a member of more than one group, each job running
on that host is counted against the limit for all groups to which the host belongs.
Limits for users
and user groups
Jobs are normally queued on a first-come, first-served (FCFS) basis. It is possible for
some users to abuse the system by submitting a large number of jobs; jobs from other
users must wait until these jobs complete. Limiting resources by user prevents users
from monopolizing all the resources.
Users can submit an unlimited number of jobs, but if they have reached their limit for
any resource, the rest of their jobs stay pending, until some of their running jobs finish
or resources become available.
If a limit is specified for a user group, the total amount of a resource used by all users in
that group is counted. If a user is a member of more than one group, each of that user’s
jobs is counted against the limit for all groups to which that user belongs.
Use the keyword
all to configure limits that apply to each user or user group in a
cluster. This is useful if you have a large cluster but only want to exclude a few users from
the limit definition.
Per-user limits on
users and groups
Per-user limits are enforced on each user or individually to each user in the user group
listed. If a user group contains a subgroup, the limit also applies to each member in the
subgroup recursively.
Per-user limits that use the keywords
all apply to each user in a cluster. If user groups
are configured, the limit applies to each member of the user group, not the group as a
whole.