Changes between Version 2 and Version 3 of MultiUserPriority


Ignore:
Timestamp:
10/01/18 23:58:47 (10 months ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MultiUserPriority

    v2 v3  
    1 = Prioritizing jobs in a multi-user project =
     1= Allocation-based job prioritization =
    22
    3 By default, BOINC processes jobs in a roughly first-in, first-out order.
    4 If your project has multiple job submitters,
    5 this is probably not what you want:
    6 users who submits lots of jobs would get more than their share of the project's capacity.
    7 BOINC has a set of mechanisms that address this issue.
    8 To use them, do the following:
     3This document is for projects with [MultiUser multiple job submitters]
     4who use quotas to allocate resources among submitters.
    95
    10 == Set the desired quotas for job submitters ==
     6If you use [RemoteJobs remote job submission], read no further;
     7those mechanisms automatically prioritize jobs based on quotas.
    118
    12 Create a user account for each job submitter,
    13 and [MultiUser set their quotas].
     9Otherwise, you'll need to modify your job submission scripts or work generators
     10to set job priorities.
    1411
    15 == Modify your job submission scripts or work generators ==
    16 
    17 Wherever you create jobs - e.g. [RemoteJobs web scripts for remote job submission]
    18 and [WorkGeneration work generators] - you must set the priority of the jobs
     12When you create jobs, set the priority of the jobs
    1913as follows:
    2014
     
    3630}}}
    3731
    38  * Set job priorities.  For example, use the '''--priority''' option to '''create_work'''.
    39    Also, if you're creating a batch, set batch.logical_end_time to the priority
    40    (this is not used for scheduling, but is used in displaying batches on the web).
    41 
    42 == Prioritize existing jobs ==
    43 
    44 If you have a lot of jobs already queued,
    45 you can prioritize them (and initialize user priorities) by running
    46 
    47 {{{
    48 html/ops/submit_init_priority.php
    49 }}}
    50 
    51 This script can also be used to reset all priorities to zero.
    52 
    53 == Use the right feeder options ==
    54 
    55 Run the feeder with the '''--priority_asc''' option.
    56 
    57 Notes:
    58  * Currently this can't be used in combination with the --all_apps option,
    59   or with homogeneous redundancy.
    60  * If there are any problems, remove the '''--priority_asc''' option
    61   and you'll be using FIFO again.
     32 * Set job priorities to this value.  For example, use the '''--priority''' option to '''create_work'''.