Compiler reuse
sccache decides whether an invocation can use a stored result.
Give Rust, C, and C++ builds access to one shared sccache store. Reuse eligible compilations from CI, containers, and local development.
.boringcache.toml
workspace = "my-org/app" [adapters.sccache] tag = "sccache-cache" command = ["cargo", "build", "--release"]
boringcache sccache
permissions: contents: read id-token: write steps: - uses: boringcache/one@1781572d7b3ec5aef652f8ba479b981439b2776b # v1.48.2 with: mode: sccache trust-policy: auto - run: cargo build --release
steps: - label: Build command: > boringcache ci run --oidc-provider buildkite -- boringcache sccache
build: timeout: 1h id_tokens: BORINGCACHE_OIDC_TOKEN: aud: urn:boringcache:workload script: - boringcache ci run --oidc-provider gitlab -- boringcache sccache
sccache decides whether an invocation can use a stored result.
Matching compiler-cache data is stored once in the workspace.
Inspect compiler-cache reads, writes, and transfers.
The sccache adapter connects compiler caching to your command. For Rust builds that also need dependency and target-state reuse, use the Cargo integration.
Inspect cache hits, misses, and transfers from sccache in your workspace.
Explore the workspace →BoringCache · GitHub runner · 4 vCPU
97.1% of 20,352 lookups over 8 builds
Build times grouped by runner, with cold and warm builds shown separately.
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
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
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 sccache
We use cookies to understand how people use BoringCache. Privacy policy