May 16, 2026
Build cache glow-up or new headache?
Content-defined chunking added to Bazel
Bazel learns to send only the changed bits, and the comments are already fighting about it
TLDR: BuildBuddy added a way for Bazel to re-send only the parts of big build files that changed, cutting uploads and cache size by about 40% in its tests. Commenters love the potential, but one big debate popped up fast: is this a brilliant efficiency boost or something attackers could abuse?
Bazel just got a new trick, and the dev crowd is reacting like a group chat that suddenly discovered a life hack. The big promise is wonderfully simple: instead of re-sending a giant file every time one tiny part changes, BuildBuddy’s new system tries to send only the changed pieces. On its own repo, the company says it saw about 40% less data uploaded and a 40% smaller cache on disk. In plain English: faster builds, less waste, fewer giant re-downloads when a barely changed app package or binary gets a brand-new fingerprint.
But of course, the real entertainment is in the replies. One commenter immediately went full security-mode, asking whether bad actors could game the system and force weirdly tiny or absurdly huge chunks. That’s the kind of comment that turns a shiny optimization story into a mini thriller: is this a clever upgrade, or the start of a new class of chaos? Another commenter came in with the classic engineer response: can we use this for Docker too? Suddenly the mood shifted from suspicion to opportunism, with readers eyeing other places this idea could save time and money.
So the vibe around this Bazel update is a mix of “finally, this is smart” and “okay, but what’s the catch?” It’s not meme-level carnage, but it is that very online developer flavor of drama where one person spots a possible disaster, another sees a business opportunity, and everyone else starts imagining fewer painful builds.
Key Points
- •BuildBuddy says its Remote Cache now uses content-defined chunking so large Bazel outputs can be reused at the chunk level instead of as whole blobs.
- •In BuildBuddy's benchmark on its own repository, the Bazel chunking implementation reduced uploaded data by 40% and reduced disk cache size by 40%.
- •The article says client-side CDC with BuildBuddy requires Bazel 8.7 or 9.1+ and the `--experimental_remote_cache_chunking` flag.
- •The inefficiency addressed by CDC is most visible in transitive actions such as linking, bundling, packaging, and archiving, where small source changes can create new digests for large outputs.
- •Without CDC, remote caches upload, download, and store entire new blobs for mostly similar outputs; disabling caching avoids transfers but sacrifices reuse and can complicate remote execution.