Platform LSF Administration Guide Version 6.2
Chapter 19
Reserving Resources
Administering Platform LSF
351
3
Job4 finishes, freeing 4 more CPUs for future allocation, 2 on host A, and 2 on
host
C:
4
Job1 finishes, freeing 2 more CPUs for future allocation, 1 on host C, and 1 host D:
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 accurate estimated start time, running jobs must specify a run limit at
submission time through either
bsub -W or RUNLIMIT in queue configuration.
If run limit is not defined, 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.
Job3 Job3
Job3 Job3
Job3
Job3 Job1 Job1
J
Current available
ABCD
Current Inuse
Future available
Job3 Job3
Job3 Job3
Job3
Job3
J
Current available
ABCD
Current Inuse
Future available
Job3 Job3
Job3 Job3
Job5 Job3 Job5 Job5
Job5 Job3 Job5 Job5
A BCD
J
Future allocation