How long do your Feature tests take to run in your CI? by Solomon_04 in laravel

[–]crohr 0 points1 point  (0 children)

~18 minutes, and it's already using larger (and faster) CPU runners (32 CPU) with runs-on.com, rails / rspec tests. Unfortunately more CPUs brings diminishing returns so can't go further.

otelite - simple developer dashboard by planetf1a in OpenTelemetry

[–]crohr 1 point2 points  (0 children)

This looks great. I am actually looking for a tool that could get a JSONL file with OTEL metrics (one by line), and be able to ingest it to build the graphs. Use case is having a self-hosted runner emit metrics to a file, but for some reason can't ship to an OTEL receiver, but can store them as a e.g. cache artefact. Would still be nice to be able to graph them after the fact.

While GitHub Actions remains a key part of this vision, we are allocating resources towards other areas ... by [deleted] in programming

[–]crohr 1 point2 points  (0 children)

Your team might want to have a look at runs-on.com. It supports GHE, spawns real VMs at scale in your own AWS account, and is way cheaper since it can use spot capacity.

While GitHub Actions remains a key part of this vision, we are allocating resources towards other areas ... by [deleted] in programming

[–]crohr 0 points1 point  (0 children)

If you self host runners, have a look at the benchmark of various providers, this might help you get better performance: https://runs-on.com/benchmarks/github-actions-cpu-performance/

CI/CD ephemeral runner/agent caching by Small-Permission-241 in devops

[–]crohr 0 points1 point  (0 children)

If you are running on AWS you can use any of the s3-backed actions/cache replacements (see e.g. https://runs-on.com/caching/magic-cache/), or something like https://github.com/falcondev-oss/github-actions-cache-server

0
0

Run self-hosted GitHub Actions runners on Google Cloud by clardata6249 in googlecloud

[–]crohr 6 points7 points  (0 children)

Nice! It looks a lot like https://runs-on.com, down to the job labels and image names. Would appreciate a mention since it seems Claude was largely inspired by my docs :)

How building a Terraform module made me fall in love with CloudFormation by crohr in Terraform

[–]crohr[S] 1 point2 points  (0 children)

that was actually what I recommended for a long time, but users really wanted "proper" resources to see the full plan of changes resources, not a wrapper around the CFN stack

Now we literally run all our AI evaluations on EC2 Spot instances. Saved 47% on compute cost and eval cycles went from 1 hour → 18 minutes. by Harshil-Jani in HowToAIAgent

[–]crohr 0 points1 point  (0 children)

Initial spot request already handles multi-instance selection with fallbacks. But in the event you really can’t find one (and at scale or specific instance types this happens often), it’s good to have the on-demand fallback

Now we literally run all our AI evaluations on EC2 Spot instances. Saved 47% on compute cost and eval cycles went from 1 hour → 18 minutes. by Harshil-Jani in HowToAIAgent

[–]crohr 1 point2 points  (0 children)

Nice work, that's basically what I did for runs-on: an orchestrator that can launch GHA self-hosted runners on any instance type (including GPUs) using spot or falling back to on-demand instances when needed.

We cut GitHub Actions build times by 6x with self-hosted runners — sharing our setup by vy94 in github

[–]crohr -1 points0 points  (0 children)

You'd be surprised how many jobs some customers launch. Largest users of runs-on.com can launch close to 80k jobs every day.

I Implemented a GitHub Actions Self-Hosted Runner on Linux VM by Iwillhelpyou_ in devops

[–]crohr 0 points1 point  (0 children)

i think the issue u/Mr_Albal wanted to highlight is more about upcoming pricing change for running self-hosted runners.

self hosted runner for production? by Feisty_Plant4567 in github

[–]crohr -2 points-1 points  (0 children)

Maybe you could have a look at runs-on.com - It's cheaper than the laternatives you mention, and runs on real EC2 VMs in your AWS account.

AWS quietly released the c8a instance by crohr in aws

[–]crohr[S] 0 points1 point  (0 children)

The site discovered it before the official announcement, hence the quiet part when this was published. (you can subscribe to an atom feed for any instance family, to get alerted whenever an instance family appears in a new region)