Buildfarm vs clcache
Buildfarm
buildfarm.github.ioclcache
github.comSide by side
| Figure | Buildfarm | clcache |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| Linux | Yes | — |
| API | Yes | — |
| Self-hosted | Yes | — |
| Plans published | 0 | 1 |
| Spec score · Build Cache Software | 7.8 (#11) | 7.4 (#19) |
| License | The project repository identifies its license as Apache-2.0. | The project source is subject to the BSD 3-Clause License unless a file states otherwise. |
| Purpose | Buildfarm implements the Remote Execution API for remote caching and execution. | clcache is a Python script that avoids unnecessary recompilation by reusing cached object files for Microsoft Visual Studio. |
Plans
In their own words
Buildfarm
Buildfarm has no write-up on Specifiction yet; its figures are above.
clcache
clcache is a free, open-source Python script for Windows builds using Microsoft Visual C++ cl.exe. It intercepts compiler calls and reuses cached object files to avoid recompiling matching work, while unsupported invocations can be passed to the real compiler. Cache keys use preprocessed source, a normalized command line, and the compiler binary’s size and modification time. Command-line controls provide statistics, cleanup, clearing, and maximum-size settings; the default limit is 1073741824 bytes (1 GiB). Object files can be compressed at levels 1 through 9, though changing compression settings requires clearing the cache. Hard-link mode requires cache and build directories on the same drive. Documentation covers Visual Studio and MSBuild integration, recommends disabling TrackFileAccess, and describes optional hash caching and memcached storage. The documented path requires /c, excludes /link and /Zi, and supports /Z7. INCLUDE and LIBPATH changes may not be detected.