Hacker News Reader

I’d guess that’s for a fairly slow machine, or else the prices would be pretty high?

What sort of spec machine (or kubernetes pod) are you providing for that?

its a `2 vCPU, 7.5GB RAM` -- so far tested with open source projects including NDK and it stood up pretty well. Build times post close to what it would take on the local dev machine. Overall experience is that once you push your commit in about `2 mins + (local build time) mins` you'll get an email with the CI result.

Product wise we don't want the user to worry about machine resources as long as CI executes within reasonable time.

We can rent CPU/RAM in the cloud by the minute, but we can’t do that with the computer we’re developing on locally. I think this should naturally leads to faster builds being done in CI, more cost effectively, rather than CI being the slower builds.

Out of interest, have you modelled spot instance restarts into your costs? How about spot instance pricing going up?

Reply on news.ycombinator.com