Improving GitHub Actions Cache Performance Through Reverse Engineering
By
tsaifu
10mo ago· 8 min readenNews
100/100
Golden Brown
Bagelometer↗
Slow-proofed and worth the wait. Worth its weight in flour.
Score100TypenewsSentimentneutral
Summary
The article discusses the process of reverse engineering GitHub Actions cache to improve performance without requiring code changes or maintaining forks of upstream actions.
Key quotes
· 3 pulledOur approach was different: we forked each of the popular first-party actions that depended on Actions cache to point to our faster, colocated cache.
Maintaining these forks steadily turned into a nightmare for us.
This delivered up to 10x faster cache performance for some of our customers, with no code changes required and no need to maintain forks of upstream actions.
We reverse engineered GitHub Actions cache internals to transparently route cache requests through our faster, colocated cache. This delivered up to 10x faster cache performance for some of our customers, with no code changes required and no need to maint
You might also wanna read
How GitHub Issues improved navigation performance with client-side caching and prefetching
GitHub's Issues team tackled navigation latency by rethinking how issue pages load end-to-end. Instead of chasing marginal backend improveme
GitHub·17d ago
GitHub's Performance Improvements for Pull Request Diff Rendering
GitHub engineers discuss their efforts to improve performance in the pull request review experience, specifically focusing on the Files chan
GitHub·1mo ago
Tenki Cloud: A Cost-Effective and Faster Alternative to GitHub Actions
Tenki Cloud offers a GitHub Actions alternative that is 90% cheaper and 30% faster, with a 2-click migration process and Autoscale Runner fo
Product Hunt·1y ago