3 ms·
I can totally see this starting to matter, but I do want to point out that it hasn't ground your business to a halt just yet and is very very unlikely to. From
by hardwaresofton 6y ago
I can totally see this starting to matter, but I do want to point out that it hasn't ground your business to a halt just yet and is very very unlikely to. From what I've seen most ops pain comes from a lack of automation when deploying -- as in if the process is 5-10 or even 15 minutes, no one really cares (outside of an emergency) if it's completely automated. Do you find that is true with your work as well?
I can certainly see that it can be a painful problem (10-40GiB is huge), but I expect most smaller shops that aren't running on their own servers/colo as such these image sizes were never even an option (I can't imagine trying to upload 40GB across the public internet to launch one instance!).
- ethbr0 6y agoI've worked in the general automation space for awhile, and agree that time-to-result is rarely the limiting factor. It's also not usually total-person-clock-time. It's number-of-distinct-manual-steps. (5 minutes manual) + (15 minutes automation) + (5 minutes manual) + (30 minutes automation) = everyone hates doing it (10 minutes manual) + (45 minutes automation) = everyone's happy and can use their time productively
- js8 6y agoBecause every manual step means things can go wrong. You might also need to look it up if you don't do it often. All these increase the overhead of manual steps compared to clock time.
- ethbr0 6y agoPartly. I think it's also because manual steps require synchronization. Not only do I have to do something, I also have to set an alarm / watch the clock to know when to do something.