On 10/30/25 12:23 AM, Lars Tunkrans wrote:
What is the size of RAM in your machine. ?
When building Chrome / ungoogled-chrome on 15-current at
some time this spring, About 18 GB
RAM was used on a 64 GB machine. And then you need RAM for
the ZFS ARC cache., if you have the source code on ZFS, Therefor you
need 32 GB RAM to build Chrome efficiently.
I think I remember that using Link Time Optimization option also
took a long time at the end of the build.
The machine has 32GB RAM, chromium is in TMPFS_BLACKLIST.
There are some GBs swap used but that has never been a performance issue
so far. If memory was the problem, I don't think setting
vfs.vnode.param.can_skip_requeue=1 would improve the situation.
I'm still looking for a simpler setup to reproduce the situation. It's
hard to test if I have to wait several hours until the problem manifests.
I'm not sure if it happens at a specific point of the chromium build.
This time I noticed the issue at around 40K (of about 52K total) files
built.
It might has nothing to do with the specific commands in the build but
just be a problem that gets worse over time.
