User:Darkfader/distcc - Revision history

Darkfader: /* ccache and memcached */

2026-04-01T00:36:15Z

ccache and memcached

← Older revision		Revision as of 00:36, 1 April 2026
Line 182:		Line 182:


	=== ccache and ~~memcached~~ ===		=== ccache and distributed caches ===
	CCACHE is said to be conflicting with pump mode unless when you call them in the backend		CCACHE is said to be conflicting with pump mode unless when you call them in the backend
	so, where you start the compile, you don't use it		so, where you start the compile, you don't use it
Line 195:		Line 195:

	patch status is, unclear		patch status is, unclear


			zephyrOS runs KeyDB backend for distcc at scale since a while.
			They picked this software to not need a large ram redis server.
			One could alternatively use one system if it has enough ram (rumor has it DDR3 ECC is cheap)

	=== dockerized / native ===		=== dockerized / native ===

Darkfader: /* ccache and memcached */

2026-04-01T00:34:32Z

ccache and memcached

← Older revision		Revision as of 00:34, 1 April 2026
Line 188:		Line 188:
	they can share the cache via memcached, this is a nice trick for consistency		they can share the cache via memcached, this is a nice trick for consistency
	Upon looking at the ccache website, it seems the correct mechanism is not memcached but Redis. This would work just as well. Generally a cache shared in this way would be optimal for performance.		Upon looking at the ccache website, it seems the correct mechanism is not memcached but Redis. This would work just as well. Generally a cache shared in this way would be optimal for performance.



			This patch is described to be solving the interactions between ccache and distcc to work much better
			https://patch-diff.githubusercontent.com/raw/ccache/ccache/pull/301.diff

			patch status is, unclear

	=== dockerized / native ===		=== dockerized / native ===

Darkfader: /* Alternatives */

2026-03-29T14:25:22Z

Alternatives

