sccache
A local sccache install stores compiled object outputs and related compiler result artifacts on disk so repeated Rust and C/C++ builds can reuse previous work instead of recompiling. That cache can accumulate many hashed entries, compressed object files, dependency results, and temporary index metadata across toolchain, flag, and source changes, often growing into multiple gigabytes. Kudu removes only sccache's local disk cache contents, freeing space and clearing stale compile artifacts without touching source code, Cargo or CMake projects, credentials, or compiler settings.
Why clean sccache?
- Old cached compile results after a compiler, SDK, or build-flag change can miss reuse opportunities, so builds feel inconsistent and a supposedly incremental rebuild takes unexpectedly long
- A cache that has grown to several GB can fill an SSD or home directory quota, showing up as low-disk-space warnings even though your actual project files are much smaller
- Corrupted cache entries from an interrupted build or abrupt shutdown can cause repeated cache misses and unnecessary recompilation, which you notice as fans spinning up and compile times jumping around
- Switching between Rust toolchains, C/C++ compilers, or target architectures leaves behind large sets of no-longer-reusable artifacts, wasting disk space with no benefit to current builds
- Stale dependency and object result artifacts can mask whether sccache is helping at all, so cleaning is a quick way to reset hit rates when builds have become mysteriously slower than expected
- On shared workstations and CI-like local environments, accumulated cache entries from many branches and build configurations bloat the local cache directory and make disk usage climb after every compile
Cache paths Kudu targets
Windows
%LocalAppData%/Mozilla/sccache/cache |
macOS
~/Library/Caches/Mozilla.sccache |
Linux
~/.cache/sccache |
Common questions about sccache
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.