Configure per-resource reservation

Procedure

To enable greater flexibility for reserving numeric resources are reserved by jobs, configure the ReservationUsage section in lsb.resources to reserve resources as PER_JOB, PER_TASK, or PER_HOST

Only user-defined numeric resources can be reserved. Builtin resources like mem, cpu, swp, etc. cannot be configured in the ReservationUsage section.

The cluster-wide RESOURCE_RESERVE_PER_SLOT parameter in lsb.params is obsolete. Configuration in lsb.resources overrides RESOURCE_RESERVE_PER_SLOT if it also exists for the same resource.

RESOURCE_RESERVE_PER_TASK parameter still controls resources that are not configured in lsb.resources. Resources not reserved in lsb.resources are reserved per job.

PER_HOST reservation means that for the parallel job, LSF reserves one instance of a for each host. For example, some applications are charged only once no matter how many applications are running provided those applications are running on the same host under the same user.

Note: Configuration PER_SLOT is obsolete as of LSF 9.1.3 and replaced by PER_TASK.

Assumptions and limitations

Per-resource configuration defines resource usage for individual resources, but it does not change any existing resource limit behavior (PER_JOB, PER_TASK).
In a MultiCluster environment, you should configure resource usage in the scheduling cluster (submission cluster in lease model or receiving cluster in job forward model).
The keyword pref in the compute unit resource string is ignored, and the default configuration order is used (pref=config).