gentoo compilation time for chromium

[fedeliallalinea]

I'm very happy with the Firefox 57 beta. The new Quantum engine is very fast. You can find ebuild in the mozilla overlay.

The problem is that developer tools of chromium are very powerful

[Tom_]

I'm already using Firefox (version 56 for the moment) but I like to have two different browsers! I'll take a look at Firefox 57 beta but also at Palemoon!

[Mrat]

Pfff it just took me 4 hours and 9 minutes to emerge www-client/chromium-62.0.3202.62 with an Intel i5 2500k ! Seriously?! More than 4 hours to build a web browser ?

Code: Select all

mrat ~ # genlop -t chromium
 * www-client/chromium

     Fri Oct  6 06:05:39 2017 >>> www-client/chromium-61.0.3163.100
       merge time: 7 hours, 7 minutes and 25 seconds.

I would love just 4 hours.

[Ant P.]

Yeah, it's getting a bit ridiculous. Chromium's tarballs have grown morbidly obese too, not something I want to put up with every fortnight for security updates. I'm already preparing to vote with my feet again:

Code: Select all

 ~ $ qlop -gHd '1 week ago' www-client/{chromium,firefox} dev-lang/rust
chromium: Thu Oct 26 10:04:16 2017: 7 hours, 11 minutes, 11 seconds
chromium: 1 times
firefox: Sat Oct 28 01:06:02 2017: 52 minutes, 29 seconds
firefox: 1 times
rust: Fri Oct 27 22:15:42 2017: 1 hour, 39 minutes, 15 seconds
rust: 1 times

[Perfect Gentleman]

Code: Select all

chromium: Sat Oct 28 01:15:26 2017: 2 hours, 4 seconds
chromium: 1 times
firefox: Thu Oct 26 14:18:35 2017: 15 minutes, 35 seconds
firefox: 1 times
rust: Sat Oct 28 00:40:25 2017: 35 minutes, 1 second
rust: 1 times

Code: Select all

firefox: Thu Oct 26 14:39:10 2017: 33 minutes, 50 seconds
firefox: 1 times
rust: Sat Oct 28 11:03:09 2017: 1 hour, 2 minutes, 16 seconds
rust: 1 times

[mimosinnet]

I have a binhost to compile binary packages for my laptops, so I do not have to worry about compile times (particularly if something breaks down).

Code: Select all

# cat /proc/cpuinfo | grep 'model name'
model name      : Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz

Code: Select all

# genlop -t chromiu
     Wed Oct 18 06:18:50 2017 >>> www-client/chromium-61.0.3163.100
       merge time: 8 hours, 51 minutes and 33 seconds.

     Mon Oct 23 06:17:19 2017 >>> www-client/chromium-62.0.3202.62
       merge time: 9 hours, 51 minutes and 20 seconds.

     Tue Nov 14 07:49:04 2017 >>> www-client/chromium-62.0.3202.89
       merge time: 9 hours, 54 minutes and 58 seconds.

     Sun Nov 19 03:58:33 2017 >>> www-client/chromium-62.0.3202.89
       merge time: 9 hours, 54 minutes and 46 seconds

[kitsunenokenja]

Why are you all showing insanely long compile times? Are you not using ccache? Note: this is my build time with ccache and ungoogled patches from pg_overlay. Added two other entries for comparison purposes. Everything built with GCC 5.4.

Code: Select all

     Mon Nov  6 19:58:16 2017 >>> www-client/chromium-62.0.3202.84
       merge time: 3 hours, 12 minutes and 16 seconds.

     Mon Oct  9 18:04:31 2017 >>> www-client/firefox-52.4.0
       merge time: 25 minutes and 30 seconds.

     Thu Nov 16 00:19:35 2017 >>> app-office/libreoffice-5.4.2.2
       merge time: 1 hour, 9 minutes and 30 seconds.

[Anon-E-moose]

Showing compile times without mentioning the CPU and memory doesn't mean much of anything.

A single core cpu running a 2.4ghz vs a 8 core processor running at 3.4ghz will definitely show differences in compile times.

[msava]

In case of overly long compile times, you may want to try to add the following to your /etc/make.conf:
MAKEOPTS="-jX"
Where X is the number of physical cores + 1

I believe you meant to say logical cores, did you not?

[Nreal]

boxi /home/markus # genlop -t chromium
* www-client/chromium

Tue Jun 5 02:01:57 2018 >>> www-client/chromium-66.0.3359.170
merge time: 5 hours, 2 minutes and 52 seconds.

Wed Jun 6 09:55:21 2018 >>> www-client/chromium-67.0.3396.62
merge time: 5 hours, 38 minutes and 3 seconds.

Thu Jun 7 00:17:16 2018 >>> www-client/chromium-67.0.3396.62
merge time: 7 hours, 41 minutes and 17 seconds.

Sat Jun 9 05:17:23 2018 >>> www-client/chromium-67.0.3396.62
merge time: 6 hours, 19 minutes and 47 seconds.

Sun Jun 10 14:57:59 2018 >>> www-client/chromium-67.0.3396.79
merge time: 6 hours, 32 minutes and 46 seconds.

Fri Jun 15 08:24:47 2018 >>> www-client/chromium-67.0.3396.87
merge time: 1 hour, 49 minutes and 34 seconds.

Sat Jun 16 16:52:38 2018 >>> www-client/chromium-68.0.3440.25
merge time: 1 hour, 52 minutes and 57 seconds.

Thu Jul 19 06:11:17 2018 >>> www-client/chromium-68.0.3440.25
merge time: 1 hour, 40 minutes and 8 seconds.

Thu Jul 19 16:06:02 2018 >>> www-client/chromium-68.0.3440.25
merge time: 18 minutes and 21 seconds.

[jpp_]

Code: Select all

model name      : Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz

Code: Select all

Sun Jul 15 17:05:23 2018 >>> www-client/chromium-68.0.3440.25
       merge time: 4 hours, 27 minutes and 3 seconds.

i7 3930k - 6c 12t

[Goverp]

IIUC qt-webengine is based on Chrome code, and it's now taking me 6hrs to compile. Is there any way to give its ebuild the "jumbo" treatment?

[Nreal]

Code: Select all

Sat Jul 21 13:24:35 2018 >>> www-client/chromium-68.0.3440.25
       merge time: 16 minutes and 51 seconds.

Code: Select all

2X Intel(R) Xeon(R) CPU E5-2696 v3 @ 2.30GHz

[Chiitoo]

IIUC qt-webengine is based on Chrome code, and it's now taking me 6hrs to compile. Is there any way to give its ebuild the "jumbo" treatment?

Chromium, yes. :]

Jumbo builds have been available in QtWebEngine since 2017-11-22, I believe starting from 5.10.1 what comes to releases.

I don't imagine it will be feasible for the 5.9 branch though.

[Goverp]

...
Jumbo builds have been available in QtWebEngine since 2017-11-22, I believe starting from 5.10.1 what comes to releases.
...

Thanks for the info.
IIUC, that'll be hard-wired into the code, which would explain why there's no USE=jumbo on the extant qtwebengine-5.11.1.ebuild?