Viewing profile — aayushshah15
aayushshah15
HN member- Joined
- Fri, Oct 11, 2019, 8:10 PM UTC
- HN karma
- 34
- Public activity
- 27 items
- HN profile
- View on Hacker News ↗
About aayushshah15
No profile information was provided.
Recent public activity
-
comment
Comment #44664511
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`.…
-
comment
Comment #44659311
[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 cac…
- story
-
comment
Comment #43984761
> 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 bla…
-
comment
Comment #42732751
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 goi…
- story
-
story
Ask HN: How do you insure against regressions in performance critical codepaths?
If you work on performance-critical systems like database software or language runtimes, what sort of tooling do you use to insure against regressions in the critical codepaths in …
-
comment
Comment #42275377
> I'm unwilling to use graphite if I can't convince the rest of my team OOC, what are the main objections against?
-
comment
Comment #42033943
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.
-
comment
Comment #42029279
> 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…
-
comment
Comment #41917437
We're noticing our development instances (which run on Fly.io) have been down for over an hour.
- story
-
comment
Comment #41425054
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 epheme…
- story
-
comment
Comment #41231577
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) tha…
-
comment
Comment #41231138
> 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…
-
comment
Comment #40513838
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 Git…
-
comment
Comment #40513619
Obligatory comment about India taxing air conditioners as luxury goods while people are literally dying of heat strokes every summer
-
comment
Comment #40190851
The other side of this spectrum is that the founders spend months of their time fundraising rather than actually building the company.
- story
- story
-
comment
Comment #39958423
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 cac…
-
comment
Comment #39958396
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.
-
comment
Comment #39958289
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…
-
comment
Comment #39958155
Did you consider using a local (in the same VPC) docker registry mirror perhaps? https://docs.docker.com/docker-hub/mirror/