Dports, Dsynth and Options

[Matthew Dillon]

Excellent!  Yes, you definitely need a machine like that to get a decent
build rate.  The packages get larger and larger as the build goes on (since
the dependencies have to be built first and those are smaller packages).  I
usually calculate roughly 1GB or so per compile worst-case... which is
about what those huge C++ programs start to eat up near the end of the
build.  Plus all the working files for the builds are in tmpfs.

So just monitor the wear on your SSD.  We have SSD based swap on all of our
builders and the wear rate is totally reasonable.  As long as a good middle
of the road Number_of_builders and Max_jobs_per_builder config is
specified, Dsynth does a pretty good job adjusting the concurrency based on
its understanding of memory requirements and swap use.   You can see the
memory/load statistics in the 00_last_results.log as it is building.  'tail
-f 00_last_results | fgrep Load='.

DSynth is also fairly sophisticated in how it selects packages to build.
 It will try mixing small and large packages together to keep things
flowing (within the limitations of the dependency tree) and to avoid, as
much as possible, delaying large packages to the end.

-Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20230202/f1250953/attachment-0002.htm>