aayushshah15

5 ms·

1.
How Blacksmith runs more than 10M CI jobs a day(blacksmith.sh)
8 points by aayushshah15 14d ago|0 comments
2.
by aayushshah15 1y ago
Yes! This is documented in our docs: https://docs.blacksmith.sh/blacksmith-caching/docker-builds#... , the TLDR is that you can use the `build-push-action` with `setup-only: true`.
3.
by aayushshah15 1y ago
[cofounder of blacksmith here] This is on our radar! The primitives mentioned in this blog post are fairly general and allow us to support various types of artifact storage and caching protocols.
4.
How we built a logging platform for GitHub Actions with ClickHouse(blacksmith.sh)
5 points by aayushshah15 1y ago|1 comments
5.
by aayushshah15 1y ago
> one downside I've observed with some serverless in the past is that it can introduce up-front latency delays as the system spins up support to handle your spike [cofounder of blacksmith here] This is exactly one of the symptoms of
6.
by aayushshah15 2y ago
Some backstory on this: we've been working on a storage primitive to power incremental docker builds for Blacksmith's GitHub Actions runners. We realized early on that this was going to be a useful capability on its own since we n
7.
Show HN: Sticky Disks in GitHub Actions(github.com)
13 points by aayushshah15 2y ago|1 comments
8.
Ask HN: How do you insure against regressions in performance critical codepaths?
4 points by aayushshah15 2y ago|1 comments
9.
by aayushshah15 2y ago
> I'm unwilling to use graphite if I can't convince the rest of my team OOC, what are the main objections against?
10.
by aayushshah15 2y ago
That issue is from 2020 and has already been addressed. The fact that io_uring support is not "GA" is mostly a semantic aspect that doesn't affect most use-cases.
11.
by aayushshah15 2y ago
> Firecracker didn't have a very compelling I/O story Can you provide any sources for this claim? We're running Firecracker in production over at blacksmith dot sh and haven't been able to reproduce any perf regressio
12.
Fly.io Outage(status.flyio.net)
7 points by aayushshah15 2y ago|2 comments
13.
by aayushshah15 2y ago
We're noticing our development instances (which run on Fly.io) have been down for over an hour.
14.
by aayushshah15 2y ago
I'm obviously biased here but this is what we do at blacksmith dot sh. We run you GitHub Actions on consumer grade desktop CPUs with high single core performance, all inside ephemeral Firecracker VMs. Give us a shot!
15.
Stacked Diffs Can Be Expensive: Why You Should Do It More(blacksmith.sh)
4 points by aayushshah15 2y ago|0 comments
16.
by aayushshah15 2y ago
Well, the point was that if 4 concurrent `git push`es saturates up to 1500 vCPUs then you'd need 16 of those hetzner dedicated servers (which you have to manage the uptime for) that you're paying for for the entire month. ~4 pushe
17.
by aayushshah15 2y ago
> we buy one or two very expensive machines that run CI and builds This unfortunately does not work for orgs that have, say, more than 20 engineers. The core issue is that once you have a test suite large enough to have ~30 shards, you o
18.
by aayushshah15 2y ago
A previous org I worked at had a python script (written by a PM) to download our github actions job history and shove that into an excel sheet. How this is still not offered by GitHub actions is beyond me.
19.
by aayushshah15 2y ago
Obligatory comment about India taxing air conditioners as luxury goods while people are literally dying of heat strokes every summer
20.
by aayushshah15 2y ago
The other side of this spectrum is that the founders spend months of their time fundraising rather than actually building the company.
21.
"But YC takes 7% of my company " – Our experience of YC W24(blacksmith.sh)
8 points by aayushshah15 2y ago|4 comments
22.
Local Docker registry caches in GitHub Actions(blacksmith.sh)
3 points by aayushshah15 2y ago|0 comments
23.
by aayushshah15 2y ago
This is simply false. For starters, GitHub actions by default run on Intel Haswell chips from 2014 (in some cases). Secondly, hardware being faster doesn't obviate the need for caching, especially for docker builds where your layer pul
24.
by aayushshah15 2y ago
A subtle challenge with "sticky disks" is that it requires your workflow steps to be idempotent beyond the point of "resumption", which can be tricky in a lot of cases.
25.
by aayushshah15 2y ago
GitHub has perverse incentives to not fix this problem because they charge customers based on usage (by the minute), so they make more money by providing slower builds to end-users.
26.
by aayushshah15 2y ago
Did you consider using a local (in the same VPC) docker registry mirror perhaps? https://docs.docker.com/docker-hub/mirror/
27.
by aayushshah15 2y ago
how do you ensure isolation between runs on a self hosted runner that way?
28.
by aayushshah15 2y ago
(blacksmith co-founder here) it's unfortunate the amount of expertise / tinkering required to get "incrementalism" in docker builds in github actions. we're hoping to solve this with some of the stuff we have in the