Re: [Condor-users] Jobs License Management

["Jason Stowe" <jstowe@xxxxxxxxxxxxxxxxxx>]

Stuart,
This limiting is happening at matchmaking time, and lasts the life of
a job. This is why there is no preemption based upon decreasing limits
below currency usage.

One thing that would be an important part to this feature would be to
allow Condor to account for Limits using more than just multiples of
1.
For I/0 connection or IO related limits, it would be useful and
probably trivial to add the ability to specify some format like:
concurrency_limits = <LIMIT_NAME>:<LIMIT_USED>, ....
The ":<LIMIT_USED>" would be optional and default to 1. But, if you
wanted to specify fractional numbers for jobs using limits you can.
E.g. rather than:
concurrency_limits = APPNAME, APPNAME, PLUGIN_B
you would have
concurrency_limits = APPNAME:2, PLUGIN_B

This would enable more load-based limits like:
concurrency_limits = LOAD_LIMIT:1.25, APPNAME
and on other jobs:
concurrency_limits = LOAD_LIMIT:0.5

This kind of fractional specification would help increase the number
of applicable use cases for this feature.

Thanks,
Jason


On Tue, Oct 14, 2008 at 11:22 PM, Stuart Anderson
<anderson@xxxxxxxxxxxxxxxx> wrote:
> In the context of the new Concurrency Limit will it be possible for a
> running job to drop a resource constraint when it is done with it, or
> is it implicitly assumed that all jobs require their specified
> resources for their entire lifetime?
>
> The motivation for this is managing I/O resources where a typical work
> flow is to launch a large number of jobs that each read in a large
> amount data from a shared filesystem (or set of filesystems), and then
> crunch on the data for a long time before outputing a relatively small
> amount of results. It would be interesting to be able to hand out
> tokens for filer access but then be able to return them after the I/O
> intensive phase of each individual job is done.
>
> Thanks.
>
> --
> Stuart Anderson  anderson@xxxxxxxxxxxxxxxx
> http://www.ligo.caltech.edu/~anderson
>
>
>
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/
>



-- 
===================================
Jason A. Stowe
cell: 607.227.9686
main: 888.292.5320

Cycle Computing, LLC
Leader in Condor Grid Solutions
Enterprise Condor Support and Management Tools

http://www.cyclecomputing.com
http://www.cyclecloud.com