Reverse engineering the GHA cache to improve performance (2024)

Reverse engineering the GHA cache to improve performance (2024)(depot.dev)

36 points by bootlegbilly 357 days ago | 6 comments

mohsen1 357 days ago |

I am confused https://news.ycombinator.com/item?id=44658909

kylegalbraith 357 days ago | |

Founder of Depot here. Looks like Blacksmith was inspired by our implementation from last May and wrote a similar post to ours here.

ayewo 357 days ago | | |

To help reduce the confusion for other visitor to this post, you might want to email the HN mods to add (2024) to the title .

This will make it clear that you guys built the prior art that Blacksmith took inspiration from.

jacobwg 357 days ago |

Since we launched this last year, GitHub released a v2 of their internal cache API [0], based on Twirp [1] of all things, so we adapted to that. Interestingly that Twirp service also receives Actions artifacts, though we have not intercepted those today given that you likely still want them to appear in the GitHub UI / be accessible from the GitHub API.

[0] https://github.com/actions/cache/discussions/1510

[1] https://github.com/twitchtv/twirp

kmcquade 357 days ago |

These guys do an insane amount of engineering to speed up builds and everyone follows. Love their blogs.

Zero chance I'd sign up for their competitors knowing how good the product is and that everyone else follows them. I don't know why Docker, JFrog, or GitHub don't just buy them already.