<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/accelerating-development-for-massive-git-repositories-38rzq6nl9" -->

---
title: Accelerating development for massive Git repositories
description: Google open-sourced ABFS, a virtual filesystem and build cache that slashes Android checkout and build times. The Android 17 open source release has 1,084 Git...
canonical: https://daily.dev/posts/accelerating-development-for-massive-git-repositories-38rzq6nl9
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Accelerating development for massive Git repositories | daily.dev
og:description: Google open-sourced ABFS, a virtual filesystem and build cache that slashes Android checkout and build times. The Android 17 open source release has 1,084 Git...
og:url: https://daily.dev/posts/accelerating-development-for-massive-git-repositories-38rzq6nl9
og:image: https://api.daily.dev/og/posts/38RzQ6NL9.png
og:image:alt: Accelerating development for massive Git repositories
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Accelerating development for massive Git repositories

**[Google Developers](https://daily.dev/sources/googledevs)** · 7 min read · 1 upvotes · 1 comments

## Summary

Google open-sourced ABFS, a virtual filesystem and build cache that slashes Android checkout and build times. The Android 17 open source release has 1,084 Git repositories, 1.62 million files, and takes 300 GB for a built workspace. Traditionally, it took over 30 minutes to fetch AOSP source and well over an hour to build. With ABFS, mounting a workspace takes under 8 seconds each, and an agent can check out a full Android tree in under 10 seconds and perform a full build in under 10 minutes. The system uses a content-addressable filesystem (CASFS) to lazy-load files and Ninja-go, which replaces timestamp checks with two-phase content-addressable caching, letting developers and AI agents mount multiple Android branches and run parallel builds on one machine.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://developers.googleblog.com/accelerating-development-for-massive-git-repositories>

## Questions this post answers

### What is Google's ABFS and how does it speed up Android builds?

ABFS (Another Build File Service) is Google's open-source virtual filesystem and build cache that lazy-loads source code and caches build outputs across a content-addressable storage layer. It cuts a full Android checkout to under 8 seconds and a complete build to under 10 minutes, down from over 30 minutes to fetch and over an hour to build traditionally.

_Engineers scaling large monorepo builds can track ABFS developments on daily.dev as the tooling matures._

### How many Git repositories and files does a full Android AOSP checkout contain?

The Android 17 open source release contains 1,084 Git repositories and 1.62 million files, taking 300 GB for a fully built workspace. A typical Android tree with hardware vendor code and first-party apps is 2 to 3 times larger, exceeding 3,000 Git repositories across multiple SKU and maintenance branches.

_Teams evaluating monorepo scaling strategies can follow this kind of benchmark data on daily.dev._

### Why is Ninja's timestamp-based build caching unreliable for large codebases like Android?

Ninja rebuilds an output whenever its input file is newer, but build rules can introduce hidden dependencies, over-declared inputs, or undeclared outputs. These issues silently produce stale incremental artifacts in timestamp-based builds, forcing developers to wipe output directories and run clean builds. Google's Ninja-go replaces this with two-phase content-addressable caching instead.

_Developers debugging stale build caches can keep up with build-system fixes like this via daily.dev._

## Community discussion

Top comments from developers on daily.dev.

**@pdfopsdev** · 0 upvotes

> vfs for git and edenfs solved basically the same problem for windows and meta's monorepos years ago, curious how CASFS's lazy load compares on cold cache misses over a slow link vs those.

## Similar posts on daily.dev

- [LayerFS: The filesystem for AI coding agents](https://daily.dev/posts/layerfs-the-filesystem-for-ai-coding-agents-0b7soblux) · Hacker News · 0 upvotes · 0 comments
- [Uber Builds GitFarm to Run Git Operations as a Service for Large-Scale Monorepos](https://daily.dev/posts/uber-builds-gitfarm-to-run-git-operations-as-a-service-for-large-scale-monorepos-jj2rqjqnt) · InfoQ · 2 upvotes · 0 comments
- [Scaling Developer Experience: How We Improved Android Studio in a Large Monorepo](https://daily.dev/posts/scaling-developer-experience-how-we-improved-android-studio-in-a-large-monorepo-c27iviirr) · Grab Tech Blog · 0 upvotes · 0 comments

---

Tags: [#android](https://daily.dev/tags/android), [#git](https://daily.dev/tags/git), [#build-systems](https://daily.dev/tags/build-systems)

[View this post on daily.dev](https://daily.dev/posts/accelerating-development-for-massive-git-repositories-38rzq6nl9)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Accelerating development for massive Git repositories","url":"https://daily.dev/posts/accelerating-development-for-massive-git-repositories-38rzq6nl9","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/accelerating-development-for-massive-git-repositories-38rzq6nl9"},"datePublished":"2026-11-17T17:14:15.976Z","dateModified":"2026-11-17T17:29:52.798Z","description":"Google open-sourced ABFS, a virtual filesystem and build cache that slashes Android checkout and build times. The Android 17 open source release has 1,084 Git...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/750bdc82be3df39a70f659a5d1bb6f58?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/750bdc82be3df39a70f659a5d1bb6f58?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Google Developers","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Google Developers","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/ea4bbded4e7f45ccb82e121a3156535f","url":"https://daily.dev/sources/googledevs"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/accelerating-development-for-massive-git-repositories-38rzq6nl9","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"android,git,build-systems","timeRequired":"PT7M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Google Developers","item":"https://daily.dev/sources/googledevs"},{"@type":"ListItem","position":3,"name":"Accelerating development for massive Git repositories"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/accelerating-development-for-massive-git-repositories-38rzq6nl9","comment":[{"@type":"Comment","text":"vfs for git and edenfs solved basically the same problem for windows and meta’s monorepos years ago, curious how CASFS’s lazy load compares on cold cache misses over a slow link vs those.","datePublished":"2026-11-17T18:01:35.084Z","url":"https://daily.dev/posts/38RzQ6NL9#c-b1We58imM","author":{"@type":"Person","name":"PDFops","url":"https://daily.dev/pdfopsdev","image":"https://media.daily.dev/image/upload/s---8isRBKc--/f_auto/v1782922291/avatars/avatar_orjMeK8QKaaVZwGq7ScPz?_a=BAMAMicg0"}}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/accelerating-development-for-massive-git-repositories-38rzq6nl9#faq","mainEntity":[{"@type":"Question","name":"What is Google's ABFS and how does it speed up Android builds?","acceptedAnswer":{"@type":"Answer","text":"ABFS (Another Build File Service) is Google's open-source virtual filesystem and build cache that lazy-loads source code and caches build outputs across a content-addressable storage layer. It cuts a full Android checkout to under 8 seconds and a complete build to under 10 minutes, down from over 30 minutes to fetch and over an hour to build traditionally. Engineers scaling large monorepo builds can track ABFS developments on daily.dev as the tooling matures."}},{"@type":"Question","name":"How many Git repositories and files does a full Android AOSP checkout contain?","acceptedAnswer":{"@type":"Answer","text":"The Android 17 open source release contains 1,084 Git repositories and 1.62 million files, taking 300 GB for a fully built workspace. A typical Android tree with hardware vendor code and first-party apps is 2 to 3 times larger, exceeding 3,000 Git repositories across multiple SKU and maintenance branches. Teams evaluating monorepo scaling strategies can follow this kind of benchmark data on daily.dev."}},{"@type":"Question","name":"Why is Ninja's timestamp-based build caching unreliable for large codebases like Android?","acceptedAnswer":{"@type":"Answer","text":"Ninja rebuilds an output whenever its input file is newer, but build rules can introduce hidden dependencies, over-declared inputs, or undeclared outputs. These issues silently produce stale incremental artifacts in timestamp-based builds, forcing developers to wipe output directories and run clean builds. Google's Ninja-go replaces this with two-phase content-addressable caching instead. Developers debugging stale build caches can keep up with build-system fixes like this via daily.dev."}}]}
```

