Hi,
If the other files are still "processing" while you hit the rush job, they still need to finish their actual step before leaving place to another one.
Rush job, just allow a max priority to a job.
Quotation from Switch documentation :
The Switch job scheduler has the following (sometimes conflicting) objectives, in order of importance:
● Maximize overall throughput, that is, process as many jobs as possible in a given amount of time.
● Allow users to specify individual job priorities: a task for a job with a higher priority should be executed first. This can be used to "rush" a particular job through a flow, or to define a high priority flow (by assigning a priority to all jobs in the flow).
● Process jobs in order of arrival, that is, jobs should arrive at the end of a flow in the order they were placed in the flow to begin with (FIFO = first-in/first-out).
These objectives are not absolute: enforcing some particular order of execution to the letter would sacrifice throughput and/or overly complicate the implementation.
In other words, As soon as a core is available, Switch starts processing a pending job:
● If multiple jobs are available, it will process the one with the highest priority.
● If multiple jobs are available with the same priority, it _should_ give priority to the jobs in "FIFO" (first in, first out) mode
Alternatively, you could use the app "Priority helper", similar to rush job functionality, but with more granularity.
https://www.enfocus.com/en/appstore/pro ... ity-helper