Live data from Hacker News

Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds

warpbuild.com

31–40 of 89 posts

Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds

#31
One of the reasons we didn't go with buildjet was their concurrency limits (https://buildjet.com/for-github-actions/docs/about/pricing#c...) and the pricing on extending those limits.

We are a small company but our autoscaling cluster for GitHub actions on aws will scale up to >500vcpus during the work day when there are a lot of prs going in.

I don't see it documented anywhere, what are your concurrency limits on accounts?

Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds

#33
post #28

Earlier quoted context omitted.

Thanks for the feedback! We are currently seeing fairly heavy load. The hn hug of death is real. Tweaked some settings and the startup delays should be back to the sub-10 second range in a few minutes.

I suspected that :) Where do you guys host the servers that run Github actions? (startup time is better now but speed is still much worse than Github)

Right now, we are on a public cloud. We will be moving things onto our own infra with overflow on public clouds eventually.

Try out the jobs once again - you should be okay (I think :) )

Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds

#34
Are you having any slowdown right now? I have been waiting for a 32x to pick up a job for some time now:

  Requested labels: warp-ubuntu-latest-x64-32x
  Job defined at: .../workflows/ci.yml@refs/pull/294/merge
  Waiting for a runner to pick up this job...

Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds

#36
post #34

Are you having any slowdown right now? I have been waiting for a 32x to pick up a job for some time now: Requested labels: warp-ubuntu-latest-x64-32x Job defined at: .../workflows/ci.yml@refs/pull/294/merge Waiting for a runner to pick up this job...

We do only 2x, 4x, 16x right now. We can add 32x but generally haven't seen much demand for it.

Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds

#37

One of the reasons we didn't go with buildjet was their concurrency limits ( https://buildjet.com/for-github-actions/docs/about/pricing#c... ) and the pricing on extending those limits. We are a small company but our autoscaling cluster for GitHub actions on aws will scale up to >500vcpus during the work day when there are a lot of prs going in. I don't see it documented anywhere, what are your concurrency limits on…

We don't enforce concurrency limits. It is not something that we want our users to think about. I'd hate to worry about it too.

In general, we should be able to deal with spiky workloads of that scale without issue in a couple of minutes.

I'd love for you to try us out.

Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds

#38
post #18

We are currently on Buildjet and it has made significant difference for our rust builds. But I would change in a heartbeat for Windows and even more for MacOS support. Mind you only if it is per minute pricing. The GitHub Actions macos machines are sooo bad that anything else at this point I will take.

What do you need macOS for? Have you considered cross-compilation? Zig + Rust allows cross-compilation for Rust: https://actually.fyi/posts/zig-makes-rust-cross-compilation-...

Anything that interact with the kernel needs to be tested on the actual OS. Simiarly if you call native libraries. And Apple Clang masquerading as GCC or not having all upstream LLVM patches is also annoying.

Re: Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds

#39
post #18

We are currently on Buildjet and it has made significant difference for our rust builds. But I would change in a heartbeat for Windows and even more for MacOS support. Mind you only if it is per minute pricing. The GitHub Actions macos machines are sooo bad that anything else at this point I will take.

What do you need macOS for? Have you considered cross-compilation? Zig + Rust allows cross-compilation for Rust: https://actually.fyi/posts/zig-makes-rust-cross-compilation-...

A very common use case for macos runners is iOS builds.
Post reply on HN