Page History

...

Hence we need a load management that can limit the number of submission. Then whenever the Job becomes active the limit token is released.

Here is the simplest illustration:

suite test_limit_on_submission
    limit disk 2
    family anon    
        inlimit -s disk   # Inlimit submission
        task t1
        task t2
        task t3
        task t4
        task t5
        task t6
        task t7
        task t8
        task t9
        task t10
        task t11
        task t12
    endfamily
endsuite

Hence we could have more than 2 active jobs, since we are only controlled number in the submitted state.

If we removed the -s then we can only have two active jobs running at one time