← Older revision		Revision as of 14:25, 29 March 2026
Line 394:		Line 394:
	A commercial alternative (incredibuild https://www.incredibuild.com/) exists, but I have not tried it.		A commercial alternative (incredibuild https://www.incredibuild.com/) exists, but I have not tried it.
	There are references to some 'forever free' tier, also, but I could not yet find the terms and conditions for having a 'forever free thing'. it also seems you need a windows-based 'coordinator' host.		There are references to some 'forever free' tier, also, but I could not yet find the terms and conditions for having a 'forever free thing'. it also seems you need a windows-based 'coordinator' host.
	generally if there's some professional context with high (business) pressure for faster builds I would check that out, and then ~~there's more~~ time ~~to get~~ a great distcc setup ~~built in~~ the ~~meantime~~.		opinion: generally if there's some professional context with high (business) pressure for faster builds I would check that out, and then without time pressure build a great distcc setup for the long-term.


	Architecturally it seems to be taking the ccache approach with a shared cache and smarter redistribution.		Architecturally it seems to be taking the ccache approach with a shared cache and smarter redistribution.

Darkfader: /* Alternatives */

2026-03-29T14:23:32Z

Alternatives

← Older revision		Revision as of 14:23, 29 March 2026
Line 393:		Line 393:

	A commercial alternative (incredibuild https://www.incredibuild.com/) exists, but I have not tried it.		A commercial alternative (incredibuild https://www.incredibuild.com/) exists, but I have not tried it.
	~~THey advertise~~ some 'forever free' tier; generally if there's high (business) pressure for faster builds I would check that out.		There are references to some 'forever free' tier, also, but I could not yet find the terms and conditions for having a 'forever free thing'. it also seems you need a windows-based 'coordinator' host.
			generally if there's some professional context with high (business) pressure for faster builds I would check that out, and then there's more time to get a great distcc setup built in the meantime.

	Architecturally it seems to be taking the ccache approach with a shared cache and smarter redistribution.		Architecturally it seems to be taking the ccache approach with a shared cache and smarter redistribution.

Darkfader: /* selinux */

2026-03-28T22:42:55Z

selinux

← Older revision		Revision as of 22:42, 28 March 2026
Line 370:		Line 370:

	there's also a selinux policy for distcc from gentoo or liguros if one is so inclined.		there's also a selinux policy for distcc from gentoo or liguros if one is so inclined.
	https://repology.org/project/selinux-distcc/versions		links for further review:
	https://gitlab.com/liguros/liguros-repo/-/tree/stable/sec-policy/selinux-distcc
			- https://repology.org/project/selinux-distcc/versions
			- https://gitlab.com/liguros/liguros-repo/-/tree/stable/sec-policy/selinux-distcc

	=== general posture ===		=== general posture ===

Darkfader: /* selinux */

2026-03-28T18:14:36Z

selinux

← Older revision		Revision as of 18:14, 28 March 2026
Line 369:		Line 369:


	there's also a selinux policy for distcc from gentoo or liguros if one is so inclined.		there's also a selinux policy for distcc from gentoo or liguros if one is so inclined.
	https://repology.org/project/selinux-distcc/versions		https://repology.org/project/selinux-distcc/versions
			https://gitlab.com/liguros/liguros-repo/-/tree/stable/sec-policy/selinux-distcc

	=== general posture ===		=== general posture ===

Darkfader: /* Gitlab integration */

2026-03-28T18:13:39Z

Gitlab integration

← Older revision		Revision as of 18:13, 28 March 2026
Line 226:		Line 226:

	TBA		TBA

			Maybe work from this k8s howto, it's a bit more prod-grade than most:

			https://cinaq.com/blog/2020/05/10/speed-up-docker-builds-with-distcc-ccache-and-kubernetes/

	== Kernel specific settings ==		== Kernel specific settings ==

Darkfader at 16:33, 28 March 2026

2026-03-28T16:33:18Z

← Older revision		Revision as of 16:33, 28 March 2026
Line 114:		Line 114:



	~~=== untested build container system ===~~

	~~See this one https://github.com/bensuperpc/docker-distcc~~
	~~not yet tested, but this could be a good basis for a 'best practice' container.~~
	~~There's others, especially for crossbuilds, but those are also very complex to modify.~~

	== detail infos ==		== detail infos ==
Line 198:		Line 192:

	it remains mostly the same, a container needs to make sure it monitors the right services (distccd, nginx, include_server)		it remains mostly the same, a container needs to make sure it monitors the right services (distccd, nginx, include_server)
	if you're using zeroconf, you need to somehow expose the mdns service broadcasts & ~~reception~~		if you're using zeroconf, you need to somehow expose the mdns service broadcasts & receptio


			==== untested build container system ====

			See this one https://github.com/bensuperpc/docker-distcc
			not yet tested, but this could be a good basis for a 'best practice' container.
			There's others, especially for crossbuilds, but those are also very complex to modify.


	Processs list:		Processs list:

Darkfader: /* Operation */

2026-03-28T16:32:18Z

Operation

← Older revision		Revision as of 16:32, 28 March 2026
Line 219:		Line 219:
	==== localhost? =====		==== localhost? =====
	unclear if you need to use --allow for 127.0.0.1/32 or something to allow the remote preproccesor.		unclear if you need to use --allow for 127.0.0.1/32 or something to allow the remote preproccesor.


			=== Gitlab integration ===

			TBA

	== Kernel specific settings ==		== Kernel specific settings ==

Darkfader: /* Alternatives */

2026-03-28T16:31:00Z

Alternatives

← Older revision		Revision as of 16:31, 28 March 2026
Line 375:		Line 375:
	https://github.com/icecc/icecream		https://github.com/icecc/icecream

	It appears 'maybe better' but hard to tell. There's no mention if maybe SUSE's OBS uses it or something. Without more knowledge of their use I don't know how big a benefit will come from switching.		It appears 'maybe better' but hard to tell. There's no mention if maybe SUSE's OBS uses it or something. Without more knowledge of their use I don't know how big a benefit will come from switching. At least you'd wanna know they have a higher commitment to maintenance than the understaffed distcc 'team' of current.