Mailing List Archives

Public Access

 		[Computer Systems Lab]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] affecting user priority

FYI, for quotas to work the units on your SlotWeight must match the units on your quota. Also, for it to make sense, all your SLotWeights should be of the same unit. A unit is core or MB memory, maybe core*1000+memory <- complex.
If the use case you're after is chargeback, you should do post-processing on either job ads or slot ads -- you can get records dropped by the startd and the schedd. 

Best,


matt

On 04/30/2013 02:19 PM, Rita wrote:

I didn't realize this attribute, its great.

With Slotweight in mind, is it possible to create a new attribute for a
job called it "resourceUsage" which will account for "Cpus+Memory" ?
Since this will a virtual attribute when the job is running I would like
to collect this information and "charge" the user :p




On Tue, Apr 30, 2013 at 2:47 PM, Todd Tannenbaum <tannenba@xxxxxxxxxxx
<mailto:tannenba@xxxxxxxxxxx>> wrote:

    On 4/30/2013 1:20 PM, Rita wrote:

        is it possible to choose what will affect a user's priority?
        currently,
        it seems the only metric is CPU usage. My thought is, if I can
        assign a
        user priority by memory requirements  and then CPU usage.


    By default, the fair-share user priority mechanism in HTCondor is
    based upon how many slots are used by a given user over time.  The
    "cost" for each slot is, by default, based upon the number of CPUs
    in that slot. However, you can customize it to whatever you want via
    the "SlotWeight" knob in your condor_config files. So the default is
       SlotWeight = Cpus
    If you want it based upon some mixture of memory plus CPUs, perhaps
       SlotWeight = cpus * 1000 + Memory
    SlotWeight is read by the condor_startd (e.g. by the execute node),
    so each execute node could have a different SlotWeight.
    I copied a snippet from the HTCondor Manual below.

    Hope this helps
    Todd

    SlotWeight
         This may be used to give a slot greater weight when calculating
    usage, computing fair shares, and enforcing group quotas. For
    example, claiming a slot with SlotWeight = 2 is equivalent to
    claiming two SlotWeight = 1 slots. The default value is Cpus, the
    number of CPUs associated with the slot, which is 1 unless specially
    configured. Any expression referring to attributes of the slot
    ClassAd and evaluating to a positive floating point number is valid.



        --
        --- Get your facts first, then you can distort them as you please.--


        _________________________________________________
        HTCondor-users mailing list
        To unsubscribe, send a message to
        htcondor-users-request@xxxxxxxxxxxxx
        <mailto:htcondor-users-request@xxxxxxxxxxx> with a
        subject: Unsubscribe
        You can also unsubscribe by visiting
        https://lists.cs.wisc.edu/__mailman/listinfo/htcondor-__users
        <https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users>

        The archives can be found at:
        https://lists.cs.wisc.edu/__archive/htcondor-users/
        <https://lists.cs.wisc.edu/archive/htcondor-users/>



    --
    Todd Tannenbaum <tannenba@xxxxxxxxxxx <mailto:tannenba@xxxxxxxxxxx>>
    University of Wisconsin-Madison
    Center for High Throughput Computing   Department of Computer Sciences
    HTCondor Technical Lead                1210 W. Dayton St. Rm #4257
    Phone: (608) 263-7132 <tel:%28608%29%20263-7132>
      Madison, WI 53706-1685




--
--- Get your facts first, then you can distort them as you please.--


_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/