With depot disabled, mix deps.compile took about 5:34 in our most recent run, and the whole deploy step took 9:12:
So, what you said about the time to run the deps.compile step is not accurate for our builds with depot disabled:
generally it’s taken 20-30 min to process that step
Here’s a run from when depot was enabled. mix.compile took 20:47 and the whole thing took 34:43:
This deployment did succeed since it completed in < 60 minutes. So, what I said earlier about it always failing was inaccurate - but even in this case where it worked a 4X slowdown and 4X increase in GitHub Actions minutes used, and a 4X greater time before we can deploy fixes to production is still not great.
The mix deps.compile step is the single longest step but even factoring that out, the other steps took 14 minutes on the depot run (34:43 - 20:47) vs. about 3:40 on our runs without depot (9:12 - 5:34) so I don’t think that profiling or optimizing our compile is going to be helpful. The whole thing is just much, much slower with depot. To be clear: we don’t have a goal of getting onto depot, so to be honest I don’t want to spend more time on this. I’d prefer to keep things the way they are, I’m just concerned since you’ve stated that you’re going to force everyone onto depot.