LSF Version 7.3 - Administering Platform LSF

Time-based Slot Reservation
414 Administering Platform LSF
5 Job5 can now be placed with 2 CPUs on host A, 2 CPUs on host C, and 2 CPUs
on host D. The estimated start time is shown as the finish time of
Job1:
Assumptions and limitations
◆ To get an accurate estimated start time, you must specify a run limit at the job
level using the
bsub -W option, in the queue by configuring RUNLIMIT in
lsb.queues, or in the application by configuring RUNLIMIT in
lsb.applications, or you must specify a run time estimate by defining the
RUNTIME parameter in
lsb.applications. If a run limit or a run time
estimate is not defined, the scheduler will try to use CPU limit instead.
◆ Estimated start time is only relatively accurate according to current running job
information. If running jobs finish earlier, estimated start time may be moved
to earlier time. Only the highest priority job will get accurate predicted start
time. The estimated start time for other jobs could be changed after the first job
starts.
◆ Under time-based slot reservation, only information from currently running
jobs is used for making reservation decisions.
◆ Estimated start time calculation does not consider Deadline scheduling.
◆ Estimated start time calculation does not consider Advance Reservation.
◆ Estimated start time calculation does not consider DISPATCH_WINDOW in
lsb.hosts and lsb.queue configuration.
◆ If preemptive scheduling is used, the estimated start time may not be accurate.
The scheduler may calculate and estimated time, but actually it may preempt
other jobs to start earlier.
Slot limit enforcement
The following slot limits are enforced:
◆ Slot limits configured in lsb.resources (SLOTS, PER_SLOT)