From Newsgroup: muc.lists.freebsd.stable

There have been reports of rather large time differences for
14.4-RELEASE vs. 14.3-RELEASE --as well as prior reports referencing 14.3-RELEASE vs. 15.0-RELEASE. This is just a report of from-scratch
building of a particular set of port-packages on a fairly fast machine
(amd64 7950X3D) for each of those.

Upstream based context installed/used:

pkgbase GENERIC-NODEBUG main boot kernel
pkgbase debug main boot world (/etc/malloc.conf -> junk:false)

pkgbase 15.0-RELEASE poudriere-devel jail world.
ftp-archive 14.4-RELEASE poudriere-devel jail world.
ftp-archive 14.3-RELEASE poudriere-devel jail world.

(So: None are my builds.)

# poudriere jail -l
JAILNAME VERSION OSVERSION ARCH METHOD
TIMESTAMP PATH
release14p3-amd64 14.3-RELEASE-p10 1403000 amd64 ftp-archive 2026-04-14 18:00:43 /usr/local/poudriere/jails/release14p3-amd64
. . .
release14-amd64 14.4-RELEASE-p1 1404000 amd64 ftp-archive 2026-04-14 18:02:42 /usr/local/poudriere/jails/release14-amd64
. . .
release-amd64 15.0-RELEASE-p5 1500068 amd64 pkgbase
2026-04-17 16:09:49 /usr/local/poudriere/jails/release-amd64
. . .

ZFS context.


As for the 7950X3D build times:
(maximum ratio: 02:29:18/02:04:06 approx.= 1.2)

15.0-RELEASE (run third) took the most time:
(1 less built than for 14.*-RELEASE : 687 vs. 688)

[02:29:20] [release-amd64-alt] [2026-04-18_08h47m48s] [committing] Time: 02:29:18
Queued: 688 Inspected: 0 Ignored: 0 Built: 687 Failed: 1
Skipped: 0 Fetched: 0 Remaining: 0


14.4-RELEASE (run second) took the middle amount of time:

[02:24:13] [release14-amd64-alt] [2026-04-18_06h23m35s] [committing]
Time: 02:24:11
Queued: 689 Inspected: 0 Ignored: 0 Built: 688 Failed: 1
Skipped: 0 Fetched: 0 Remaining: 0


14.3-RELEASE (run first) took the least time, by a bigger amount:

[02:04:06] [release14p3-amd64-alt] [2026-04-17_21h53m02s] [committing]
Time: 02:04:05
Queued: 689 Inspected: 0 Ignored: 0 Built: 688 Failed: 1
Skipped: 0 Fetched: 0 Remaining: 0


So, in the 79050X3D's context, 14.4-RELEASE and 15.0-RELEASE are similar
in how much more time they take than 14.3-RELEASE. This suggests that
the biggest difference makers are probably just differences between 14.4
and 14.3 that are also in 15.0, not any extra differences 15.0 may have
vs. 14.3.

I've never managed to replicate the much larger 14.4 vs. 14.3 time
ratios that have been reported.


For reference:

# ~/fbsd-based-on-what-commit.sh -C /usr/ports-alt/
b96a271bbc08 (HEAD -> main, freebsd/main, freebsd/HEAD) www/firefox:
update to 150.0 (rc1)
Author: Christoph Moench-Tegeder <cmt@FreeBSD.org>
Commit: Christoph Moench-Tegeder <cmt@FreeBSD.org>
CommitDate: 2026-04-16 17:51:06 +0000
branch: main
merge-base: b96a271bbc0820a058e89001c9ac2309cbf8a60d
merge-base: CommitDate: 2026-04-16 17:51:06 +0000
n742012 (--first-parent --count for merge-base)

/usr/ports-alt/ is a clean tree.

My /usr/local/etc/poudriere.d/poudriere.conf is involved and likely unusual.

15.0-RELEASE has a newer jemalloc.

The SWAP space was never put to use. The 1min load average got to be as
high as: 178.27, the 5min: 125.95, the 15min: 76.14 . (Sampled every top
update by a patched top.) There are 16 SMT cores, so 32 FreeBSD cpus.
Implicit 32 builders allowed in parallel. ALLOW_MAKE_JOBS=yes was in
use but no MAKE_JOBS_NUMBER_LIMIT or the like was in use, so: implicit
32 per builder allowed. The media in use was (is): PCIe Optane 1.4 TB.



SIDE NOTE:
A different example, aarch64 Windows Dev Kit 2023 context, USB3 media,
UFS, only around 273 port-packages queued/built . . .


15.0-RELEASE:

UPDATE 15.0-RELEASE NOTES LATER, given how long the WinDevKit2023 builds
take.


