Docker layers
Skip a Dockerfile instruction when BuildKit finds matching inputs and a cached result.
Keep Docker layers, package downloads, and compiler results between builds. When your code changes, reuse the work that still matches, on your laptop or your CI runners.
The instruction runs. Inner caches can still match.
Tool results
Compiler and task outputs
Package caches
Downloads already stored
Skip a Dockerfile instruction when BuildKit finds matching inputs and a cached result.
Keep pnpm, npm, or uv downloads between builds with opt-in persistent cache mounts.
Reuse matching ccache, sccache, Go, or Turborepo results inside an instruction that runs again.
Keep your Dockerfile and build on your existing runners. Start with shared layers, then add the tool caches and mounts your build needs.
A source change can make a build instruction run again. Your compiler, build tool, and package manager can still reuse their own cached work, even on a fresh builder.
Add native tool caching for matching results. Persist cache mounts for downloads and directories you want to keep between builds.
Configure Docker layers and inner caches →ccache · sccache · Go · Turborepo
Read matching results from native tool caches.
pnpm · npm · uv
Restore selected Dockerfile cache mounts.
See cache reads and transfers for each Docker build.
Explore the workspace →BoringCache · GitHub runner · 4 vCPU
98.5% of 2,486 lookups over 30 builds
Build times grouped by runner, with cold and warm builds shown separately.
Docker
Benchmark →Product analytics platform. One Docker image with the Django backend and Node.js frontend.
Average restore, build and save · lower is better
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
Base · Image layers
Plus · Image layers, tool caches and cache mounts
Builds of one commit can land on different CPU models. These ratios use only the build pairs where both caches ran on the same model; above 1.00× means BoringCache's total time over those pairs was lower.
Each table is one workflow run with one build per cache. A row marked Different CPU ran on another CPU model than BoringCache at the same level, so part of its time difference can come from the hardware.
| Cache | Cold | Warm | CPU |
|---|---|---|---|
| Base · Image layers | |||
| BoringCache Image layers | 15 min 28 s | 2 min 13 s | Cold: AMD EPYC 7763 · Warm: AMD EPYC 9V74 |
| Plus · Image layers, tool caches and cache mounts | |||
| BoringCache + Image layers, tool caches and cache mounts | 16 min 29 s | 3 min 4 s | Cold: AMD EPYC 7763 · Warm: Intel Xeon Platinum 8573C |
| Cache | Cold | Warm | CPU |
|---|---|---|---|
| GHA Cache Buildx type=gha, mode=max | 39 min 59 s | 3 min 6 s | Cold: AMD EPYC 7763 · Warm: AMD EPYC 9V74 |
| GHCR Buildx type=registry, mode=max | 23 min 24 s | 2 min 44 s | AMD EPYC 7763 |
4 vCPU · 16 GB · Ubuntu 24.04 Arm64
Base · Image layers
Plus · Image layers, tool caches and cache mounts
Neoverse-N2
Each table is one workflow run with one build per cache. A row marked Different CPU ran on another CPU model than BoringCache at the same level, so part of its time difference can come from the hardware.
| Cache | Cold | Warm | CPU |
|---|---|---|---|
| Base · Image layers | |||
| BoringCache Image layers | 12 min 51 s | 2 min 20 s | Neoverse-N2 |
| Plus · Image layers, tool caches and cache mounts | |||
| BoringCache + Image layers, tool caches and cache mounts | 12 min 32 s | 2 min 18 s | Neoverse-N2 |
| Cache | Cold | Warm | CPU |
|---|---|---|---|
| GHA Cache Buildx type=gha, mode=max | 26 min 41 s | 2 min 39 s | Neoverse-N2 |
| GHCR Buildx type=registry, mode=max | 16 min 37 s | 2 min 15 s | Neoverse-N2 |
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
Base · Image layers
Plus · Image layers, tool caches and cache mounts
Each table is one workflow run with one build per cache. A row marked Different CPU ran on another CPU model than BoringCache at the same level, so part of its time difference can come from the hardware.
| Cache | Cold | Warm | CPU |
|---|---|---|---|
| Base · Image layers | |||
| BoringCache Image layers | 12 min 27 s | 61.1 s | AMD EPYC 9R45 |
| Plus · Image layers, tool caches and cache mounts | |||
| BoringCache + Image layers, tool caches and cache mounts | 10 min 57 s | 59.7 s | AMD EPYC 9R45 |
8 vCPU · 32 GB · Ubuntu 24.04 x86-64
Base · Image layers
Plus · Image layers, tool caches and cache mounts
AMD EPYC 9R45
Each table is one workflow run with one build per cache. A row marked Different CPU ran on another CPU model than BoringCache at the same level, so part of its time difference can come from the hardware.
| Cache | Cold | Warm | CPU |
|---|---|---|---|
| Base · Image layers | |||
| BoringCache Image layers | 5 min 4 s | 47.3 s | AMD EPYC 9R45 |
| Plus · Image layers, tool caches and cache mounts | |||
| BoringCache + Image layers, tool caches and cache mounts | 5 min 33 s | 52.0 s | AMD EPYC 9R45 |
16 vCPU · 32 GB* · x86-64
Each table is one workflow run with one build per cache. A row marked Different CPU ran on another CPU model than BoringCache at the same level, so part of its time difference can come from the hardware.
| Cache | Cold | Warm | CPU |
|---|---|---|---|
| Depot builder Builds on Depot's remote BuildKit machine | 6 min 46 s | 2 min 10 s | Not recorded |
* Builder sizes published by providers.
4 vCPU · 16 GB · x86-64
Base · Image layers
Plus · Image layers, tool caches and cache mounts
AMD EPYC
Each table is one workflow run with one build per cache. A row marked Different CPU ran on another CPU model than BoringCache at the same level, so part of its time difference can come from the hardware.
| Cache | Cold | Warm | CPU |
|---|---|---|---|
| Base · Image layers | |||
| BoringCache Image layers | 7 min 32 s | 44.8 s | AMD EPYC |
| Plus · Image layers, tool caches and cache mounts | |||
| BoringCache + Image layers, tool caches and cache mounts | 9 min 21 s | 52.9 s | AMD EPYC |
8 vCPU · 16 GiB* · x86-64
Each table is one workflow run with one build per cache. A row marked Different CPU ran on another CPU model than BoringCache at the same level, so part of its time difference can come from the hardware.
| Cache | Cold | Warm | CPU |
|---|---|---|---|
| Namespace builder Builds on Namespace's remote BuildKit machine | 8 min 27 s | 3 min 51 s | Not recorded |
* Builder sizes published by providers.
BoringCache · GitHub runner · 4 vCPU
98.5% of 2,486 lookups over 30 builds
Give consumers restore access and publishers a separate permission. Connect supported CI through OIDC or use scoped credentials.
Connect your CI →Separate readers and publishers
Send me a repo or a workflow and I'll take a look. I've spent more than a year on slow Docker, Cargo and Bazel builds in CI.
Install the CLI. Run onboarding to connect your repository and configure your cache.
30-day trial. No credit card required.
curl -sSL https://install.boringcache.com/install.sh | sh
boringcache onboard
boringcache docker
We use cookies to understand how people use BoringCache. Privacy policy