HNHacker News
TopNewBestAskShowJobs

suryao

381 karma · joined May 29, 2019

Founder, WarpBuild.com - fast, secure Github actions runners that speed up builds by 30+% and at half the cost. Get started in 2 mins.
submissionscomments
suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
A very common use case for macos runners is iOS builds.
suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
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.

suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
We do only 2x, 4x, 16x right now. We can add 32x but generally haven't seen much demand for it.
suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
I don't have benchmarks but here's another comment from the thread. https://news.ycombinator.com/item?id=38571518
suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
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 :) )

suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
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.

suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
There is a performance - cost envelope that we are pushing, which I believe github will be hard pressed to match.

Also, this is the first step in our broader objective to: (a) support all CI providers (b) provide ecosystem support and tooling for efficient build engineering. The latter is in the form of additional tools, recommendations to be incorporated into workflow design, build insights etc. We are just getting started.

suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
Absolutely! We're working on it
suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
VMs are a necessity if you are serious about security and isolation guarantees. I'd hope everyone else also uses it.

I haven't run benchmarks but this comment provides a glimpse - https://news.ycombinator.com/item?id=38571518

VM startup speed has many levels to it. Right now, we are doing the inefficient job of having a pool though we have some items in the roadmap to fix this better.

In terms of speed up, we are doing things differently. For instance, we are baking in container layer caching natively so that users can benefit. This leads to speed ups of 2-10x depending on how the dockerfile is structured for caching.

This is just the first step - we have a very exciting roadmap :-)

suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
We have a few users who were using BuildJet try us out and they like it. It's an easy switch if you want to check it out.
suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
That was oversight. Fixed it - thanks for pointing it out.
suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
From a first-principles perspective, the stack is as follows:

VMs on warpbuild: baremetal > hypervisor for VM > runner workload Container: baremetal > (cloud VM [1]) > k8s worker node OS > containerd > container OS > runner workload

This assumes containers are running on k8s, which is an okay assumption in this case. The perf penalty of using a VM is much lower.

Note: if you are referring to the VM spin up time, then it is a whole other story and we have taken some pains to mitigate that to achieve comparable spinup time.

[1] if using a non-bare metal ec2/gce instance, say

suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
There are 2 factors here:

1) I was being conservative on my promises. For instance, we have users who reported GHA runtimes going down from ~25m to ~9m [1] 2) Local builds have the amazing advantage of being able to cache subsequent runs. CI workflows are ephemeral. This introduces a performance penalty. However, we are working on something that automagically caches some builds, especially container builds, that would enable huge benefits of 2x-10x further.

Hope this clarifies!

[1] https://x.com/suryaoruganti/status/1730419264132370556

suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
Thanks for taking the time to read my little launch and glad that it's clearer what we do.

Try it out if you can, you will like the results :-)

suryao··on Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
We've had a few customers migrate over from BuildJet because WarpBuild is in active development. For instance, we are adding support for macos runners in Jan.

Our mission is broader than just fast runners - it's about better CI dev ex. This includes surfacing recommendations that would optimize build times, insights into the critical paths of workflows and more.

We're also investing in tooling to overcome issues that currently exist, such as an action to ssh into running workflows for easy debugging.

suryao··on Lifetime deal on securely managing your environment secrets
Congrats on the launch!
suryao··on Run Gitlab pipelines 2x faster and 5x cheaper without changes in .gitlab-ci.yml
This is fantastic - we do something similar for Github actions with WarpBuild.

There's just so much time and compute wasted otherwise.

suryao··on India’s pickle people: Decades-old culinary heirlooms, nostalgia
I love bellam Avakaya. And the ginger garlic varieties are to die for.

My uncle (60+ yo) is a true connoisseur though. He loves it so much and abhors the mass manufactured stuff that he actually gets small batches made in India and even sells it in the US where he lives.

I helped build a Shopify storefront for him at Avakaya.com

