Skip to content
Snippets Groups Projects

Spell check

Merged David Hrbáč requested to merge spell_check into master
7 files
+ 30
22
Compare changes
  • Side-by-side
  • Inline
Files
7
@@ -9,24 +9,24 @@ Scheduler gives each job an execution priority and then uses this job execution
Job execution priority on Anselm is determined by these job properties (in order of importance):
1. queue priority
2. fairshare priority
2. fair-share priority
3. eligible time
### Queue priority
Queue priority is priority of queue where job is queued before execution.
Queue priority has the biggest impact on job execution priority. Execution priority of jobs in higher priority queues is always greater than execution priority of jobs in lower priority queues. Other properties of job used for determining job execution priority (fairshare priority, eligible time) cannot compete with queue priority.
Queue priority has the biggest impact on job execution priority. Execution priority of jobs in higher priority queues is always greater than execution priority of jobs in lower priority queues. Other properties of job used for determining job execution priority (fair-share priority, eligible time) cannot compete with queue priority.
Queue priorities can be seen at <https://extranet.it4i.cz/anselm/queues>
### Fairshare priority
### Fair-share priority
Fairshare priority is priority calculated on recent usage of resources. Fairshare priority is calculated per project, all members of project share same fairshare priority. Projects with higher recent usage have lower fairshare priority than projects with lower or none recent usage.
Fair-share priority is priority calculated on recent usage of resources. Fair-share priority is calculated per project, all members of project share same fair-share priority. Projects with higher recent usage have lower fair-share priority than projects with lower or none recent usage.
Fairshare priority is used for ranking jobs with equal queue priority.
Fair-share priority is used for ranking jobs with equal queue priority.
Fairshare priority is calculated as
Fair-share priority is calculated as
![](../../img/fairshare_formula.png)
@@ -34,15 +34,15 @@ where MAX_FAIRSHARE has value 1E6, usage~Project~ is cumulated usage by all memb
Usage counts allocated core hours (ncpus*walltime). Usage is decayed, or cut in half periodically, at the interval 168 hours (one week). Jobs queued in queue qexp are not calculated to project's usage.
>Calculated usage and fairshare priority can be seen at <https://extranet.it4i.cz/anselm/projects>.
>Calculated usage and fair-share priority can be seen at <https://extranet.it4i.cz/anselm/projects>.
Calculated fairshare priority can be also seen as Resource_List.fairshare attribute of a job.
Calculated fair-share priority can be also seen as Resource_List.fairshare attribute of a job.
###Eligible time
Eligible time is amount (in seconds) of eligible time job accrued while waiting to run. Jobs with higher eligible time gains higher priority.
Eligible time has the least impact on execution priority. Eligible time is used for sorting jobs with equal queue priority and fairshare priority. It is very, very difficult for eligible time to compete with fairshare priority.
Eligible time has the least impact on execution priority. Eligible time is used for sorting jobs with equal queue priority and fair-share priority. It is very, very difficult for eligible time to compete with fair-share priority.
Eligible time can be seen as eligible_time attribute of job.
Loading