Platform LSF Administration Guide Version 6.2

Chapter 16
Fairshare Scheduling
Administering Platform LSF
301
Initially, queues Livorno, Palermo, and Venezia in poolB are not assigned any slots
because the first 7 higher priority queues have used all 21 slots available for allocation.
As jobs run and each queue accumulates used slots, LSF favors queues that have not run
jobs yet. As jobs finish in the first 7 queues of
poolB, slots are redistributed to the other
queues that originally had no jobs (queues
Livorno, Palermo, and Venezia). The
total slot count remains 21 in all queues in
poolB.
% bqueues
QUEUE_NAME PRIO STATUS MAX JL/U JL/P JL/H NJOBS PEND RUN SUSP
Roma 50 Open:Active - - - - 15 6 9 0
V 48 Open:Active - - - - 25 18 7 0
Genova 47 Open:Active - - - - 460 455 5 0
Pisa 44 Open:Active - - - - 263 261 2 0
Milano 43 Open:Active - - - - 261 259 2 0
Parma 42 Open:Active - - - - 259 257 2 0
Bologna 40 Open:Active - - - - 259 257 2 0
Sora 40 Open:Active - - - - 260 258 2 0
Ferrara 40 Open:Active - - - - 257 255 2 0
Napoli 40 Open:Active - - - - 258 256 2 0
Livorno 40 Open:Active - - - - 258 256 2 0
Palermo 40 Open:Active - - - - 256 253 3 0
Venezia 4 Open:Active - - - - 255 253 2 0
The following figure illustrates the round-robin distribution of slot allocations between
queues
Livorno and Palermo:
How LSF rebalances slot usage
In the following examples, job runtime is not equal, but varies randomly over time.