LSF Version 7.3 - Administering Platform LSF

Typical Slot Allocation Scenarios
318 Administering Platform LSF
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.
3 queues in one
pool with 50%,
30%, 20% shares
A pool configures 3 queues:
◆ queue1 50% with short-running jobs
◆ queue2 20% with short-running jobs
◆ queue3 30% with longer running jobs
As
queue1 and queue2 finish their jobs, the number of jobs in queue3 expands, and
as
queue1 and queue2 get more work, LSF rebalances the usage: