SourceFS: A 2h+ Android build becomes a 15m task with a virtual filesystem
1–10 of 66 posts
Re: SourceFS: A 2h+ Android build becomes a 15m task with a virtual filesystem
#2Why tf does an electric vehicle need 500m+ lines of code
Re: SourceFS: A 2h+ Android build becomes a 15m task with a virtual filesystem
#3Could you just do the build in /dev/shm?
Re: SourceFS: A 2h+ Android build becomes a 15m task with a virtual filesystem
#4While it looks like at least some of the team are ex-googlers, this isn't the srcfs we know from piper (Google internal tools).
Looks like it's similar in some ways. But they also don't tell too much and even the self-hosting variant is "Talk to us" pricing :/
Re: SourceFS: A 2h+ Android build becomes a 15m task with a virtual filesystem
#5The 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?
Re: SourceFS: A 2h+ Android build becomes a 15m task with a virtual filesystem
#6Their performance claims are quite a bit ahead of the distributed android build systems that I've used, I'm curious what the secret sauce is.
Re: SourceFS: A 2h+ Android build becomes a 15m task with a virtual filesystem
#7Could you just do the build in /dev/shm?
No. `/dev/shm` would just be a build in `tmpfs`.
Though from what I gather form the story, part of the spedup comes from how android composes their build stages.
I.e. speeding up by not downloading everything only helps if you don't need everything you download. And adds up when you download multiple times.
I'm not sure they can actually provide a speedup in a tight developer cycle with a local git checkout and a good build system.
Re: SourceFS: A 2h+ Android build becomes a 15m task with a virtual filesystem
#8While it looks like at least some of the team are ex-googlers, this isn't the srcfs we know from piper (Google internal tools). Looks like it's similar in some ways. But they also don't tell too much and even the self-hosting variant is "Talk to us" pricing :/
WDYM this seems very familiar. At commit deadbeef I don't need to materialize the full tree to build some subcomponent of the monorepo. Did I miss something?
And as for pricing... are there really that many people working on O(billion) lines of code that can't afford $TalkToUs? I'd reckon that Linux is the biggest source of hobbyist commits and that checks out on my laptop OK (though I'll admit I don't really do much beyond ./configure && make there...)
Re: SourceFS: A 2h+ Android build becomes a 15m task with a virtual filesystem
#9Why tf does an electric vehicle need 500m+ lines of code
Some people actually write tests.
Re: SourceFS: A 2h+ Android build becomes a 15m task with a virtual filesystem
#10The 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?
It seems like that plus some build output caching?