Skip to content

Blog

Notes from building and running BoringCache.

What I've learned about repeated build work as I took BoringCache from simple save and restore APIs you could use anywhere to build-tool integrations and caching inside Docker.

RSS feed
  • BoringCache
  • Benchmarks
  • CI caching

Seven months of benchmarking my CI build cache on real projects

Since March, I've benchmarked BoringCache on PostHog, Zed and Deno as their code changes. Here's where it makes builds faster, where another cache is level or faster, and how much data, egress and runner size it saves.

18 min read
  • BoringCache
  • Benchmarks
  • CI caching

Cache, not bigger runners

Why I chose shared cache and object storage instead of larger runners, and what that choice looks like on PostHog and a 40 GB Rust target.

7 min read
  • Rust
  • Cargo
  • CI caching

Reusing large Rust builds on fresh runners

How I use content-defined chunks and client optimizations to save and restore large Cargo targets, and what I'm doing about accumulated build outputs.

9 min read
  • Rails
  • Deployment

How I deploy Rails to plain Linux

I build Rails with Dagger, reuse the slow work with BoringCache, then send one filesystem artifact to four Ubuntu servers.

8 min read
  • Docker
  • BuildKit
  • CI caching

A Docker layer miss doesn't mean a cold build

When BuildKit has to run a step again, portable cache mounts and native tool caches can preserve cached directories and tool results for reuse inside that step.

11 min read
  • BoringCache
  • CI caching

Introducing BoringCache

After a year of building it, I'm introducing BoringCache: shared cache, build outputs and container images wherever the build runs.

10 min read
  • Rust
  • Cargo
  • sccache

Rust build cache is three caches, not one

I thought Rust build cache meant the target directory. Building the BoringCache CLI taught me why dependency state, Cargo target state, and sccache solve different parts of the build.

17 min read
  • BuildKit
  • Benchmarks

The BuildKit backend we deleted after it worked

I tried moving BuildKit state between ephemeral runners. Restoring it was fast, but changed builds were slower than the simpler cache backend.

15 min read
  • Docker
  • BuildKit

Docker build done. Still exporting cache…

A Docker build could finish its build steps and then spend minutes exporting cache. I wanted to prepare the cache while those steps were running.

13 min read
  • BoringCache
  • CI caching

Why I built BoringCache

I started with a slow Ruby install on an old MacBook Air. I wanted to reuse work that another machine had already done, wherever I chose to build.

6 min read

Work through a build problem.

The practical guides cover setup choices, slow exports, and missing cache.