Thanks for the WarpBuild love!
381 karma · joined May 29, 2019
Thanks for the WarpBuild love!
I make a similar product offering fast Github actions runners[1] and we've been down this rabbit hole of boot time optimization.
Eventually, we realized that the best solution is to actually build scale. There are two factors in your favor then: 1) Spikes are less pronounced and the workloads are a lot more predictable. 2) The predictability means that you have a decent estimate of the workload to expect at any given time, within reason for maintaining an efficient warm pool.
This enables us to simplify the stack and not have high-maintenance optimizations while delivering great user experience.
We have some pretty heavy use customers that enable us to do this.
As someone who builds a product on top of this, it's rather frustrating that their status page are usually a half hour delayed and incomplete.
It's fantastic that the 3vcpu variant is free for public repos on gha on all plans now though.
The VM reboot times add up quickly and that's likely the rationale. However, it gets hard when there are users running linting jobs that take ~2s but running it with 16vcpu instances so we kept the 1 min floor.
I agree with the stuff you've mentioned, obviously, but also empathize a bit with the GitHub folks because of all the licences and limitations Mac runners come with.
The perf for comparable operations is squarely on them though.
[1] https://docs.warpbuild.com/runners#macos-m2-pro-on-arm64
Automated container layer caching is coming in ~2 weeks.
This will be present transparently so you'll be able to get the goodness with zero changes to your current actions.
So you'll get that goodness when running CI with zero changes to your actions needed.
The docs are wip - it'll be updated in the next couple of days.
Benchmarks are hard to come by but iirc, each VMM adds a 3-5% overhead. The gatekeeping for permissions and sandboxing that is done at each level involves active compute cycles and that adds a little overhead.
Something of the order of 10% may not be large but there's a difference.[1]
Disk IO is another major factor btw, since virtual filesystems can be ... flaky.
Could you elaborate on the pain points with using containers?
May be easier to think of it as an $8 credit. It shows up as such in the dashboard.