381 karma · joined May 29, 2019
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.
Try out the jobs once again - you should be okay (I think :) )
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.
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.
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 :-)
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
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!
Try it out if you can, you will like the results :-)
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.
There's just so much time and compute wasted otherwise.
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
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.
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.
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.
[...] 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.