suryao

6 ms·

31.
by suryao 2y ago
TLDR: disk is often the bottleneck in builds. Use 'fio' to get performance of the disk. If you want to truly speed up builds by optimizing disk performance, there are no shortcuts to physically attaching NVMe storage with high thr
32.
by suryao 2y ago
If you're building rust containers, we have the world's fastest remote container builders with automated caching. You wouldn't really have to change anything on your dockerfile to leverage this and see significant speed up. T
33.
by suryao 2y ago
You might want to check out my product, WarpBuild[0]. We are fully usage based, no minimums etc., and our container builders are faster than others on the market. We also have a BYOC option that gives 10x cost reduction and used by many cus
34.
by suryao 2y ago
There definitely are a ton of issues with GitHub actions. To add to the OP's list: - Self-hosting on your aws/gcp/azure account can get a little tricky. `actions-runner-controller` is nice but runs your workflows within a doc
35.
A bear case: My predictions regarding AI progress(lesswrong.com)
204 points by suryao 2y ago|215 comments
36.
by suryao 2y ago
This sucks for individuals and open source. For folks that have a heavy reliance on dockerhub, here are some things that may help (not all are applicable to all use cases): 1. Setup a pull through mirror. Google Artifact Registry has decent
37.
by suryao 2y ago
Check out my project, WarpBuild [1], if you want managed Mac VMs for CI/CD purposes. It plugs in nicely to the GitHub actions ecosystem and provides machines on demand. [1] https://warpbuild.com
38.
by suryao 2y ago
hey - https://www.warpbuild.com is the website the pricing is https://www.warpbuild.com/pricing
39.
by suryao 2y ago
Ha,forgot to add for private repos.
40.
by suryao 2y ago
For cheaper (for private repos) and faster arm64 runners, check out what we're making at WarpBuild. We also support spinning up self-hosted runners on your AWS/gcp/azure in just a couple of clicks.
41.
by suryao 2y ago
Great article. Do you have throughput comparisons? I've found r2 to be highly variable in throughput, especially with concurrent downloads. s3 feels very consistent, but I haven't measured the difference.
42.
Guide to Self-Host GitHub Actions Runners on EKS using actions-runner-controller(warpbuild.com)
2 points by suryao 2y ago|1 comments
43.
by suryao 2y ago
I put together a detailed write-up on setting up self-hosted GitHub Actions Runners using ARC (Actions Runner Controller) on AWS using EKS. This includes terraform code for provisioning the infrastructure, and helm configurations for Karpen
44.
Hosting GitHub Actions runners in your GCP, AWS VPC(docs.warpbuild.com)
1 points by suryao 2y ago|0 comments
45.
by suryao 2y ago
This is absolutely true. We run fairly heavy duty CI infra and I can say with confidence that this is one of the biggest factors impacting CI runner performance, almost equal in weight to raw CPU perf.
46.
by suryao 2y ago
If it needs to be asked, historically the answer has been a resounding Yes.
47.
by suryao 2y ago
This is very useful. How do you get the self-hosted runner costs - directly with the aws/gcp/azure integration or something else?
48.
PS5 Pro Is Released(playstation.com)
3 points by suryao 2y ago|0 comments
49.
by suryao 2y ago
It is definitely a high-spend area. It is not uncommon for teams that are <50 people to spend ~$2-5000/month on CI, sometimes more. There are repos we've seen that are heavily sharded for testing and trigger ~50-200 separate jo
50.
by suryao 2y ago
Thanks for posting about our recent launch.
51.
GitHub Actions artifacts leaking auth tokens in projects like Firebase and Clair(bleepingcomputer.com)
1 points by suryao 2y ago|0 comments
52.
by suryao 2y ago
Thought I'd plug my product because of the mention of actions-runner-controller on k8s. I wouldn't wish that on my worst enemy :) It is a terrible experience riddled with many gotchas. I'm making WarpBuild to provide runners
53.
by suryao 2y ago
incremental CI is absolutely the way to go
54.
by suryao 2y ago
This is pretty cool - provides a good speed up for container builds. The couple of beefy instances can set you back $200-1000 a month on aws apart from the regular github action runner costs and it only goes up from there. We have a way aro
55.
by suryao 2y ago
Any such error is a bug. We do have tons of ruby users running 1000s of jobs each hour but maybe we are hitting a corner case with you, I'm sorry that that happened and I'll look into it. Switching from github actions default runn
56.
by suryao 2y ago
The MacOS runners are in our cloud (not user's AWS) and are usage based. Users pay only for the actual minutes of usage.
57.
GitHub Actions with large runners are delayed(githubstatus.com)
1 points by suryao 2y ago|0 comments
58.
by suryao 2y ago
Yes, but likely in ~1.5 months.
59.
by suryao 2y ago
Thanks for being patient with us through our teething issues. I think you'll like the stuff in our pipeline :-)
60.
Show HN: 10x cheaper GitHub Actions on your AWS account(warpbuild.com)
30 points by suryao 2y ago|12 comments

More ›