Better worker pool management
We have been discussing internally defining multiple worker pools, and split them across groups of stacks. This has been rejected because it would not be efficient. Some worker pools could become idle for too long, resulting in a waste of money and resources.
Meaning, it would be great if workers from multiple worker pools, if idle, could become available to be picked up by tasks coming from another worker pools without available workers.
- Workaround
- No
Log in to comment and vote
Comments2
Black Breeze
Jun 6, 2025
Based on inactivity, I assume that the proposed solution was satisfactory.
Black Breeze
May 15, 2025
Have you looked into autoscaling workers? Especially in Kubernetes, we have a very good story around it. More than happy to put you in touch with our Solutions Engineers who can help you with that.