Faster Docker builds using a remote BuildKit instance

Re:Faster Docker builds using a remote BuildKit instance by aayushshah15 on Monday August 12, 2024 @10:25PM (#41231577)

Well, the point was that if 4 concurrent `git push`es saturates up to 1500 vCPUs then you'd need 16 of those hetzner dedicated servers (which you have to manage the uptime for) that you're paying for for the entire month. ~4 pushes is a very small amount and an org with a few dozen or so engineers will regularly see peaks higher than this.

Additionally, you'd have to ensure some isolation across your test runs (either by running the test suites in ephemeral containers, or VMs) which is additional engineering work for something that isn't business critical.

[ Parent | on HN ]

Re:Faster Docker builds using a remote BuildKit instance by adamcharnock on Tuesday August 13, 2024 @01:23AM (#41232523)

In my experience, dedicated hardware has provided a baseline real-world 2x speed up over cloud instances (presumably down to no contention, local nvme). So that would be 8 hetzner instances.

I managed to squeeze out a 5x speed up total (see my other comment). In which case that would mean 3-4 instances.

Plus with shorter build times you may then find that having a builds queued up is acceptable.

[ Parent | on HN ]