The scheduling priority affects the order in which the jobs are scheduled. The range is 1 to 15.

Two types of priorities are supported:
  • Scheduling priority: Determine the order in which jobs are scheduled. The range is 1(low) to 15(top).
  • Execution priority: Influence the execution of the job on the remote machine. The range is 1(low) to 15(top).
There are conditions in which lower priorities supersede higher priorities, such as:
  • FairShare weightings are not currently supported in Accelerator Plus. For the jobs of a given user, higher priority jobs are scheduled before lower priority ones.
  • A low priority job will be dispatched before a high priority job if the resources for the low priority job are available while the resources for the high priority job are not.
In Accelerator Plus, set the priority of a job at submission time with the option -p.
% wx run -p high sleep 10
% wx run -p 12  sleep 10
% wx run -p 12.low sleep 10
The priority can be set from the GUI using the Retrace Priority Flags dialog from the console. With the command vsr, you can use the option -priority (which can be abbreviated to -p) as shown in the example below:
% vsr -p high target           # Use high scheduling priority.
% vsr -p h target              # Abbreviated form.
% vsr -p high.high target      # Set both scheduling and execution priority

Priorities Relative to Previous Run

When specifying a priority, it is possible to use also the following symbolic values:
Symbolic Name
Same priority as before. If not defined, then use low priority.
Increase previous priority by 1, without exceeding the maximum priority for the user.
Decrease previous priority by 1, but no less than low priority.
Example: rerun the job 123456 with increased priority:
% wx rerun -p incr 000123456