Add ability to prioritize GitHub Action runners
**Describe the enhancement** Self-hosted GitHub actions should have an attribute (`weight`) that allows to prioritize them, i.e. If there are multiple idle runners with matching labels, then the `weight` attribute would determine which runner to use first, e.g. prioritized in ascending order. **Additional information** For context, the reason this is needed is because the current implementation randomly picks an available runner. However, imagine that you are scaling up and down runners depending on how long they have been idle. Using random allocation mechanism, there is no way to determine (efficiently) how long the runner was not in use. As a result, we have a large portion of VMs runnings that are not in use most of the time. Prioritization would allow more efficient resource packing.
Posted by gajus on Feb 7, 2022, 4:33 PM
Tags
Related issues
- Huh, this is not my experience.
- For some reason an Azure outage does not faze me in the same way that an AWS outage does.
- The triplet of wind, pole, dragon appears multiple times in the same order, so is possibly a single phrase that has been broken up into t...
- Option to skip refreshing resource instances whose configuration hasn't changed since the last apply
- [YouTube] Unable to extract uploader id
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
reliability (E-commerce)
Huh, this is not my experience.
For some reason an Azure outage does not faze me in the same way that an AWS outage does.
The triplet of wind, pole, dragon appears multiple times in the same order, so is possibly a single phrase that has been broken up into t...
Option to skip refreshing resource instances whose configuration hasn't changed since the last apply
[YouTube] Unable to extract uploader id
Add ability to prioritize GitHub Action runners
Add ability to prioritize GitHub Action runners
**Describe the enhancement** Self-hosted GitHub actions should have an attribute (`weight`) that allows to prioritize them, i.e. If there are multiple idle runners with matching labels, then the `weight` attribute would determine which runner to use first, e.g. prioritized in ascending order. **Additional information** For context, the reason this is needed is because the current implementation randomly picks an available runner. However, imagine that you are scaling up and down runners depending on how long they have been idle. Using random allocation mechanism, there is no way to determine (efficiently) how long the runner was not in use. As a result, we have a large portion of VMs runnings that are not in use most of the time. Prioritization would allow more efficient resource packing.
Comments (0)
No comments yet. Start the discussion.