Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Open-source x64 and Arm GitHub runners

ubicloud.com

Post reply on HN
Print view View original

111–120 of 128 posts

Re: Show HN: Open-source x64 and Arm GitHub runners

#111

Post by Aeolun »

crohr wrote: post #105
Aeolun wrote: post #92

How does this pricing work? With purely spot based AWS runners we can barely reach the 10x cost treshold compared to github runners. Edit: Oh, Hetzner. They’re really ubiquitous in cheap computing these days.

You can reach 10x cheaper with just AWS, especially on the larger runner sizes. That is even including disk costs. I put a calculator for RunsOn at https://runs-on.com/calculator/

I mean, I did just say that, but it seems to me they can’t just resell AWS spot instances because there’d be no margin left.

Re: Show HN: Open-source x64 and Arm GitHub runners

#112

Post by suryao »

tmpfs wrote: post #98

This looks great and the pricing is obviously a big improvement, I will try it out for our Linux jobs. Sure would be good to see competition for the MacOS and Windows runners too, these are the ones that tend to cost us the most.

We at WarpBuild currently support mac instances (M2 Pros). Windows support will come soon.

Re: Show HN: Open-source x64 and Arm GitHub runners

#113

Post by boundlessdreamz »

crohr wrote: post #106
MuffinFlavored wrote: post #30

Earlier quoted context omitted.

> so for us it's been faster to disable cache entirely and just redo everything on each build. I wonder what the consequential "carbon footprint" of this is, but at scale for all companies/all jobs of similar nature

One of the goal of my own hosted runner project [1] is to display the carbon cost and money cost after each run. Too many people are oblivious of the costs and I think as an industry it would be great to at least get the data points. [1]: https://runs-on.com

This is pretty much exactly what I wanted (yay for custom images) but the pricing makes it a non starter. Please consider a tiered monthly pricing based on build minutes.

Re: Show HN: Open-source x64 and Arm GitHub runners

#114

Post by OJFord »

umur wrote: post #73
robertlagrant wrote: post #47

Earlier quoted context omitted.

If we're doing nits, because this product looks cool, here are a couple of potential tweaks: > Imagine to do more I'd get rid of this. I don't understand the phrase, and it sounds like fluff. > Fast runs even at this price point I'd get rid of the "point". "Price point" isn't a synonym for "price", which I think is what's being attempted here. I'd be tempted to just have no tagline, and retitle this section "Faster t…

Much appreciate the nits! I've made a few minor tweaks right now, we will do a more complete revision later on.

> Fast runs even at this price

what about: 'Cheaper doesn't mean slower'? It's pithier, and (in particular for anyone reading before/without looking at the page) better IMO in its place as a subheading. Scans better. Or even 'Cheaper != slower' (again, subhead).

Re: Show HN: Open-source x64 and Arm GitHub runners

#115

Post by OJFord »

gitter101 wrote: post #91

what stops GitHub from shutting down these offerings from a legal or technical perspective, these alternatives clearly violate their terms of service: "Additionally, regardless of whether an Action is using self-hosted runners, Actions should not be used for: the provision of a stand-alone or integrated application or service offering the Actions product or service, or any elements of the Actions product or service,…

No that means you can't create a CI/CD competitor that's 'hosted' in Actions. (e.g. Install OJFordCI GitHub app, pay at ojfordci.com/sign-up, view your CI results at ojfordci.com, but actually also at github.com in the Actions tab on your repo.)

They absolutely support custom runners, it's how all these work, they don't need to stop them via ToS, they can just not allow it as an option. `runs-on: ubicloud` only works because GitHub implements it right.

Re: Show HN: Open-source x64 and Arm GitHub runners

#116

Post by okeuro49 »

sophiabits wrote: post #86
ploxiln wrote: post #57

Earlier quoted context omitted.

Also consider the carbon footprint of using caches! Apparently it takes longer, because it has to send/recv more data, compress and decompress, cause load on other systems ... It's really kinda impossible to judge the carbon footprint for these kinds of things, and if it's justified. Consider the carbon footprint of all the dumb AI feature rolled out at Facebook, Google, etc. Consider the carbon footprint of everyone…

There’s a French think tank called “The Shift Project” which actually produced a report estimating CO2 impact of data transfer a few years ago [1]! The numbers are obviously very rough; there’s a LOT of factors to consider and which vary from one node to another. But the methodology is quite comprehensive, e.g. they factor in power consumption of the end user’s device while waiting for the data to transfer over the w…

It was PHP 5.4 -> PHP 7.0. There was no 6.

Re: Show HN: Open-source x64 and Arm GitHub runners

#117

Post by ayewo »

electroly wrote: post #49
suryao wrote: post #20

Earlier quoted context omitted.

We support GitHub MacOS 13 runners on M2 Pros at WarpBuild [1]. They're about 25% faster and 50% cheaper per minute compared to the equivalent GitHub hosted runners. [1] https://docs.warpbuild.com/runners#macos-m2-pro-on-arm64

Any timeline for supporting repositories in personal accounts? I'm willing to create an organization and move the repository, but I won't bother if it's right around the corner. macOS ARM runners are a gamechanger given the offensively high pricing GitHub offers them at.

Have you seen this announcement by GitHub regarding Apple Silicon:

https://github.blog/changelog/2024-01-30-github-actions-intr... ?

Today, GitHub is excited to announce the launch of a new M1 macOS runner! This runner is available for all plans, free in public repositories, and eligible to consume included free plan minutes in private repositories. The new runner executes Actions workflows with a 3 vCPU, 7 GB RAM, and 14 GB of storage VM, which provides the latest Mac hardware Actions has to offer. The new runner operates exclusively on macOS 14 and to use it, simply update the runs-on key in your YAML workflow file to macos-14.

Re: Show HN: Open-source x64 and Arm GitHub runners

#118

Post by andag »

I want the vendor that can take care of this for us, but that can guarantee a private egress range, or can run things within our VPC.

Several builds connect to internal resources, so running them on external nodes suboptimal and expensive when it comes to network egress.

Re: Show HN: Open-source x64 and Arm GitHub runners

#119

Post by electroly »

ayewo wrote: post #117
electroly wrote: post #49

Earlier quoted context omitted.

Any timeline for supporting repositories in personal accounts? I'm willing to create an organization and move the repository, but I won't bother if it's right around the corner. macOS ARM runners are a gamechanger given the offensively high pricing GitHub offers them at.

Have you seen this announcement by GitHub regarding Apple Silicon: https://github.blog/changelog/2024-01-30-github-actions-intr... ? Today, GitHub is excited to announce the launch of a new M1 macOS runner! This runner is available for all plans, free in public repositories, and eligible to consume included free plan minutes in private repositories. The new runner executes Actions workflows with a 3 vCPU, 7 GB RAM, a…

I had not seen it--thank you!

Re: Show HN: Open-source x64 and Arm GitHub runners

#120

Post by pinkgolem »

crohr wrote: post #107
pinkgolem wrote: post #51

Earlier quoted context omitted.

Iops on GitHub runners is also terrible slow, you easily get a 5x to 10x improvement We did the same, and set up GitHub actions runners on hetzner Halfed the integration test time and made them more reliable.

Just a catch with Hetzner vs AWS: pricing at AWS is per-second while Hetzner is per-hour, which is (very) inconvenient if you're launching ephemeral runners.

while thats true.. i am using TestFlows-GitHub-Hetzner-Runners, which recycles runner for the 1 hour lifetime, works like a charm so far

also main reason for switching was performance, not cost for us.

Post reply on HN