How to avoid crazy long "Spin up Environment" times?

I have a relatively complex workflow, but random jobs within it take 2-9 minutes to spin up with no visibilty into what’s taking so long. These were from the same commit, taking a workflow that should have taken 2 minutes, to one that is going to take at least 14 when it finishes.

(the infuriating thing is that this job with 5x parallelism is done, in the time this fifth one spun up the other 4 did all of the work and finished in under 20 seconds, leaving this vestigial container to sit there, “spinning”, blocking the rest of the workflow)

Is there anything I can do to fix this?

I would submit that as a support ticket. My workflows are admittedly simple, but I can’t imagine why a complex workflow would take a long time to get an environment - maybe it is waiting for a set of resources so it can get the right number of containers?

I’ve just checked a few recent spin-up times for my current work, and I am seeing 3s, 5s, 10s, etc.

1 Like