A re-occurring question is why chromium is slow to build.
Doing a build of Ungoogled-Chromium on a large enough Desktop PC.
Total build time 2 Hours and 3 minutes.
CPU Intel Core Ultra 9 285K 24 cores without hyperthreading.
GPU not relevant for this build-run : Nvidia RTXPRO 4000.
Memory 64 GB DDR5 5600 DUAL Bus ( 2x 32 GB )
Storage 1 TB M.2 Gen5 NVME.
Vendor: Shuttle SB860R8 Barebone chassie.
FreeBSD 15.1 Stable AMD64
Desktop Manager in use while doing build: KDE/Plasma 6.6.4
FileSystem OpenZFS
Memory Allocation during run.
ZFS ARC Cahche up to 30 GB ( not limited )
Active Memory: up to 28 GB
Inactive memory: up to 8.5 GB
Allocated SWAP: up to 500 MB. ( Increases as run progress. )
Resident sizes of up to 2.5 GB per compile task.
As the build consumes up to 2.5 GB resident memory per compile task/thread at its most hungry state.
And Memory is needed for the filesystem , if this build is attempted with 16 GB RAM only ,
you can run 4 or 5 compile threads and limit ZFS to a 5 GB Arc. looking at a completion time of maybe 8 - 10 hours.
With 32 GB Ram , Maybe 10 compile jobs and 10 GB ZFS ARC running for 5 Hours.
A Machine with 16 GB and default 2 GB SWAP. will run out of Virtual memory, unless its restricted in number of build tasks and
Filesystem cache (ZFS ARC) usage.
Doing a build of Ungoogled-Chromium on a large enough Desktop PC.
Total build time 2 Hours and 3 minutes.
CPU Intel Core Ultra 9 285K 24 cores without hyperthreading.
GPU not relevant for this build-run : Nvidia RTXPRO 4000.
Memory 64 GB DDR5 5600 DUAL Bus ( 2x 32 GB )
Storage 1 TB M.2 Gen5 NVME.
Vendor: Shuttle SB860R8 Barebone chassie.
FreeBSD 15.1 Stable AMD64
Desktop Manager in use while doing build: KDE/Plasma 6.6.4
FileSystem OpenZFS
Memory Allocation during run.
ZFS ARC Cahche up to 30 GB ( not limited )
Active Memory: up to 28 GB
Inactive memory: up to 8.5 GB
Allocated SWAP: up to 500 MB. ( Increases as run progress. )
Resident sizes of up to 2.5 GB per compile task.
As the build consumes up to 2.5 GB resident memory per compile task/thread at its most hungry state.
And Memory is needed for the filesystem , if this build is attempted with 16 GB RAM only ,
you can run 4 or 5 compile threads and limit ZFS to a 5 GB Arc. looking at a completion time of maybe 8 - 10 hours.
With 32 GB Ram , Maybe 10 compile jobs and 10 GB ZFS ARC running for 5 Hours.
A Machine with 16 GB and default 2 GB SWAP. will run out of Virtual memory, unless its restricted in number of build tasks and
Filesystem cache (ZFS ARC) usage.
