Join us

Dynamic AutoScaling of GitHub Runners

Dynamic AutoScaling of GitHub Runners

This article describes Dgraph Labs' transition from a self-hosted on-prem TeamCity setup to GitHub Actions for their CI/CD needs. They were facing challenges with high compute costs, maintenance efforts, and configuration time, which led them to explore GitHub Actions.

With GitHub Actions, they were able to reduce their compute costs, maintenance efforts, and configuration time. However, they still faced challenges with idle runners and manual attach/detach of runners.

To solve these challenges, they built an in-house solution called "Dynamic AutoScaling of GitHub Runners." Their architecture includes VM images, SSM Parameter Store, and an orchestrator, which monitors GitHub events and dynamically scales up or down based on the job queue and available runner count. They also provide a financial analysis showing the significant cost savings they achieved after enabling Dynamic AutoScaling of GitHub Runners.


Let's keep in touch!

Stay updated with my latest posts and news. I share insights, updates, and exclusive content.

Unsubscribe anytime. By subscribing, you share your email with @faun and accept our Terms & Privacy.

Give a Pawfive to this post!


Only registered users can post comments. Please, login or signup.

Start writing about what excites you in tech — connect with developers, grow your voice, and get rewarded.

Join other developers and claim your FAUN.dev() account now!

Avatar

The FAUN

FAUN.dev()

@faun
The FAUN watches over the forest of developers. It roams between Kubernetes clusters, code caves, AI trails, and cloud canopies, gathering the signals that matter and clearing out the noise.
Developer Influence
3k

Influence

302k

Total Hits

3711

Posts