Skip to content
ccache remote cache

Compile C and C++ with shared results.

Connect ccache to a workspace your CI and local builds can use. Reuse eligible compiler results without replacing your compiler or build system.

With ccache configured in your build system:

.boringcache.toml
workspace = "my-org/app"

[adapters.ccache]
tag = "ccache-cache"
command = ["cmake", "--build", "build"]
boringcache ccache

Use ccache as you do today.

Compiler results

Reuse compatible compiler outputs.

Existing build configuration

Keep ccache configured in CMake, Meson, or Make.

Cache visibility

Inspect hits, misses, errors, and transfers.

Keep your compiler setup explicit.

BoringCache provides shared storage; it does not select your compiler launcher. Configure ccache in your build system before running the adapter.

See which compilations used cache.

Inspect ccache requests, hits, misses, timeouts, and errors alongside cache transfers.

Explore the workspace →
OBS Studio · Workspace insights
Cache hits

BoringCache · GitHub runner · 4 vCPU

96.2% of 16,612 lookups over 28 builds

Served from the runner
Under 1 ms per read
Read from cache
4.23 GB

ccache benchmark

All ccache results →

Build times grouped by runner, with cold and warm builds shown separately.

OBS Studio

ccache

Benchmark →

Video recording and live streaming application in C and C++.

Average restore, build and save · lower is better

GitHub runner

4 vCPU · 16 GB · Ubuntu 26.04 x86-64

BoringCache
1 min 52 s 28 builds
GHA Cache
2 min 3 s 28 builds
Same CPU model

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.

GHA Cache vs BoringCache
1.28× · 11 of 28
6 CPU models recorded
BoringCache · Remote storage
AMD EPYC 7763 (15 builds) · AMD EPYC 9V45 (5 builds) · AMD EPYC 9V74 (5 builds) · Intel Xeon 6973P-C (2 builds) · Intel Xeon Platinum 8573C (1 build)
GHA Cache · Local cache directory restored and saved by actions/cache
AMD EPYC 7763 (14 builds) · AMD EPYC 9V45 (5 builds) · AMD EPYC 9V74 (3 builds) · Intel Xeon Platinum 8573C (3 builds) · Intel Xeon Platinum 8370C (2 builds) · Intel Xeon 6973P-C (1 build)
Cache hits

BoringCache · GitHub runner · 4 vCPU

96.2% of 16,612 lookups over 28 builds

Served from the runner
Under 1 ms per read
Read from cache
4.23 GB

Keep shared-cache publication in trusted jobs.

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

  • Trusted builds Publish shared cache for the next build Read + publish
  • Pull requests Restore cache without replacing it Read only
  • Local development Use a scoped credential for the workspace Scoped access

Common questions

Does BoringCache replace ccache?
No. ccache still decides cache keys, hits, and misses. BoringCache supplies its shared remote storage and lifecycle.
Will BoringCache configure my compiler launcher?
Keep ccache configured as your compiler launcher. With CMake, set CMAKE_C_COMPILER_LAUNCHER and CMAKE_CXX_COMPILER_LAUNCHER to ccache. BoringCache does not change your compiler selection.
Is ccache always faster than a directory cache?
No. Remote storage supports reuse, but total time depends on setup, transfer, and the amount of compiler work. Measure the complete build on your project.
Read the ccache setup guide →

Set up ccache caching

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 ccache