Compiler outputs stay compiler-native
sccache still decides cacheability for Rust, C, and C++ compilation.
Getting started
On this page
j / k move between sections.
Docs / Adapter commands / sccache
Keep sccache in charge of compiler keys and reuse. The adapter supplies its remote endpoint, starts and stops the daemon, controls writes, and records native statistics.
sccache still decides cacheability for Rust, C, and C++ compilation.
Reuse compiler outputs across CI jobs and local development when paths and inputs line up.
Restore broadly, publish narrowly, and avoid giving every job write access.
Keep the command and cache tag in .boringcache.toml, then use the same boringcache sccache entrypoint locally and in CI.
[adapters.sccache] tag = "compiler-cache" command = ["cargo", "build", "--release"] # Run: boringcache sccache
The Action starts sccache with the shared remote store, exports compiler-wrapper settings, and stops the daemon after later workflow steps.
- uses: boringcache/one@1781572d7b3ec5aef652f8ba479b981439b2776b # v1.48.2 with: trust-policy: auto mode: sccache - run: cargo build --release
Approve the repository through Connect CI and grant the job contents: read and id-token: write. The Action uses that Machine connection. Pull requests restore by default; trusted jobs may publish. See the authentication example in the GitHub Actions reference for scoped credentials when OIDC is unavailable.
Deno, Zed, Zed on Namespace runners, and Zed release bundle build the same upstream commits with BoringCache, Depot Cache, GHA Cache, kache, GHA Cache + target, mr-boxington and Depot runner cache on the same runner classes.
Rust
Benchmark →JavaScript and TypeScript runtime 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 | 39 min 29 s | 29 min 26 s | AMD EPYC 7763 |
| Depot Cache sccache WebDAV backend | 43 min 11 s | 32 min 55 s | AMD EPYC 7763 |
| GHA Cache sccache GitHub Actions backend | 40 min 35 s | 34 min 39 s | Cold: Intel Xeon Platinum 8573C · Warm: AMD EPYC 9V74 Different CPU |
| kache | 33 min 0 s | 80.2 s | Cold: AMD EPYC 9V74 · Warm: AMD EPYC 7763 Different CPU |
| Plus · sccache, Cargo registry and target directory | |||
| BoringCache + sccache, Cargo registry and target directory | 41 min 52 s | 59.2 s | Cold: AMD EPYC 7763 · Warm: AMD EPYC 9V45 |
| GHA Cache + target sccache plus actions/cache for registry and target | 42 min 23 s | 28 min 14 s | AMD EPYC 7763 Different CPU |
| mr-boxington | 39 min 24 s | 34 min 8 s | Cold: Intel Xeon Platinum 8573C · Warm: AMD EPYC 9V74 Different CPU |
BoringCache · GitHub runner · 4 vCPU
97.1% of 20,352 lookups over 8 builds
Check the tool's own reference when you need cache-key rules, build settings, or version-specific behavior.
Compare every supported command, protocol, and Action mode in one place.
Adapter command index →Need help or found something unclear? Open an issue or browse the CLI repo.
We use cookies to understand how people use BoringCache. Privacy policy