Platform LSF Administration Guide Version 6.2

What’s New in Platform LSF Version 6.0
Administering Platform LSF
34
Queue-based
fairshare
Prevents starvation of low-priority work and ensures high-priority jobs get the resources
they require by sharing resources among queues. Queue-based fairshare extends your
existing user- and project-based fairshare policies by enabling flexible slot allocation per
queue based on slot share units you configure.
See Chapter 16, “Fairshare Scheduling” for more information.
User fairshare by
queue priority
Improves control of user-based fairshare by taking queue priority into account for
dispatching jobs from different queues against the same user fairshare policy. Within the
queue, dispatch order is based on share quota.
See Chapter 16, “Fairshare Scheduling” for more information.
Job group support
Use LSF job groups to organize and control a collection of individual jobs in higher level
work units for easy management. A job group is a container for jobs in much the same
way that a directory in a file system is a container for files. For example, you can organize
jobs around groups that are meaningful to your business: a payroll application may have
one group of jobs that calculates weekly payments, another job group for calculating
monthly salaries, and a third job group that handles the salaries of part-time or contract
employees.
Jobs groups increase end-user productivity by reducing complexity:
◆ Submit, view, and control jobs according to their groups rather than looking at
individual jobs
◆ Create job group hierarchies
◆ Move jobs in and out of job groups as needed
◆ Kill, stop resume and send job control actions to entire job groups
◆ View job status by group
See Chapter 6, “Managing Jobs” for more information.
High Performance Computing
Dynamic ptile
enforcement
Parallel jobs now have a flexible choice of the number of CPUs in the different kinds of
hosts in a heterogeneous cluster.
Improves the performance and throughput of parallel jobs by setting multiple
ptile
values in a
span string according to the CPU configuration of the host type or model.
You can specify various
ptile values in the queue (RES_REQ in lsb.queues, or at
job submission with
bsub -R):
◆ Default ptile value, specified by n processors. For example:
span[ptile=4]
LSF allocates 4 processors on each available host, regardless of how many
processors the host has.
◆ Predefined ptile value, specified by ’!’. For example:
span[ptile='!']
LSF uses the predefined maximum job slot limit in lsb.hosts (MXJ per host
type/model) as its value.