14.4-RELEASE (run first):

[09:12:00] [release14-aarch64-alt] [2026-04-17_22h10m56s] [committing]
Time: 09:11:36
Queued: 273 Inspected: 0 Ignored: 0 Built: 273 Failed: 0
Skipped: 0 Fetched: 0 Remaining: 0


14.3-RELEASE:

UPDATE 14.3-RELEASE NOTES LATER, given how long the WinDevKit2023 builds
take.
--
===
Mark Millard
marklmi at yahoo.com



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

On 4/18/26 12:26, Mark Millard wrote:

There have been reports of rather large time differences for
14.4-RELEASE vs. 14.3-RELEASE --as well as prior reports referencing 14.3-RELEASE vs. 15.0-RELEASE. This is just a report of from-scratch building of a particular set of port-packages on a fairly fast machine
(amd64 7950X3D) for each of those.

Upstream based context installed/used:

pkgbase GENERIC-NODEBUG main boot kernel
pkgbase debug main boot world (/etc/malloc.conf -> junk:false)

pkgbase 15.0-RELEASE poudriere-devel jail world.
ftp-archive 14.4-RELEASE poudriere-devel jail world.
ftp-archive 14.3-RELEASE poudriere-devel jail world.

(So: None are my builds.)

# poudriere jail -l
JAILNAME VERSION OSVERSION ARCH METHOD
TIMESTAMP PATH
release14p3-amd64 14.3-RELEASE-p10 1403000 amd64 ftp-archive 2026-04-14 18:00:43 /usr/local/poudriere/jails/release14p3-amd64
. . .
release14-amd64 14.4-RELEASE-p1 1404000 amd64 ftp-archive 2026-04-14 18:02:42 /usr/local/poudriere/jails/release14-amd64
. . .
release-amd64 15.0-RELEASE-p5 1500068 amd64 pkgbase 2026-04-17 16:09:49 /usr/local/poudriere/jails/release-amd64
. . .

ZFS context.

As for the 7950X3D build times:
(maximum ratio: 02:29:18/02:04:06 approx.= 1.2)

15.0-RELEASE (run third) took the most time:
(1 less built than for 14.*-RELEASE : 687 vs. 688)

[02:29:20] [release-amd64-alt] [2026-04-18_08h47m48s] [committing] Time: 02:29:18
Queued: 688 Inspected: 0 Ignored: 0 Built: 687 Failed: 1
Skipped: 0 Fetched: 0 Remaining: 0

14.4-RELEASE (run second) took the middle amount of time:

[02:24:13] [release14-amd64-alt] [2026-04-18_06h23m35s] [committing]
Time: 02:24:11
Queued: 689 Inspected: 0 Ignored: 0 Built: 688 Failed: 1
Skipped: 0 Fetched: 0 Remaining: 0

14.3-RELEASE (run first) took the least time, by a bigger amount:

[02:04:06] [release14p3-amd64-alt] [2026-04-17_21h53m02s] [committing]
Time: 02:04:05
Queued: 689 Inspected: 0 Ignored: 0 Built: 688 Failed: 1
Skipped: 0 Fetched: 0 Remaining: 0

So, in the 79050X3D's context, 14.4-RELEASE and 15.0-RELEASE are similar
in how much more time they take than 14.3-RELEASE. This suggests that
the biggest difference makers are probably just differences between 14.4
and 14.3 that are also in 15.0, not any extra differences 15.0 may have
vs. 14.3.

I've never managed to replicate the much larger 14.4 vs. 14.3 time
ratios that have been reported.

For reference:

# ~/fbsd-based-on-what-commit.sh -C /usr/ports-alt/
b96a271bbc08 (HEAD -> main, freebsd/main, freebsd/HEAD) www/firefox:
update to 150.0 (rc1)
Author: Christoph Moench-Tegeder <cmt@FreeBSD.org>
Commit: Christoph Moench-Tegeder <cmt@FreeBSD.org>
CommitDate: 2026-04-16 17:51:06 +0000
branch: main
merge-base: b96a271bbc0820a058e89001c9ac2309cbf8a60d
merge-base: CommitDate: 2026-04-16 17:51:06 +0000
n742012 (--first-parent --count for merge-base)

/usr/ports-alt/ is a clean tree.

My /usr/local/etc/poudriere.d/poudriere.conf is involved and likely unusual.

15.0-RELEASE has a newer jemalloc.

The SWAP space was never put to use. The 1min load average got to be as
high as: 178.27, the 5min: 125.95, the 15min: 76.14 . (Sampled every top update by a patched top.) There are 16 SMT cores, so 32 FreeBSD cpus. Implicit 32 builders allowed in parallel. ALLOW_MAKE_JOBS=yes was in
use but no MAKE_JOBS_NUMBER_LIMIT or the like was in use, so: implicit
32 per builder allowed. The media in use was (is): PCIe Optane 1.4 TB.