suryao··on Virtualizing development environments in 2023
That's the mission we're on at Argonaut. I'd love to know more about how you think about it if you're up for a chat.
suryao··on K9s: A lazier way to manage Kubernetes Clusters
I'm a huge fan of k9s and we use it quite a bit at Argonaut.

I'm unaffiliated with the tool except as a user and a tiny sponsor, and I'd encourage users who are willing and able to sponsor this amazing tool as well.

suryao··on Tell HN: Heroku disabling monthly plans?
If anyone's intending to move to a full cloud such as AWS or GCP, we have built easy migration paths at Argonaut.
suryao··on Launch HN: Argonaut (YC S21) – Easily Deploy Apps and Infra to AWS and GCP
The user can interact with k8s directly. We do checks to ensure there are no breaking APIs between versions and have an upgrade path for the tools etc. that Argonaut installs. For custom helm charts etc. that users may setup directly, we work with users in a maintenance window for the upgrades.
suryao··on Launch HN: Argonaut (YC S21) – Easily Deploy Apps and Infra to AWS and GCP
Haha
suryao··on Launch HN: Argonaut (YC S21) – Easily Deploy Apps and Infra to AWS and GCP
This type of use case leverages Argonaut's flexibility maximally. For traditional apps, the push-to-deploy CI/CD can be setup. For Pulsar and ScyllaDB, and Elastic there are helm charts that can be used very easily as a part of our AddOns which we are expanding continuously. For Knative and clickhouse, the best way to run them would be through Kubernetes operators. While this can be setup using Argonaut today, the experience feels janky and we're working on making this a first class entity in the product.

The way Argonaut would help is by managing the configs and deployments in one place for easy collaboration and deployment, across environments and having GitOps with secret management for all the configs.

suryao··on Launch HN: Argonaut (YC S21) – Easily Deploy Apps and Infra to AWS and GCP
We are currently on AWS and GCP, with plans to expand to Azure later this year. Private clouds have not come up much in discussions so far, but we are open to it. How do you foresee a solution that works with private clouds to look like?
suryao··on Launch HN: Argonaut (YC S21) – Easily Deploy Apps and Infra to AWS and GCP
Responding on behalf of alex at cashflowy since I have some context. The team was originally on Elastic Beanstalk but chose to move to using kubernetes to leverage the rich ecosystem of helm charts. That enabled setup of tools like metabsse etc. very easily. Overall, it was lesser hassle for more functionality since CI/CD was also out of the box, and self-hosting these tools was a breeze with helm charts.
suryao··on Launch HN: Argonaut (YC S21) – Easily Deploy Apps and Infra to AWS and GCP
Google CloudRun (equivalent to ECS) and AWS ECS are great but they have some limitations in the type of workloads you can run. The choice of EKS (and GKE) was done for a few forward looking reasons including the ability to run any kind of workloads and more complex scenarios including enabling cloud portability for example. Else, it would lead to potential lock-in as companies diversify in their requirements.

With Argonaut, we try to make EKS easier to use than ECS to bring the best of both worlds. We handle the kubernetes version upgrades as well.

suryao··on Launch HN: Argonaut (YC S21) – Easily Deploy Apps and Infra to AWS and GCP
We handle things like maintenance. For example, kubernetes cluster upgrades are automated transparently for our users. We do not have auto remediation. That is a hard problem when we do not control the full runtime and hosting.
suryao··on Launch HN: Argonaut (YC S21) – Easily Deploy Apps and Infra to AWS and GCP
Reg Azure, pasting my response from elsewhere in the thread:

[...] in the Argonaut context, that only limits the overall infra management piece where we don't have a seamless integration using IAM roles and can't provision infra like dbs and queues. The app deployments to Azure kubernetes (or any k8s cluster) work seamlessly though, and some of our customers deploy to AKS in this manner.

We do not support gov cloud yet.

suryao··on Launch HN: Argonaut (YC S21) – Easily Deploy Apps and Infra to AWS and GCP
Do you mean a self-hosted option, since the product is self-service with support from our team? If so, I'd love to understand your constraints that require self-hosting. Email is surya@companyname.dev
← PreviousPage 4 of 5Next →