Prioritization - using priorities to organize your jobs [Envoy 4.6.10+]

Prioritization - using priorities to organize your jobs [Envoy 4.6.10+]

You can use the priorities to organize the job queue - turns in which your submitted jobs will run. You can increase or decrease the priority number for each job that is awaiting its turn to be rendered ("Starting" status in Envoy). You can't shuffle jobs with other statuses like "Running".  See the lists of known limitations and overall rules below and the working example at the bottom of it.

KNOWN LIMITATIONS AND OVERALL RULES:
SORTING:
- the higher the number the higher the position in the queue
- jobs with the same priority will run according to their submission time
- all running and starting (queued) jobs will be sorted according to their priorities
- all finished or stopped jobs will be queued at the bottom according to their submission date

KILLING AND RESTARTING JOBS/FRAMES:
- when you are maxing out node limit with the high priority job and stop/kill some frames that won't release the pool for other jobs - that allows you to restart those frames within the current pool
- you can't put queued job before the one that is already running - the only way to do that is to kill the running job

CHANGING ENVOY'S GLOBAL SETTINGS:
- changing the Plan from Economy to Rush for example will grant you additional nodes but it might disrupt the way you have set your jobs with priority numbers so the queue may not exactly evaluate as expected 


EXAMPLE:
We have 3 jobs - 1 on the top of the queue is running on 5 nodes and since we are on Economy plan we only get 5 nodes at our disposal so other jobs are waiting for it to finish.

Use the UP/DOWN arrows you see on the far left to each job in order to adjust the priority of the queued jobs. Higher number means higher position in the render queue:


After adjusting the priority the view will refresh - it will do that each time the given priority value is adjusted. As the actively running job finishes the one with highest priority starts next and the finished ones are placed at the bottom according to their submission date:


Please remember only the queued jobs can be sorted so as soon as the job changes state from "Starting" to any other the priority disappears. Now the Priority 2 job is running:


As Priority 2 job finishes Priority 1 starts:



All jobs finished now and are positioned according to their submission dates:


    • Related Articles

    • Custom Envoy log path [Envoy 4.6.10+]

      You can use custom path for the Envoy log. Please edit the gm-config.cfg to set the new path. Config file locations based on your OS: WINDOWS: "C:\Users\%USERNAME%\AppData\Local\GridMarkets\Envoy\gm-config.cfg" LINUX: ...
    • Envoy installation under Linux [Linux]

      Envoy for Linux has been tested with Ubuntu, Fedora, Open Suse, Mint, Debian and several other distros, but given that distros can be highly customised we can NOT guarantee it will install or run. This article provides information on how to handle ...
    • Installing plug-ins with Envoy and manually [Envoy 4.0.X or newer]

      Installing plug-ins with Envoy GridMarkets Envoy contains logic for installing and updating the various GridMarkets plug-ins. To open the Envoy plug-ins view click GridMarkets in the top bar menu and then Plugins. Make sure you have closed the app ...
    • Downloading files manually [Envoy 4.0.x+]

      You can download files manually via Envoy from the Files tab (firstly please make sure you are aware of how long we keep your files in our file retention policy though). In order to access it please go to GRIDMARKETS [1] section, search for the ...
    • Pricing plans \ Machine configurations \ Render estimates calculator

      Pricing overview Calculator \ Machine configurations \ Priorities