If the slot has 4096 MB of memory, than the above policy implies that an expected 4 jobs that can be serviced (note that each job consumes at least one chunk of 1024MB).
-Note that job may actually acquire more than one 'chunk' of a resource. Example: if a job ends up taking 2 of the memory quanta defined above (for 2048 mem), it will reduce the partitionable slot's weight from 4 to 2. It is effectively occupying 2 "expected jobs." and it is charged a value of 2, which is deducted against its submitter share, group quota, added to submitter usage, etc.
-
An advantage of this convention is that it allows the negotiator's matchmaking to add up the pool's slot weights to obtain a measurement of how many jobs can be serviced by all of the resources. This is especially helpful for working with Accounting Group Quotas, since it makes the one-dimensional group quota computations work smoothly with slots having different consumption policies and different slot weights, and allows compatible comparisons with running and idle jobs.
{subsubsection: match cost}