SIDE NOTE:
A different example, aarch64 Windows Dev Kit 2023 context, USB3 media,
UFS, only around 273 port-packages queued/built . . .

15.0-RELEASE:

This was run third and the in-process from-scratch build queued 271 (2
less than under 14.*). It will be many hours before there is a final
"time" for this.

UPDATE 15.0-RELEASE NOTES LATER, given how long the WinDevKit2023 builds take.

14.4-RELEASE (run first):

[09:12:00] [release14-aarch64-alt] [2026-04-17_22h10m56s] [committing]
Time: 09:11:36
Queued: 273 Inspected: 0 Ignored: 0 Built: 273 Failed: 0
Skipped: 0 Fetched: 0 Remaining: 0

14.3-RELEASE:

This was run second.

UPDATE 14.3-RELEASE NOTES LATER, given how long the WinDevKit2023 builds take.

[08:11:31] [release14p3-aarch64-alt] [2026-04-18_07h22m56s] [committing]
Time: 08:10:58
Queued: 273 Inspected: 0 Ignored: 0 Built: 273 Failed: 0
Skipped: 0 Fetched: 0 Remaining: 0

Note: 09:11:36/08:10:58 approx.= 1.12



--
===
Mark Millard
marklmi at yahoo.com


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

Mark Millard wrote on Sat, 18 Apr 2026 21:26:10 +0200 (CEST):

There have been reports of rather large time differences for
14.4-RELEASE vs. 14.3-RELEASE --as well as prior reports referencing 14.3-RELEASE vs. 15.0-RELEASE.

PR 287447 perhaps?

14.3's cc is statically linked against libllvm etc, while 14.4 and 15.0 have private shared libraries - boils down to 2e47f35be5dc.

Running on a system with WITH_LLVM_LINK_STATIC_LIBRARIES has significantly reduced build times for me.

Kind regards
Helge


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

On 4/19/26 09:22, Mark Millard wrote:

On 4/19/26 01:15, Helge Oldach wrote:

Mark Millard wrote on Sat, 18 Apr 2026 21:26:10 +0200 (CEST):

There have been reports of rather large time differences for
14.4-RELEASE vs. 14.3-RELEASE --as well as prior reports referencing
14.3-RELEASE vs. 15.0-RELEASE.

PR 287447 perhaps?

14.3's cc is statically linked against libllvm etc, while 14.4 and 15.0 have private shared libraries - boils down to 2e47f35be5dc.

My Windows Dev Kit 2023 test does not as well fit with that being the explanation of most everything in that context: it got a noticeably more significant difference between 15.0 and 14.4 for the time ratios vs.
14.3 compared to the 7950X3D figures:

7950X3D 15.0 and 14.4 vs. 14.3 ratios:
15.0: 02:29:18/02:04:06 approx.= 1.20
14.4: 02:24:11/02:04:05 approx.= 1.16

WinDevKit2023 15.0 and 14.4 vs. 14.3 ratios:
15.0: 09:58:30/08:10:58 approx.= 1.22
14.4: 09:11:36/08:10:58 approx.= 1.12
(So: not as close.)

Of course, since I built a notably smaller subset of the port-packages
on the WinDevKit2023 in order to avoid much longer build time frames,
the workload change could be significantly contributing. I do not have
an analysis of the workload differences to use to make judgments with
for that.

To deal with the above issue, I've started a from-scratch build sequence
of the same subset of port-packages on the 7950X3D. That should make for
time ratios that are more reasonable to compare/contrast.

I happened to have set the sequence to 15.0 then 14.4 then 14.3 .

[I've also corrected my prior inclusion of freebsd-current@ to be
freebsd-arm@ instead.]

More interesting will be when future from-scratch official port-package builds on ampere4 and ampere5 (aarch64 contexts that closely match) are
also available for comparison to the 14.3 and 15.0 overall times on
those machines.

Running on a system with WITH_LLVM_LINK_STATIC_LIBRARIES has significantly reduced build times for me.

My personal builds of other chroots/poudriere-devel jails use that --but
for WinDevKit2023 I also build the FreeBSD versions as targeted to Cortext-A76 (WindDevKit2023 and RPi5 compatible). I also build personal kernels that I can boot that are targeted to Cortext-A76. I use the same upstream pkgbase boot world no matter which boot kernel is in use.

I have yet to update my personal builds of such to do tests with.

Kind regards
Helge

--
===
Mark Millard
marklmi at yahoo.com


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21f-Linux NewsLink 1.2