On Tue, May 26, 2026 at 07:29:49AM +0200, Kurt Jaeger wrote:
The ports tree is a dependency tree. To target the fastest way for
upgrades would require to rebuild if a dependency changes
and to optimise the longest path, compile-time-wise.
Finding that longest path would be interesting.
Some elements in that path might have problems with parallel
compilation (MAKE_JOBS_UNSAFE option). Fixing those elements
might help.
Because this longest path is not subject to parallelization, I'm
not sure it's easily achievable.
It is subject to CPU takt rate optimization, therefore using faster
CPUs might help as well. And large TMPFS.
I don't think I articulated what I meant thoroughly.
By distributed I mean something like folding@home where a user
would get a slice of work and process/upload it.
I have absolutely *no idea* if this is even feasible. Just spitballing
what came into my head when thinking about how to share the load.
I mean just 1000 subscribers crunching on half power would be
an immense resource, compared to just a few machines doing it.
--
