| View previous topic :: View next topic |
| Author |
Message |
hariskar
Apprentice
Joined: 29 Jan 2017
Posts: 168
|
 Posted: Fri Jan 27, 2023 2:39 pm Post subject: Chromium build time 36 hours?? |
 |
|
I just installed gentoo, compiled Chromium in about 36 hours...
Is my PC extremely weak and outdated? Do I have wrong settings?
RAM is 16GB.
Do I have to update cpu, mb, ram?
Thank you!
| Code: | ~ $ sudo qlop -tH www-client/chromium
2023-01-25T20:35:16 >>> www-client/chromium: 1 day, 12 hours, 13 minutes, 5 seconds |
| Code: | ~ $ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 39 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Vendor ID: GenuineIntel
Model name: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
CPU family: 6
Model: 60
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
Stepping: 3
CPU(s) scaling MHz: 22%
CPU max MHz: 3700.0000
CPU min MHz: 800.0000
BogoMIPS: 6600.13
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulq
dq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm abm cpuid_fault invpcid_single pti tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1
avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts
Virtualization features:
Virtualization: VT-x
Caches (sum of all):
L1d: 128 KiB (4 instances)
L1i: 128 KiB (4 instances)
L2: 1 MiB (4 instances)
L3: 6 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-3
Vulnerabilities:
Itlb multihit: Processor vulnerable
L1tf: Mitigation; PTE Inversion
Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Meltdown: Mitigation; PTI
Mmio stale data: Unknown: No mitigations
Retbleed: Not affected
Spec store bypass: Vulnerable
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected
Srbds: Vulnerable: No microcode
Tsx async abort: Not affected |
| Code: | ~ $ cat /etc/portage/make.conf
# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
COMMON_FLAGS="-march=haswell -O2 -pipe"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"
USE="X elogind"
# NOTE: This stage was built with the bindist Use flag enabled
# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C
MAKEOPTS="-j4"
GRUB_PLATFORMS="efi-64"
VIDEO_CARDS="nouveau" |
Last edited by hariskar on Fri Jan 27, 2023 2:54 pm; edited 1 time in total |
|
| Back to top |
|
 |
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 30976
Location: here
|
| Posted: Fri Jan 27, 2023 2:47 pm Post subject: |
|
|
In my i7-4930K 32GB and makeopts -j12 latest chromium I compiled (100.0.4896.75) took 5:39:33.
After that I installed www-client/chromium-bin the precompiled version.
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
hariskar
Apprentice
Joined: 29 Jan 2017
Posts: 168
|
| Posted: Fri Jan 27, 2023 2:53 pm Post subject: |
|
|
| fedeliallalinea wrote: | In my i7-4930K 32GB and makeopts -j12 latest chromium I compiled (100.0.4896.75) took 5:39:33.
After that I installed www-client/chromium-bin the precompiled version. |
So, it is normal for my PC to make that long..
I don't want to install bin, 5-6 hours would be OK for me, so I guess I have to update my hardware..
Thank you! |
|
| Back to top |
|
|
CooSee
Veteran
Joined: 20 Nov 2004
Posts: 1455
Location: Earth
|
| Posted: Fri Jan 27, 2023 3:02 pm Post subject: |
|
|
on my system with Xeon-E3-1245v5 + 32GB ram + ccache - SMT enabled.
| Code: | Sat Jan 14 04:23:09 2023 >>> www-client/ungoogled-chromium-109.0.5414.74_p1
merge time: 7 hours, 5 minutes and 10 seconds. |
and yesterdays update
| Code: | Fri Jan 27 04:26:09 2023 >>> www-client/ungoogled-chromium-109.0.5414.119_p1
merge time: 3 hours, 56 minutes and 22 seconds. |
_________________
" Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier " |
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1695
|
| Posted: Fri Jan 27, 2023 3:10 pm Post subject: |
|
|
| hariskar wrote: | | fedeliallalinea wrote: | In my i7-4930K 32GB and makeopts -j12 latest chromium I compiled (100.0.4896.75) took 5:39:33.
After that I installed www-client/chromium-bin the precompiled version. |
So, it is normal for my PC to make that long..
I don't want to install bin, 5-6 hours would be OK for me, so I guess I have to update my hardware..
Thank you! |
Note that qlop is a simple log parser. If there is any sleep/hibernate involved, it will skew the output.
The log will only contain when it starts and stops and does not take into account other factors. |
|
| Back to top |
|
|
hariskar
Apprentice
Joined: 29 Jan 2017
Posts: 168
|
| Posted: Fri Jan 27, 2023 3:51 pm Post subject: |
|
|
Thank you for replies!
I try with ccache to see if there is a significant improvement.. |
|
| Back to top |
|
|
logrusx
Veteran
Joined: 22 Feb 2018
Posts: 1589
|
| Posted: Fri Jan 27, 2023 4:47 pm Post subject: |
|
|
| hariskar wrote: | Thank you for replies!
I try with ccache to see if there is a significant improvement.. |
There won't be. Instead, it'll likely bring unexpected compilation errors. I'm surprised it takes so long. It's comparable to the Q6600 with 8GB of RAM I used to run Gentoo on an year ago. Maybe try to swap your CPU with one that supports HT.
I don't know why you're reluctant to use the bin version. Despite I have a Ryzen 7 5800H I moved to binary packages for libreoffice, rust, firefox, chroimum (ungoogled chromium from pf4public overlay). Back when I used the Q6600, I used to enable LTO on ungoogled-chromium which brought some improvement in the performance, but I'm not sure it's worth given the long compilation times. It took ~40 hours for me back then.
Best Regards,
Georgi |
|
| Back to top |
|
|
hariskar
Apprentice
Joined: 29 Jan 2017
Posts: 168
|
| Posted: Fri Jan 27, 2023 5:02 pm Post subject: |
|
|
| logrusx wrote: | | Maybe try to swap your CPU with one that supports HT |
The motherboard is old (socket 1150), so I guess I have to swap also motherboard and maybe RAM.. |
|
| Back to top |
|
|
CooSee
Veteran
Joined: 20 Nov 2004
Posts: 1455
Location: Earth
|
| Posted: Fri Jan 27, 2023 5:41 pm Post subject: |
|
|
| Quote: | | There won't be. Instead, it'll likely bring unexpected compilation errors |
of course, be aware!
compiling time depends on many things - CPU - disk speed - kernel?!, etc.
i have a fast NVME and ccache is on separate fast NVME - no SWAP.
without ccache, chromium take more than 8 hours, while browsing with FF and watching stream with chromium.
_________________
" Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier " |
|
| Back to top |
|
|
Chiitoo
Administrator
Joined: 28 Feb 2010
Posts: 2587
Location: Here and Away Again
|
| Posted: Sat Jan 28, 2023 12:50 am Post subject: |
|
|
Yeah, ccache will not do much when compiling a new version, but it should definitely help with rebuilds.
Well, I generally only build Chromium in Qt WebEngine, which luckily still has the 'jumbo-build' option being maintained, so I don't really have experience on plain Chromium itself.
Out of curiosity, with a Ryzen 7 1700 using 14 of the available 16 threads (the older builds are with a 6-core Phenom by the by):
| Code: | Thu May 8 01:39:04 2014 >>> www-client/chromium-35.0.1916.86
merge time: 42 minutes and 38 seconds.
Mon Mar 16 09:00:10 2015 >>> www-client/chromium-41.0.2272.76
merge time: 1 hour, 27 minutes and 29 seconds.
Sat Jan 28 02:31:53 2023 >>> www-client/chromium-110.0.5481.38
merge time: 6 hours, 44 minutes and 37 seconds. |
Here's qtwebengine-6.4.2[jumbo-build] (which didn't get a 100% full use of the 16 threads either, but I did not limit it to 14):
| Code: | Thu Jan 5 18:11:52 2023 >>> dev-qt/qtwebengine-6.4.2
merge time: 2 hours, 32 minutes and 23 seconds. |
_________________
Kindest of regardses. |
|
| Back to top |
|
|
hariskar
Apprentice
Joined: 29 Jan 2017
Posts: 168
|
| Posted: Sat Jan 28, 2023 3:27 am Post subject: |
|
|
| Thank you, I suppose compilation time of ungoogled-chromium should be about the same? |
|
| Back to top |
|
|
logrusx
Veteran
Joined: 22 Feb 2018
Posts: 1589
|
| Posted: Sat Jan 28, 2023 1:37 pm Post subject: |
|
|
| hariskar wrote: | | Thank you, I suppose compilation time of ungoogled-chromium should be about the same? |
Yes, but you could enable LTO, which in my case gave some performance benefits. There is ungoogled-chromium-bin too.
Best Regards,
Georgi |
|
| Back to top |
|
|
hariskar
Apprentice
Joined: 29 Jan 2017
Posts: 168
|
| Posted: Tue Mar 28, 2023 2:52 pm Post subject: |
|
|
After I changed to (entry level) Ryzen 5 5600G compilation time of Chromium dropped to 4 hours (it was 36-40 with previous hardware!
4 hours is a totally acceptable time!
Thanks again for replies! |
|
| Back to top |
|
|
stefan11111
l33t
Joined: 29 Jan 2023
Posts: 922
Location: Romania
|
| Posted: Tue Mar 28, 2023 3:02 pm Post subject: |
|
|
| hariskar wrote: | After I changed to (entry level) Ryzen 5 5600G compilation time of Chromium dropped to 4 hours (it was 36-40 with previous hardware!
4 hours is a totally acceptable time!
Thanks again for replies! |
That is a modern cpu, only 2 years old.
I don't use chromium, but I think that 4 hours is a very long time for that cpu.
On an i5 7400, librewolf with lto and pgo takes 2.5 hours to compile.
Those flags double the compile time.
| Code: | | 2023-03-25T00:29:10 >>> www-client/librewolf: 2:36:14 |
If my 6 year old cpu with 4 cores and 4 threads can do this, surely yours can do better.
_________________
My overlay: https://github.com/stefan11111/stefan_overlay
INSTALL_MASK="/etc/systemd /lib/systemd /usr/lib/systemd /usr/lib/modules-load.d *udev* /usr/lib/tmpfiles.d *tmpfiles* /var/lib/dbus /usr/bin/gdbus /lib/udev" |
|
| Back to top |
|
|
hariskar
Apprentice
Joined: 29 Jan 2017
Posts: 168
|
| Posted: Tue Mar 28, 2023 3:12 pm Post subject: |
|
|
| Firefox compiled in about 4 hours with my old cpu. Chromium is much more demanding... |
|
| Back to top |
|
|
stefan11111
l33t
Joined: 29 Jan 2023
Posts: 922
Location: Romania
|
| Posted: Tue Mar 28, 2023 3:30 pm Post subject: |
|
|
| hariskar wrote: | | Firefox compiled in about 4 hours with my old cpu. Chromium is much more demanding... |
What kind of bloat do they add to chromium?
_________________
My overlay: https://github.com/stefan11111/stefan_overlay
INSTALL_MASK="/etc/systemd /lib/systemd /usr/lib/systemd /usr/lib/modules-load.d *udev* /usr/lib/tmpfiles.d *tmpfiles* /var/lib/dbus /usr/bin/gdbus /lib/udev" |
|
| Back to top |
|
|
logrusx
Veteran
Joined: 22 Feb 2018
Posts: 1589
|
| Posted: Tue Mar 28, 2023 6:15 pm Post subject: Re: Chromium build time 36 hours?? |
|
|
| hariskar wrote: | I just installed gentoo, compiled Chromium in about 36 hours...
Is my PC extremely weak and outdated? Do I have wrong settings?
RAM is 16GB.
Do I have to update cpu, mb, ram?
Thank you!
| Code: | ~ $ sudo qlop -tH www-client/chromium
2023-01-25T20:35:16 >>> www-client/chromium: 1 day, 12 hours, 13 minutes, 5 seconds |
| Code: | ~ $ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 39 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Vendor ID: GenuineIntel
Model name: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
CPU family: 6
Model: 60
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
Stepping: 3
CPU(s) scaling MHz: 22%
CPU max MHz: 3700.0000
CPU min MHz: 800.0000
BogoMIPS: 6600.13
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulq
dq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm abm cpuid_fault invpcid_single pti tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1
avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts
Virtualization features:
Virtualization: VT-x
Caches (sum of all):
L1d: 128 KiB (4 instances)
L1i: 128 KiB (4 instances)
L2: 1 MiB (4 instances)
L3: 6 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-3
Vulnerabilities:
Itlb multihit: Processor vulnerable
L1tf: Mitigation; PTE Inversion
Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Meltdown: Mitigation; PTI
Mmio stale data: Unknown: No mitigations
Retbleed: Not affected
Spec store bypass: Vulnerable
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected
Srbds: Vulnerable: No microcode
Tsx async abort: Not affected |
| Code: | ~ $ cat /etc/portage/make.conf
# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
COMMON_FLAGS="-march=haswell -O2 -pipe"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"
USE="X elogind"
# NOTE: This stage was built with the bindist Use flag enabled
# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C
MAKEOPTS="-j4"
GRUB_PLATFORMS="efi-64"
VIDEO_CARDS="nouveau" |
|
RAM is OK for 8 threads, but your CPU only has 4 of them. The build time is comparable to my old Q6600 with 4 cores/4threads and 8Gb RAM. If your MB supports Hiperthreading or 8 core CPU without HT, that could be an easy upgrade. However I don't remember Intel desktop CPU's from that generation supporting HT.
Chromium used to compile for shorter times when they used the jumboo build which merged header files, but now they removed it and we're stuck with loading and compiling countless header files over and over again. Pre-compiled headers is not supported, neither it works, at least for GCC afar.
Best Regards,
Georgi |
|
| Back to top |
|
|
logrusx
Veteran
Joined: 22 Feb 2018
Posts: 1589
|
| Posted: Tue Mar 28, 2023 6:18 pm Post subject: |
|
|
| CooSee wrote: | on my system with Xeon-E3-1245v5 + 32GB ram + ccache - SMT enabled.
| Code: | Sat Jan 14 04:23:09 2023 >>> www-client/ungoogled-chromium-109.0.5414.74_p1
merge time: 7 hours, 5 minutes and 10 seconds. |
and yesterdays update
| Code: | Fri Jan 27 04:26:09 2023 >>> www-client/ungoogled-chromium-109.0.5414.119_p1
merge time: 3 hours, 56 minutes and 22 seconds. |
|
That's a lucky run. Ccache has proven to be more of a problem rather than a solution. It doesn't benefit compile times even between minor versions as changes have too wide of an impact.
Best Regards,
Georgi |
|
| Back to top |
|
|
logrusx
Veteran
Joined: 22 Feb 2018
Posts: 1589
|
| Posted: Tue Mar 28, 2023 6:20 pm Post subject: |
|
|
| hariskar wrote: | Thank you for replies!
I try with ccache to see if there is a significant improvement.. |
There won't be and in your case a single failure will wipe out all the benefit. Ccache is known to cause build failures. Better look for an 8thread or 8core CPU. There's also chromium bin version as well as ungoogled chromium bin, if you don't like the original. And I think there's a binary package of chromium produced by the experimental Gentoo binhost.
Best Regards,
Georgi |
|
| Back to top |
|
|
hariskar
Apprentice
Joined: 29 Jan 2017
Posts: 168
|
| Posted: Tue Mar 28, 2023 6:29 pm Post subject: |
|
|
After I changed to (entry level) Ryzen 5 5600G compilation time of Chromium dropped to 4 hours (it was 36-40 with previous hardware!
4 hours is a totally acceptable time! |
|
| Back to top |
|
|
CooSee
Veteran
Joined: 20 Nov 2004
Posts: 1455
Location: Earth
|
| Posted: Tue Mar 28, 2023 8:02 pm Post subject: |
|
|
| Quote: | | That's a lucky run. Ccache has proven to be more of a problem rather than a solution. It doesn't benefit compile times even between minor versions as changes have too wide of an impact. |
yes, you're right 
sometimes it helps, sometimes not - here are some examples including todays merge:
| Code: | Wed Jan 18 00:55:14 2023 >>> www-client/ungoogled-chromium-109.0.5414.74_p1
merge time: 2 hours, 25 minutes and 27 seconds.
Thu Jan 19 00:16:33 2023 >>> www-client/ungoogled-chromium-109.0.5414.74_p1
merge time: 24 minutes and 27 seconds.
Fri Jan 27 04:26:09 2023 >>> www-client/ungoogled-chromium-109.0.5414.119_p1
merge time: 3 hours, 56 minutes and 22 seconds.
Thu Feb 9 19:03:34 2023 >>> www-client/ungoogled-chromium-109.0.5414.119_p1
merge time: 7 hours, 9 minutes and 50 seconds.
Fri Feb 10 19:31:03 2023 >>> www-client/ungoogled-chromium-110.0.5481.77_p1
merge time: 2 hours, 50 minutes and 10 seconds.
Sun Feb 19 01:13:09 2023 >>> www-client/ungoogled-chromium-110.0.5481.100_p1
merge time: 1 hour, 44 minutes and 48 seconds.
Wed Feb 22 14:16:08 2023 >>> www-client/ungoogled-chromium-110.0.5481.100_p1
merge time: 21 minutes and 52 seconds.
Fri Feb 24 17:55:16 2023 >>> www-client/ungoogled-chromium-110.0.5481.177_p1
merge time: 3 hours, 35 minutes and 50 seconds.
Mon Mar 13 02:55:52 2023 >>> www-client/ungoogled-chromium-111.0.5563.64_p1
merge time: 4 hours, 42 minutes and 13 seconds.
Wed Mar 15 14:27:00 2023 >>> www-client/ungoogled-chromium-111.0.5563.64_p1
merge time: 1 hour, 5 minutes and 34 seconds.
Sat Mar 25 19:19:03 2023 >>> www-client/ungoogled-chromium-111.0.5563.110_p1
merge time: 1 hour, 20 minutes and 42 seconds.
Tue Mar 28 21:41:56 2023 >>> www-client/ungoogled-chromium-111.0.5563.146_p1
merge time: 7 hours, 53 minutes and 4 seconds. |
_________________
" Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier " |
|
| Back to top |
|
|
ukky
Tux's lil' helper
Joined: 26 Feb 2023
Posts: 109
Location: Montreal, Canada
|
| Posted: Wed Mar 29, 2023 2:48 am Post subject: |
|
|
It seems like when compiling Chromium it really matters how many CPU threads system has.
Two years ago I did a lot of compiling tests on the same motherboard, with 3 different Xeon E5-2XXX flavors:
| Code: | E5-2640, 6 physical cores, 12 with HT
E5-2687W v2, 8 physical cores, 16 with HT
E5-2697 v2, 12 physical cores, 24 with HT |
In dual-CPU configuration, the same number of memory channels and same type of memory sticks were used for both CPU.
Results for E5-2640, chromium-88.0.4324.182, this test was done to establish a baseline:
| Code: | | Threads: 12; RAM: 64 GiB; Chromium compile time: 6h 50m 36s |
Results for single E5-2687W v2, chromium-89.0.4389.72, MAKEOPTS="-j15" (From X. No Firefox, no Teams, no Conky):
| Code: | RAM: 32 GiB (4x8GiB); Chromium compile time: 4h 10m 58s
RAM: 32 GiB (16GiB+2x8GiB); Chromium compile time: 4h 27m 47s (From X. Firefox and Teams open) (Memory peak use: 30441712 KiB) (Swap: 3.3M)
RAM: 32 GiB (16GiB+2x8GiB); Chromium compile time: 4h 14m 33s (Memory peak use: 28345864 KiB) (Swap: 264K)
RAM: 32 GiB (2x16GiB); Chromium compile time: 4h 18m 25s (Memory peak use: 26618540 KiB) (Swap: 776K)
RAM: 32 GiB (1x32GiB@1866MHz); Chromium compile time: 4h 19m 25s (Memory peak use: 27189324 KiB) (Swap: 264K)
RAM: 40 GiB (5x8GiB@1333MHz); Chromium compile time: 4h 10m 57s (Memory peak use: 28612384 KiB) (Swap: 520K)
RAM: 40 GiB (16GiB+3x8GiB@1333MHz); Chromium compile time: 4h 11m 39s (Memory peak use: 27137568 KiB) (Swap: 264K)
RAM: 40 GiB (2x16GiB+8GiB@1333MHz); Chromium compile time: 4h 14m 42s (Memory peak use: 27825476 KiB) (Swap: 8K)
RAM: 40 GiB (2x16GiB+8GiB@1600MHz); Chromium compile time: 4h 12m 6s (Memory peak use: 28300296 KiB) (Swap: 520K)
RAM: 48 GiB (16GiB+4x8GiB@1333MHz); Chromium compile time: 4h 13m 16s (Memory peak use: 28211884 KiB) (Swap: 520K)
RAM: 48 GiB (2x16GiB+2x8GiB@1333MHz); Chromium compile time: 4h 12m 11s (Memory peak use: 28576656 KiB) (Swap: 0)
RAM: 48 GiB (2x16GiB+2x8GiB@1600MHz); Chromium compile time: 4h 10m 31s (Memory peak use: 27582552 KiB) (Swap: 0)
RAM: 48 GiB (3x16GiB@1600MHz); Chromium compile time: 4h 11m 53s (Memory peak use: 27397824 KiB) (Swap: 0)
RAM: 56 GiB (16GiB+5x8GiB@1333MHz); Chromium compile time: 4h 12m 35s (Memory peak use: 26961056 KiB) (Swap: 0)
RAM: 56 GiB (2x16GiB+3x8GiB@1333MHz); Chromium compile time: 4h 14m 13s (Memory peak use: 26305972 KiB) (Swap: 0)
RAM: 56 GiB (3x16GiB+8GiB@1333MHz); Chromium compile time: 4h 13m 16s (Memory peak use: 28141656 KiB) (Swap: 0)
RAM: 56 GiB (3x16GiB+8GiB@1600MHz); Chromium compile time: 4h 10m 34s (Memory peak use: 26871600 KiB) (Swap: 0)
RAM: 64 GiB (8x8GiB@1333MHz); Chromium compile time: 4h 9m 47s (Memory peak use: 28140252 KiB) (Swap: 0)
RAM: 64 GiB (2x16GiB+4x8GiB@1333MHz); Chromium compile time: 4h 14m 9s (Memory peak use: 26955104 KiB) (Swap: 0)
RAM: 64 GiB (4x16GiB@1600MHz); Chromium compile time: 4h 10m 29s (Memory peak use: 27978364 KiB) (Swap: 0)
RAM: 64 GiB (2x32GiB@1333MHz); Chromium compile time: 4h 13m 55s (Memory peak use: 28093332 KiB) (Swap: 0)
RAM: 64 GiB (2x32GiB@1866MHz); Chromium compile time: 4h 11m 38s (Memory peak use: 26375220 KiB) (Swap: 0)
RAM: 72 GiB (2x16GiB+5x8GiB@1333MHz); Chromium compile time: 4h 12m 16s (Memory peak use: 27742192 KiB) (Swap: 0)
RAM: 96 GiB (4x16GiB+4x8GiB@1333MHz); Chromium compile time: 4h 12m 43s (Memory peak use: 29047576 KiB) (Swap: 0)
RAM: 96 GiB (4x16GiB+4x8GiB@1600MHz); Chromium compile time: 4h 10m 48s (Memory peak use: 28041900 KiB) (Swap: 0)
RAM: 96 GiB (3x32GiB@1333MHz); Chromium compile time: 4h 13m 46s (Memory peak use: 28461792 KiB) (Swap: 0)
RAM: 96 GiB (3x32GiB@1866MHz); Chromium compile time: 4h 9m 57s (Memory peak use: 27419148 KiB) (Swap: 0)
RAM: 128 GiB (4x16GiB+8x8GiB@1066MHz); Chromium compile time: 4h 15m 35s (Memory peak use: 27407152 KiB) (Swap: 0)
RAM: 128 GiB (4x32GiB@1333MHz); Chromium compile time: 4h 12m 17s (Memory peak use: 26469860 KiB) (Swap: 0)
RAM: 128 GiB (4x32GiB@1866MHz); Chromium compile time: 4h 8m 13s (Memory peak use: 26389000 KiB) (Swap: 0)
RAM: 160 GiB (5x32GiB@1333MHz); Chromium compile time: 4h 25m 32s (Memory peak use: 27983212 KiB) (Swap: 0)
RAM: 160 GiB (5x32GiB@1866MHz); Chromium compile time: 4h 16m 2s (Memory peak use: 26745744 KiB) (Swap: 0)
RAM: 192 GiB (6x32GiB@1333MHz); Chromium compile time: 4h 14m 33s (Memory peak use: 26525668 KiB) (Swap: 0)
RAM: 192 GiB (6x32GiB@1866MHz); Chromium compile time: 4h 9m 41s (Memory peak use: 27587068 KiB) (Swap: 0)
RAM: 224 GiB (7x32GiB@1333MHz); Chromium compile time: 4h 22m 50s (Memory peak use: 27987444 KiB) (Swap: 0)
RAM: 224 GiB (7x32GiB@1866MHz); Chromium compile time: 4h 14m 42s (Memory peak use: 28137312 KiB) (Swap: 0)
RAM: 256 GiB (8x32GiB@1333MHz); Chromium compile time: 4h 11m 58s (Memory peak use: 27578092 KiB) (Swap: 0)
RAM: 256 GiB (8x32GiB@1866MHz); Chromium compile time: 4h 8m 40s (Memory peak use: 28297108 KiB) (Swap: 0)
|
Results for dual E5-2687W v2, chromium-89.0.4389.72, MAKEOPTS="-j31" (From X. No Firefox, no Teams, no Conky):
| Code: | RAM: 64 GiB ([4x8GiB@1333MHz] + [4x8GiB@1333MHz]); Chromium compile time: 2h 17m 42s (Memory peak use: 46600136 KiB) (Swap: 8K)
RAM: 64 GiB ([16GiB+2x8GiB@1333MHz] + [16GiB+2x8GiB@1333MHz]); Chromium compile time: 2h 21m 20s (Memory peak use: 47260604 KiB) (Swap: 0)
RAM: 64 GiB ([16GiB+2x8GiB@1600MHz] + [16GiB+2x8GiB@1600MHz]); Chromium compile time: 2h 19m 17s (Memory peak use: 46182344 KiB) (Swap: 0)
RAM: 64 GiB ([16GiB+2x8GiB@1600MHz] + [16GiB+2x8GiB@1600MHz]); Chromium compile time: 2h 19m 17s (Memory peak use: 46182344 KiB) (Swap: 0)
RAM: 64 GiB ([1x32GiB@1866MHz] + [1x32GiB@1866MHz]); Chromium compile time: 2h 28m 20s (Memory peak use: 47142328 KiB) (Swap: 0)
RAM: 80 GiB ([5x8GiB@1333MHz] + [5x8GiB@1333MHz]); Chromium compile time: 2h 17m 27s (Memory peak use: 47932340 KiB) (Swap: 0)
RAM: 80 GiB ([16GiB+3x8GiB@1333MHz] + [16GiB+3x8GiB@1333MHz]); Chromium compile time: 2h 18m 53s (Memory peak use: 46091972 KiB) (Swap: 0)
RAM: 80 GiB ([2x16GiB+8GiB@1333MHz] + [2x16GiB+8GiB@1333MHz]); Chromium compile time: 2h 20m 14s (Memory peak use: 46745848 KiB) (Swap: 0)
RAM: 80 GiB ([2x16GiB+8GiB@1600MHz] + [2x16GiB+8GiB@1600MHz]); Chromium compile time: 2h 20m 8s (Memory peak use: 46578552 KiB) (Swap: 0)
RAM: 96 GiB ([16GiB+4x8GiB@1333MHz] + [16GiB+4x8GiB@1333MHz]); Chromium compile time: 2h 21m 33s (Memory peak use: 47763108 KiB) (Swap: 0)
RAM: 96 GiB ([2x16GiB+2x8GiB@1333MHz] + [2x16GiB+2x8GiB@1333MHz]); Chromium compile time: 2h 19m 7s (Memory peak use: 46749656 KiB) (Swap: 0)
RAM: 96 GiB ([2x16GiB+2x8GiB@1600MHz] + [2x16GiB+2x8GiB@1600MHz]); Chromium compile time: 2h 17m 11s (Memory peak use: 49964200 KiB) (Swap: 0)
RAM: 112 GiB ([16GiB+5x8GiB@1333MHz] + [16GiB+5x8GiB@1333MHz]); Chromium compile time: 2h 20m 36s (Memory peak use: 48688060 KiB) (Swap: 0)
RAM: 112 GiB ([2x16GiB+3x8GiB@1333MHz] + [2x16GiB+3x8GiB@1333MHz]); Chromium compile time: 2h 20m 52s (Memory peak use: 45401460 KiB) (Swap: 0)
RAM: 128 GiB ([2x16GiB+4x8GiB@1333MHz] + [2x16GiB+4x8GiB@1333MHz]); Chromium compile time: 2h 21m 28s (Memory peak use: 46194968 KiB) (Swap: 0)
RAM: 128 GiB ([2x32GiB@1866MHz] + [2x32GiB@1866MHz]); Chromium compile time: 2h 19m 0s (Memory peak use: 46294860 KiB) (Swap: 0)
RAM: 144 GiB ([2x16GiB+5x8GiB@1333MHz] + [2x16GiB+5x8GiB@1333MHz]); Chromium compile time: 2h 20m 5s (Memory peak use: 47763828 KiB) (Swap: 0)
RAM: 192 GiB ([3x32GiB@1866MHz] + [3x32GiB@1866MHz]); Chromium compile time: 2h 16m 18s (Memory peak use: 47347868 KiB) (Swap: 0)
RAM: 256 GiB ([4x32GiB@1866MHz] + [4x32GiB@1866MHz]); Chromium compile time: 2h 16m 15s (Memory peak use: 45580668 KiB) (Swap: 0)
|
Results for single E5-2697 v2 (No hyperthreading), chromium-89.0.4389.72, MAKEOPTS="-j11" (From X. No Firefox, no Teams, no Conky):
| Code: | RAM: 96 GiB (4x16GiB+4x8GiB@1333MHz); Chromium compile time: 4h 24m 32s (Memory peak use: 22359136 KiB) (Swap: 0)
|
Results for single E5-2697 v2, chromium-89.0.4389.72, MAKEOPTS="-j23" (From X. No Firefox, no Teams, no Conky):
| Code: | RAM: 40 GiB (5x8GiB@1333MHz); Chromium compile time: 3h 31m 19s (Memory peak use: 36442444 KiB) (Swap: 776K)
RAM: 40 GiB (16GiB+3x8GiB@1333MHz); Chromium compile time: 3h 31m 38s (Memory peak use: 37623988 KiB) (Swap: 264K)
RAM: 40 GiB (2x16GiB+8GiB@1333MHz); Chromium compile time: 3h 32m 1s (Memory peak use: 37257496 KiB) (Swap: 520K)
RAM: 40 GiB (2x16GiB+8GiB@1600MHz); Chromium compile time: 3h 31m 6s (Memory peak use: 37011088 KiB) (Swap: 520K)
RAM: 48 GiB (16GiB+4x8GiB@1333MHz); Chromium compile time: 3h 30m 30s (Memory peak use: 36003384 KiB) (Swap: 1M)
RAM: 48 GiB (2x16GiB+2x8GiB@1333MHz); Chromium compile time: 3h 29m 14s (Memory peak use: 37218724 KiB) (Swap: 520K)
RAM: 48 GiB (2x16GiB+2x8GiB@1600MHz); Chromium compile time: 3h 27m 48s (Memory peak use: 36307636 KiB) (Swap: 264K)
RAM: 48 GiB (3x16GiB@1600MHz); Chromium compile time: 3h 28m 36s (Memory peak use: 36950516 KiB) (Swap: 520K)
RAM: 56 GiB (16GiB+5x8GiB@1333MHz); Chromium compile time: 3h 29m 59s (Memory peak use: 36517132 KiB) (Swap: 0)
RAM: 56 GiB (2x16GiB+3x8GiB@1333MHz); Chromium compile time: 3h 30m 31s (Memory peak use: 36825840 KiB) (Swap: 0)
RAM: 56 GiB (3x16GiB+8GiB@1333MHz); Chromium compile time: 3h 29m 20s (Memory peak use: 37456016 KiB) (Swap: 0)
RAM: 56 GiB (3x16GiB+8GiB@1600MHz); Chromium compile time: 3h 27m 47s (Memory peak use: 36453632 KiB) (Swap: 0)
RAM: 64 GiB (2x32GiB@1333MHz); Chromium compile time: 3h 30m 28s (Memory peak use: 37541248 KiB) (Swap: 0)
RAM: 64 GiB (8x8GiB@1333MHz); Chromium compile time: 3h 26m 59s (Memory peak use: 37770160 KiB) (Swap: 0)
RAM: 56 GiB (2x16GiB+4x8GiB@1333MHz); Chromium compile time: 3h 29m 46s (Memory peak use: 35827564 KiB) (Swap: 0)
RAM: 64 GiB (4x16GiB@1600MHz); Chromium compile time: 3h 27m 31s (Memory peak use: 36272684 KiB) (Swap: 0)
RAM: 64 GiB (2x32GiB@1866MHz); Chromium compile time: 3h 27m 17s (Memory peak use: 37899560 KiB) (Swap: 0)
RAM: 72 GiB (2x16GiB+5x8GiB@1333MHz); Chromium compile time: 3h 29m 39s (Memory peak use: 36596516 KiB) (Swap: 0)
RAM: 96 GiB (4x16GiB+4x8GiB@1333MHz); Chromium compile time: 3h 28m 51s (Memory peak use: 36098756 KiB) (Swap: 0)
RAM: 96 GiB (4x16GiB+4x8GiB@1600MHz); Chromium compile time: 3h 27m 50s (Memory peak use: 36916308 KiB) (Swap: 0)
RAM: 96 GiB (4x16GiB+4x8GiB@1333MHz); Chromium compile time: 3h 29m 6s (Memory peak use: 36695088 KiB) (Swap: 0)
RAM: 96 GiB (4x16GiB+4x8GiB@1600MHz); Chromium compile time: 3h 27m 24s (Memory peak use: 36572624 KiB) (Swap: 0)
RAM: 96 GiB (3x32GiB@1866MHz); Chromium compile time: 3h 27m 2s (Memory peak use: 36127364 KiB) (Swap: 0)
RAM: 128 GiB (4x16GiB+8x8GiB@1333MHz); Chromium compile time: 3h 28m 52s (Memory peak use: 35736916 KiB) (Swap: 0)
RAM: 128 GiB (4x32GiB@1866MHz); Chromium compile time: 3h 26m 35s (Memory peak use: 37419204 KiB) (Swap: 0)
RAM: 160 GiB (5x32GiB@1866MHz); Chromium compile time: 3h 31m 50s (Memory peak use: 36269956 KiB) (Swap: 0)
RAM: 192 GiB (6x32GiB@1866MHz); Chromium compile time: 3h 27m 12s (Memory peak use: 36458584 KiB) (Swap: 0)
RAM: 224 GiB (7x32GiB@1866MHz); Chromium compile time: 3h 26m 30s (Memory peak use: 36759788 KiB) (Swap: 0)
RAM: 256 GiB (8x32GiB@1866MHz); Chromium compile time: 3h 25m 55s (Memory peak use: 36601128 KiB) (Swap: 0)
|
Results for dual E5-2697 v2, chromium-89.0.4389.72, MAKEOPTS="-j47" (From X. No Firefox, no Teams, no Conky):
| Code: | RAM: 80 GiB ([5x8GiB@1333MHz] + [5x8GiB@1333MHz]); Chromium compile time: 1h 55m 9s (Memory peak use: 60304228 KiB) (Swap: 0)
RAM: 80 GiB ([16GiB+3x8GiB@1333MHz] + [16GiB+3x8GiB@1333MHz]); Chromium compile time: 1h 56m 1s (Memory peak use: 59556612 KiB) (Swap: 0)
RAM: 80 GiB ([2x16GiB+8GiB@1333MHz] + [2x16GiB+8GiB@1333MHz]); Chromium compile time: 1h 56m 13s (Memory peak use: 61527404 KiB) (Swap: 0)
RAM: 80 GiB ([2x16GiB+8GiB@1600MHz] + [2x16GiB+8GiB@1600MHz]); Chromium compile time: 1h 55m 32s (Memory peak use: 59971684 KiB) (Swap: 0)
RAM: 96 GiB ([16GiB+4x8GiB@1333MHz] + [16GiB+4x8GiB@1333MHz]); Chromium compile time: 1h 58m 37s (Memory peak use: 59855504 KiB) (Swap: 0)
RAM: 96 GiB ([2x16GiB+2x8GiB@1333MHz] + [2x16GiB+2x8GiB@1333MHz]); Chromium compile time: 1h 55m 36s (Memory peak use: 62513444 KiB) (Swap: 0)
RAM: 96 GiB ([2x16GiB+2x8GiB@1600MHz] + [2x16GiB+2x8GiB@1600MHz]); Chromium compile time: 1h 54m 55s (Memory peak use: 59102832 KiB) (Swap: 0)
RAM: 112 GiB ([16GiB+5x8GiB@1333MHz] + [16GiB+5x8GiB@1333MHz]); Chromium compile time: 1h 58m 43s (Memory peak use: 61886872 KiB) (Swap: 0)
RAM: 112 GiB ([2x16GiB+3x8GiB@1333MHz] + [2x16GiB+3x8GiB@1333MHz]); Chromium compile time: 1h 59m 50s (Memory peak use: 59373236 KiB) (Swap: 0)
RAM: 128 GiB ([2x16GiB+4x8GiB@1333MHz] + [2x16GiB+4x8GiB@1333MHz]); Chromium compile time: 1h 58m 33s (Memory peak use: 58334020 KiB) (Swap: 0)
RAM: 128 GiB ([2x32GiB@1866MHz] + [2x32GiB@1866MHz]); Chromium compile time: 1h 58m 12s (Memory peak use: 59352460 KiB) (Swap: 0)
RAM: 144 GiB ([2x16GiB+5x8GiB@1333MHz] + [2x16GiB+5x8GiB@1333MHz]); Chromium compile time: 1h 57m 15s (Memory peak use: 61693408 KiB) (Swap: 0)
RAM: 192 GiB ([3x32GiB@1866MHz] + [3x32GiB@1866MHz]); Chromium compile time: 1h 55m 21s (Memory peak use: 60263968 KiB) (Swap: 0)
RAM: 256 GiB ([4x32GiB@1866MHz] + [4x32GiB@1866MHz]); Chromium compile time: 1h 53m 42s (Memory peak use: 58144268 KiB) (Swap: 0)
|
Results for dual E5-2697 v2, chromium-89.0.4389.72, MAKEOPTS="-j47" (From text console. No X. Stopped all services except for iptables, net, sshd, minidlna, syslog, ntpd, local):
| Code: | RAM: 256 GiB ([4x32GiB@1866MHz] + [4x32GiB@1866MHz]); Chromium compile time: 1h 53m 49s (Memory peak use: 57611964 KiB) (Swap: 0)
|
Results for dual E5-2697 v2, chromium-89.0.4389.72, MAKEOPTS="-j47" (From text console. No X. All services are running):
| Code: | RAM: 256 GiB ([4x32GiB@1866MHz] + [4x32GiB@1866MHz]); Chromium compile time: 1h 54m 35s (Memory peak use: 58440636 KiB) (Swap: 0)
|
I made a few conclusions (though I am not an expert in this field, my knowledge comes from tests):
a) You may have less powerful single-threaded CPU (E5-2697) which will outperform more powerful one (E5-2687W), because E5-2697 has more threads;
b) It really matters how much memory each thread has. If it system has 2GiB per CPU thread or less, chances are that due to swapping system will not compile Chromium.
c) It is important to balance memory sticks over memory channels. This is less important than having more CPU threads/cores, still, there is a room for optimization here.
d) Having a lot of CPU cores and memory is important to compile Chromium. Chromium build needs about 4-5 GiB per core/thread to be happy.
e) Memory speed plays a role a bit, but not as much as changing CPU.
P.S. If you find a typo/error, please do not judge me harshly, I copy-pasted all this info from different places in my benchmark log. |
|
| Back to top |
|
|
logrusx
Veteran
Joined: 22 Feb 2018
Posts: 1589
|
| Posted: Mon Apr 03, 2023 6:02 am Post subject: |
|
|
| CooSee wrote: | | Quote: | | That's a lucky run. Ccache has proven to be more of a problem rather than a solution. It doesn't benefit compile times even between minor versions as changes have too wide of an impact. |
yes, you're right
sometimes it helps, sometimes not - here are some examples including todays merge:
| Code: | Wed Jan 18 00:55:14 2023 >>> www-client/ungoogled-chromium-109.0.5414.74_p1
merge time: 2 hours, 25 minutes and 27 seconds.
Thu Jan 19 00:16:33 2023 >>> www-client/ungoogled-chromium-109.0.5414.74_p1
merge time: 24 minutes and 27 seconds.
Fri Jan 27 04:26:09 2023 >>> www-client/ungoogled-chromium-109.0.5414.119_p1
merge time: 3 hours, 56 minutes and 22 seconds.
Thu Feb 9 19:03:34 2023 >>> www-client/ungoogled-chromium-109.0.5414.119_p1
merge time: 7 hours, 9 minutes and 50 seconds.
Fri Feb 10 19:31:03 2023 >>> www-client/ungoogled-chromium-110.0.5481.77_p1
merge time: 2 hours, 50 minutes and 10 seconds.
Sun Feb 19 01:13:09 2023 >>> www-client/ungoogled-chromium-110.0.5481.100_p1
merge time: 1 hour, 44 minutes and 48 seconds.
Wed Feb 22 14:16:08 2023 >>> www-client/ungoogled-chromium-110.0.5481.100_p1
merge time: 21 minutes and 52 seconds.
Fri Feb 24 17:55:16 2023 >>> www-client/ungoogled-chromium-110.0.5481.177_p1
merge time: 3 hours, 35 minutes and 50 seconds.
Mon Mar 13 02:55:52 2023 >>> www-client/ungoogled-chromium-111.0.5563.64_p1
merge time: 4 hours, 42 minutes and 13 seconds.
Wed Mar 15 14:27:00 2023 >>> www-client/ungoogled-chromium-111.0.5563.64_p1
merge time: 1 hour, 5 minutes and 34 seconds.
Sat Mar 25 19:19:03 2023 >>> www-client/ungoogled-chromium-111.0.5563.110_p1
merge time: 1 hour, 20 minutes and 42 seconds.
Tue Mar 28 21:41:56 2023 >>> www-client/ungoogled-chromium-111.0.5563.146_p1
merge time: 7 hours, 53 minutes and 4 seconds. |
|
This must include a few terminated builds.
BTW with a fast enough CPU, ccache is in fact a hurdle. I tried with Ryzen 7 5800H and 32Gb RAM and it didn't make a difference for one and the same version, compiled two times. It actually made my CPU hotter.
Best Regards,
Georgi |
|
| Back to top |
|
|
CooSee
Veteran
Joined: 20 Nov 2004
Posts: 1455
Location: Earth
|
| Posted: Wed Apr 12, 2023 1:44 am Post subject: |
|
|
| Quote: | | This must include a few terminated builds. |
yes, you're right - without ccache, it takes more than 8 hours to build, on my system.
_________________
" Die Realität ist eine Illusion, die durch Mangel an ehrlicher Kommunikation entsteht "
---
" Der Mensch ist von Natur aus neugierig, was am Ende übrig bleibt ist die Gier " |
|
| Back to top |
|
|
lyallp
Veteran
Joined: 15 Jul 2004
Posts: 1589
Location: Adelaide/Australia
|
| Posted: Mon May 06, 2024 12:49 am Post subject: |
|
|
Still building.... sigh.... now I remember why I dropped chromium.
Still, my firefox is broken, despite my best efforts, so other than konqueror...
| Code: | # uname -a
Linux Lyalls-PC 6.6.21-gentoo #14 SMP PREEMPT_DYNAMIC Fri May 3 19:07:10 ACST 2024 x86_64 Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz GenuineIntel GNU/Linux
root@Lyalls-PC package.use
# genlop -cte
Currently merging 3 out of 3
* www-client/chromium-124.0.6367.60
current merge time: 23 hours and 54 seconds.
ETA: unknown.
root@Lyalls-PC package.use
# |
32G RAM, of which 24G is devoted to /tmp (tmpfs) and portage configured to use /tmp, not /var/portage/tmp.
I figure RAM disk would be faster than SSD...
_________________
...Lyall |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
