atc

> However it performs like a dud. No scheduling to speak of, just runs everything as soon as it can. We've run into nodes dying under load (-not- underprovisioned, could run all these jobs manually at once on these monsters). We've run into problems with volume reaping, fork bombs, ui freezes, everything under the sun. I've used concourse as a consumer for 3 years and I've very, very rarely seen any of the problems you're describing, even on the older versions and certainly not in the last year or so. > no scheduling to speak of Concourse has a massive scheduling system built into it.. https://github.com/concourse/atc Furthermore, you can configure jobs to run in serial (default is parallel). > ui freezes Put your `web` binary on a decently-sized VM and your problem should disappear. Also, don't have your workers on the same VM as your `w