←back to thread

SourceFS: A 2h+ Android build becomes a 15m task with a virtual filesystem

(www.source.dev)
137 points cdesai | 1 comments | 22 Oct 25 12:39 UTC | HN request time: 0.001s | source
Show context
Ericson2314 ◴[22 Oct 25 15:46 UTC] No.45670912[source]▶
The headline times are a bit ridiculous. Are they trying to turn https://github.com/facebook/sapling/blob/main/eden/fs/docs/O... or some git fuse thing into a product?
replies(2): >>45671058 #>>45671060 #
zokier ◴[22 Oct 25 15:55 UTC] No.45671060[source]▶
Well they also claim to be able to cache build steps somehow build-system independently.

> As the build runs, any step that exactly matches a prior record is skipped and the results are automatically reused

> SourceFS delivers the performance gains of modern build systems like Bazel or Buck2 – while also accelerating checkouts – all without requiring any migration.

Which sounds way too good to be true.

replies(4): >>45671827 #>>45671987 #>>45672236 #>>45677349 #
1. CJefferson ◴[23 Oct 25 01:55 UTC] No.45677349[source]▶
I used to use a python program called ‘fabricate’ which did this. If you track every file a compiler opens, then id the same compiler is run with the same flags, and no input changed, you can just drop a cached copy of the outputs in place.

I’m actually disappointed this type of thing never caught on, it’s fairly easy on Linux to track every file a program accesses, so why do I need to write dependency lists?