| 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: |
| | 3 | This document is for projects with [MultiUser multiple job submitters] |
| | 4 | who use quotas to allocate resources among submitters. |
| 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'''. |