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
Problem
-

Please authenticate to join the conversation.

Upvoters
Status

❌ Rejected

Board

πŸ’‘ Feature Requests

Tags

Stacks

Date

9 months ago

Subscribe to post

Get notified by email when there are changes.