On Wed, 27 May 2026 18:01:51 +0200 Kurt Jaeger <[email protected]> wrote:
> Hi! > > > I do believe they're talking about outsourcing the build process and > > distributing amongst resources. Like a hive or a chain where distributed > > systems would be used to build pieces (of the software) and collaborate > > back (which does have potential to be a great resource.) But, the Poudriere > > system does not support this currently. Perhaps in the future? > > Again: The critical path for a rebuild of the ports tree is > the longest compile-time path in the dependency tree. > > If you throw more CPUs at the problem, the longest path will > not become shorter. Only if you use CPUs with higher GHz rate. > > -- > [email protected] +49 171 3101372 Now what ? What I read from this thread is a bit different. Aren't others talking about "Can't be a build for single huge port to be built distributed?" rather thand "Can't we build more ports at once?"? If, for example, building devel/electron41 eats up full 256 cores in 256T256 (no HTT or alike) physical CPU with 100% loads per core, and more cores helps (i.e., assuming the build for www/electron41 can be distributed upto 32767 cores to scale), which is at least currently unavailable as single computer, distributed builds of "single port" can benefit, technically. But the breakthrough may be hard to implement. Note that even in this kind of cases, using multiple computer with 65536T65536 CPU (unrealistic for now!) for www/electron41 is just a mess as you said. Regards. -- Tomoaki AOKI <[email protected]>
