On  Tue, 13 Feb 1996 14:48:17 +0500 Mohan Das wrote:
 
<snip>
 
>Another issue which generated some discussion was that of Global limit
>vs. Local limit. That is, whether there should be a global limit on
t>he number of non-HIPRI jobs executing on the system, or should we
>only have limits for each queue and the total limit on the system will
>be the sum of these individual limits.
 
>Following are the advantages and disadvantages of the two approaches.
 
>   a. :LIMIT will change the global limit. :limit ;jobq=<qname> will change
>      Q limits.
 
>      +ve: Compatible with how :LIMIT works today.
>          :LIMIT 0 will shut off all new jobs.
 
>      -ve: Two limits to keep track of, for the users.
>          Not obvious as to which job will be selected to run once a
>          slot is open.
 
>   b. Don't have any global limit. Each Q to have its own limit.
 
>      +ve: Easier to understand for the user.
>          No guessing as to which job will be picked to run when a
>           job finishes.
 
>      -ve: :LIMIT 0 won't work as it does today, if you have more than
>          one Q. It will still work the same way if you don't make
>          use of multiple queues.
 
>We weighed the pros and cons of both the approaches and decided to go
>with the second approach.
 
I have a major concern with the loss of the global limit. My vote goes for a)
because its positive side outways the positive side of b) and the negative side
of b) outways the positive side of a). Overall, a) wins on both counts.
 
<snip>
 
>Changes to Existing Commands:
>----------------------------
 
>LIMIT, JOB, ALTJOB and STREAM commands will have a new parameter JOBQ.
 
>LIMIT command will also be enhanced to accept '+' or '-' before the numeric
>values to indicate increment and decrement.
 
>Ex: :limit +1,-1
 
>means, increase the job limit on the system job queue by 1 and decrease the
>session limit by 1.
 
Are you providing session queues as well when you refer to limit +1,-1?
 
<snip>
 
Ken Nutsford
<[log in to unmask]>