Platform LSF Administration Guide Version 6.2
Chapter 16
Fairshare Scheduling
Administering Platform LSF
297
Typical Slot Allocation Scenarios
3 queues with SLOT_SHARE 50%, 30%, 20%, with 15 job slots
This scenario has three phases:
1
All three queues have jobs running, and LSF assigns the number of slots to queues
as expected: 8, 5, 2. Though queue
Genova deserves 3 slots, the total slot
assignment must be 15, so
Genova is allocated only 2 slots:
% bqueues
QUEUE_NAME PRIO STATUS MAX JL/U JL/P JL/H NJOBS PEND RUN SUSP
Roma 50 Open:Active - - - - 1000 992 8 0
Verona 48 Open:Active - - - - 995 990 5 0
Genova 48 Open:Active - - - - 996 994 2 0
2
When queue Verona has done its work, queues Roma and Genova get their
respective shares of 8 and 3.
This leaves 4 slots to be redistributed to queues according to their shares: 40% (2
slots) to
Roma, 20% (1 slot) to Genova. The one remaining slot is assigned to queue
Roma again:
% bqueues
QUEUE_NAME PRIO STATUS MAX JL/U JL/P JL/H NJOBS PEND RUN SUSP
Roma 50 Open:Active - - - - 231 221 10 0
Verona 48 Open:Active - - - - 0 0 0 0
Genova 48 Open:Active - - - - 496 491 5 0
1
When queues Roma and Verona have no more work to do, Genova can use all the
available slots in the cluster:
% bqueues
QUEUE_NAME PRIO STATUS MAX JL/U JL/P JL/H NJOBS PEND RUN SUSP
Roma 50 Open:Active - - - - 0 0 0 0
Verona 48 Open:Active - - - - 0 0 0 0
Genova 48 Open:Active - - - - 475 460 15 0