Dependency downloads
Restore crates and Git dependencies so Cargo doesn't have to download them again.
Reuse downloaded crates and compiled work in CI. Start a new local worktree from a target snapshot, with its own files to build and change. Cargo checks what needs rebuilding.
Crates and dependencies
Reuse downloads
Cargo target state
Skip work that's still fresh
sccache results
Reuse matching compiler outputs
Fresh CI runner
Local builds
Restore crates and Git dependencies so Cargo doesn't have to download them again.
Reuse compiled outputs that Cargo considers fresh, avoiding the compiler call entirely.
Reuse eligible compiler results when Cargo still needs to compile. Misses run the compiler normally.
The adapter preserves source freshness across target restores. Cargo checks changed inputs and reuses the outputs that still match your toolchain, target, and build flags.
Create a worktree for a branch or a coding agent without starting from an empty build cache. Local target snapshots reuse compiled work from a successful clean build in the same Git repository. Each worktree gets its own writable files.
Local snapshots are opt-in, need no remote credential, and have a configurable disk budget. Only empty targets are restored. Existing populated targets are kept.
Local target snapshot
From a successful clean build
Feature worktree
Own writable target
Cargo checks freshness
Agent worktree
Own writable target
Cargo checks freshness
Inspect restored build data, compiler-cache reads, and uploads in the same run.
Explore the workspace →BoringCache · GitHub runner · 4 vCPU
95.0% of 60,173 lookups over 30 builds
Build times grouped by runner, with cold and warm builds shown separately.
Rust
Benchmark →Code editor written in Rust.
Average restore, build and save · lower is better
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
Base · sccache compiler cache
Plus · sccache, Cargo registry and target directory
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 · sccache compiler cache | |||
| BoringCache sccache compiler cache | 34 min 31 s | 15 min 45 s | AMD EPYC 9V45 |
| Depot Cache sccache WebDAV backend | 51 min 8 s | 21 min 0 s | AMD EPYC 7763 Different CPU |
| GHA Cache sccache GitHub Actions backend | 48 min 54 s | 21 min 51 s | Cold: AMD EPYC 7763 · Warm: AMD EPYC 9V74 Different CPU |
| kache | 42 min 21 s | 5 min 0 s | Cold: Intel Xeon 6973P-C · Warm: AMD EPYC 7763 Different CPU |
| Plus · sccache, Cargo registry and target directory | |||
| BoringCache + sccache, Cargo registry and target directory | 51 min 8 s | 12 min 54 s | Cold: AMD EPYC 7763 · Warm: AMD EPYC 9V45 |
| GHA Cache + target sccache plus actions/cache for registry and target | 41 min 31 s | 36 min 30 s | Cold: AMD EPYC 9V74 · Warm: AMD EPYC 7763 Different CPU |
| mr-boxington | 34 min 59 s | 40 min 3 s | Cold: AMD EPYC 9V45 · Warm: AMD EPYC 9V74 Different CPU |
4 vCPU · 16 GB · Ubuntu 24.04 x86-64
Plus · sccache, Cargo registry and target directory
Base · sccache compiler cache
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 |
|---|---|---|---|
| Plus · sccache, Cargo registry and target directory | |||
| BoringCache + sccache, Cargo registry and target directory | 28 min 25 s | 8 min 17 s | AMD EPYC 9R45 |
| Base · sccache compiler cache | |||
| kache | 26 min 58 s | 3 min 50 s | AMD EPYC 9R45 |
8 vCPU · 16 GB · x86-64
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 |
|---|---|---|---|
| BoringCache + sccache, Cargo registry and target directory | 24 min 26 s | 5 min 38 s | AMD EPYC |
BoringCache · GitHub runner · 4 vCPU
95.0% of 60,173 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 cargo
We use cookies to understand how people use BoringCache. Privacy policy