There have been multiple issues (#2577, #2928 etc) opened regarding Concourse's build/container scheduling and the container placement strategies currently present (random, volume-locality and fewest-build-containers) are not able to equitably distribute the workload because

1. they are not aware of the actual load present on the workers (number of volumes and/or build containers are loose approximations)
2. there is no queueing logic, meaning that even if all the workers are busy, any new work will still be scheduled immediately, which can cause workers to fall over.

This is a meta-issue to discuss all the use cases and possible implementations for better work scheduling in Concourse.