icecream

Some other alternatives, also haven't hearded about this one: - SN DBS - https://www.snsystems.com/ - Used by a lot of game developers, to spread mostly compilation (but also shader compile, or custom jobs). - IncrediBuild - https://www.incredibuild.com/ - Fast build - https://www.fastbuild.org/ - icecream - https://github.com/icecc/icecream - Goma - https://chromium.googlesource.com/infra/goma/client/ - Bazel / buck / like with various RBE back ends - https://bazel.build/remote/rbe - distcc - https://www.distcc.org/ - ElectricAccelerator - https://docs.cloudbees.com/docs/cloudbees-build-acceleration/11.0/ - and many others... I've had mostly experience with IncrediBuild in the past, currently SN-DBS, but colleagues are looking into FASTBuild. Though my personal favorite is bazel

Neat! I remember using [something similar][1] at a previous job. [1]: https://github.com/icecc/icecream

Related: https://github.com/icecc/icecream - another option that does what distcc does, but aimed at a somewhat different use case. https://ccache.dev/ - a similar idea but provides caching of build outputs instead of distributing builds. You can use it together with distcc to achieve even better performance.

This. If you're thinking about distcc, try icecream first, it is much nicer. > But unlike distcc, Icecream uses a central server that dynamically schedules the compile jobs to the fastest free server. https://github.com/icecc/icecream

If you like distcc, did you ever give icecc a try? https://github.com/icecc/icecream I never had the time to set it up properly, but by the looks of it, it should be even better.

A couple of tools to make compile farms easier to use: https://distcc.github.io/ https://github.com/icecc/icecream

is this the icecream you speak of? https://github.com/icecc/icecream I've never heard of it so I was intrigued.

rollcall of essential tools if you are in C/C++ land: no build should be without https://ccache.dev/, and after that, distcc https://distcc.github.io/, icecream https://github.com/icecc/icecream, and goma https://chromium.googlesource.com/infra/goma/ may be used for distributing the workload.

If you like distcc, perhaps you'd also like icecream https://github.com/icecc/icecream which I think is a bit easier to use.

This appears to be referring to a distcc derivative https://github.com/icecc/icecream Note that discc doesn't really solve the header problem, it just throws more compute at it.

Developers at my company who work on a large shared C++ codebase all use Icecream[0] to distribute the builds across their workstations. I've only hooked into it to build once since I don't work in that codebase, but it seems to work pretty well scaling it (I think on the order of 50-60 servers and about the same number of clients). As for caching, I think sccache[1] is designed to handle that in a scalable way, although I've personally only used it locally for my Rust builds. [0]: https://github.com/icecc/icecream [1]: https://github.com/mozilla/sccache

Icecc (an old distcc fork) also distributes the toolchain, to avoid that particular problem. https://github.com/icecc/icecream

"Goma is a distributed compiler service for open-source project such as Chromium and Android. It's some kind of replacement of distcc+ccache." https://chromium.googlesource.com/infra/goma/client/ I know that Opera at least, had been using icecream (https://github.com/icecc/icecream) internally to do distributed builds, and occasionally the main repo would make a modification to the build system that would break it. One time this actually resulted in the discovery of a bug in the llvm project (https://bugs.chromium.org/p/chromium/issues/detail?id=778209). Hopefully external teams that are building chromium will have this pain point alleviated. :)