Aug 26, 2017 · 1 min read
It’s closer to the latter. Previously, Galaxy’s scheduler couldn’t tell if a deploy was finished, so deploy time was something that couldn’t actually be measured.
However, if we’re talking about the time it takes to have running containers for a newly deployed version, that time should be the same.
What will take longer is for Galaxy to set this newly deployed version to be your app’s current active version since now Galaxy will only do so after starting containers and checking their health (assuming your containers pass the health check).
