Problem

When utilizing a limited set of cloud resources by a team, it's important to sort the queue of runs based on priority. Currently, runs are executed in the order in which they are submitted. This is why

1. It's important to be able to set priority.
2. Also, potentially, be able to change it (to prioritize existing runs).

Solution

Introduce the priority property of a run configuration (e.g. an integer 0..100). When the dstack server processes the job queue, it should respect the value of this property if the runs compete for the same resources.

Workaround

No response

Would you like to help us implement this feature by sending a PR?

Yes