I’m the maintainer of RunsOn (https://github.com/runs-on/runs-on), which solves this problem with far less investment
331 karma · joined January 23, 2012
Currently launching https://runs-on.com, 10x cheaper GitHub Action runner, on premise.
More details at https://cyrilrohr.com
I’m the maintainer of RunsOn (https://github.com/runs-on/runs-on), which solves this problem with far less investment
Must be installed in your AWS account (1-click cloudformation template), and then you can use any instance type offered by AWS.
Once this improves I’ll be sure to update it.
For those hitting that same kind of issue (and you are many), you should check out my product https://runs-on.com. 1-click install, 1-click upgrades, and from 7x to 16x cheaper runners on AWS.
Also note that I specifically mentioned that "all third-parties are good on that front, expected [sic] Ubicloud (but that may change)."
Also agree that now that you removed the outdated CPUs (was still active end of May), the analysis should mention that you have OK CPUs by now. I will fix it.
For providers that are on this page, do not hesitate to write to me if you find the analysis outdated for your specific service.
[edit] page is now up to date with new analysis
But at 37% cheaper than x64 it's quite a better deal than what the outdated x64 CPUs.
This. I went the same route with regards to boot time optimisations for [1] (cleaning up the AMI, cloud-init, etc.), and can boot a VM from cold in 15s (I can't rely on prewarming pools of machines -- even stopped -- since RunsOn doesn't share machines with multiple clients and this would not make sense economically).
But the time taken by the official runner binary to load and then get assigned a job by GitHub always takes around 8s, which is more than half of the VM boot time :( At some point it would be great if GitHub could give us a leaner runner binary with less legacy stuff, and tailored for ephemeral runners (that, or reverse-engineer the protocol).
It does work as advertised, try it :) And yes RunsOn is a direct competitor to the 5 YCombinator-funded companies operating in this space (Ubicloud, Warpbuild, Buildjet, Blacksmith, Depot).
https://runs-on.com/reference/caching/ https://runs-on.com/features/s3-cache-for-github-actions/
It is very hard for a single player to get favourable treatment from Azure / AWS / GCP to handle many thousands of jobs every day / hour.
I wish Depot all the luck, I think they've done good work wrt caching.
Really good thing is the declarative nature of it. When you release upgrades to AWS accounts where you don't have any control, this makes everything safer (and simpler to manage).
I'll also benchmark the z1d.
In your case your workflow can run in less than 5 minutes on AWS ephemeral machines, for the same price as ubicloud: https://github.com/runs-on/arroyo/actions/runs/7723361513/jo...
[1]: https://runs-on.com
I put a calculator for RunsOn at https://runs-on.com/calculator/
But in the meantime I’ve recently released RunsOn [1] with the same promise (10x cheaper, faster) but the whole thing runs in your AWS account.
[1]: https://runs-on.com
RunsOn is installed in one click with a CloudFormation template, which deploys a private GitHub App for the organization of your choice (even personal).
The App then receives workflow job events from GitHub, and takes care of spawning EC2 instances to act as your GitHub runners.
In your workflows, you then have to do this simple change:
- runs-on: ubuntu-latest
+ runs-on: runs-on,runner=16cpu-linux
The README has a lot more details as to how you can customize the runs-on label.
Some key advantages:
* up to 10x cheaper than GitHub, and 4x cheaper than the competition.
* 1-1 workflow compatibility for your existing workflows, since we maintain replicas of the official runner images.
* x64 and arm64 architecture are supported.
* bring your own AMIs, or customize the default ones with preinstall scripts.
* your code stays in your own infrastructure. * we take extra precaution to ensure no runner is left dangling, thanks to AWS TerminateOnShutdown feature and watchdog scripts.
I also made sure that the stack is easy to troubleshoot:
* any problem when starting runners is automatically surfaced in a special management issue.
* daily cost usage is also displayed in the management issue.
* SSH access to the runners if needed.
It has been a lot of joy creating this tool, and most companies having a bill of a few hundred dollars on GitHub will quickly see the ROI, especially if you need higher-spec runners.
Disclaimer: the tool is free for non-commercial usage, and comes with a flat license fee for commercial usage.
In the tests with my GitHub Action [1] that spawns ephemeral runners for any workflow, I found BuildJet bandwidth speed 10 to 20 times slower than machines at AWS.