| View previous topic :: View next topic |
| Author |
Message |
mir3x
Guru
Joined: 02 Jun 2012
Posts: 455
|
 Posted: Mon Oct 01, 2018 6:13 pm Post subject: Chromium is emerging fast again |
 |
|
| Code: | chromium: Mon Jul 2 07:52:59 2018: 8305 seconds
[ Here I enabled jumbo build ]
chromium: Mon Jul 2 10:18:08 2018: 3126 seconds
chromium: Fri Aug 31 21:44:36 2018: 3152 seconds
chromium: Sun Sep 16 10:38:46 2018: 3395 seconds
[ No idea what happened here - its v70 - but its less than 40 mins ...]
chromium: Mon Oct 1 19:26:12 2018: 2222 seconds |
Yay Chromium in less than 40 mins ( ryzen 7 1700X) - unbelivable 
_________________
Sent from Windows |
|
| Back to top |
|
 |
sao98021
Tux's lil' helper
Joined: 03 Apr 2012
Posts: 145
Location: Michigan
|
| Posted: Tue Oct 02, 2018 9:00 pm Post subject: Re: Chromium is emerging fast again |
|
|
| mir3x wrote: | | Code: | chromium: Mon Jul 2 07:52:59 2018: 8305 seconds
[ Here I enabled jumbo build ]
chromium: Mon Jul 2 10:18:08 2018: 3126 seconds
chromium: Fri Aug 31 21:44:36 2018: 3152 seconds
chromium: Sun Sep 16 10:38:46 2018: 3395 seconds
[ No idea what happened here - its v70 - but its less than 40 mins ...]
chromium: Mon Oct 1 19:26:12 2018: 2222 seconds |
Yay Chromium in less than 40 mins ( ryzen 7 1700X) - unbelivable |
what build is that?
i ask cause | Code: | Wed Jun 13 08:12:56 2018 >>> www-client/chromium-67.0.3396.62
merge time: 7 hours, 41 minutes and 57 seconds.
Wed Jun 13 17:58:12 2018 >>> www-client/chromium-67.0.3396.62
merge time: 7 hours, 41 minutes and 9 seconds.
Sun Aug 12 08:53:01 2018 >>> www-client/chromium-68.0.3440.75
merge time: 8 hours, 34 minutes and 17 seconds.
Sun Sep 16 04:54:24 2018 >>> www-client/chromium-69.0.3497.81
merge time: 8 hours, 25 minutes and 19 seconds.
Fri Sep 21 22:32:44 2018 >>> www-client/chromium-69.0.3497.100
merge time: 8 hours, 53 minutes and 30 seconds. |
intel i72670qm. i haven't gotten an oct 1st update.
that said, my i7 is like, 6 years old |
|
| Back to top |
|
|
mir3x
Guru
Joined: 02 Jun 2012
Posts: 455
|
| Posted: Tue Oct 02, 2018 11:12 pm Post subject: |
|
|
U need to enable "jumbo-build" in chromium use flags- emerge should be 2x times faster - and maybe ver70 is even 3x times faster with that, no idea why exaclty in v70 is much faster.
Its just normal ebuild from gentoo repository.
_________________
Sent from Windows |
|
| Back to top |
|
|
sao98021
Tux's lil' helper
Joined: 03 Apr 2012
Posts: 145
Location: Michigan
|
| Posted: Wed Oct 03, 2018 1:07 am Post subject: |
|
|
| mir3x wrote: | U need to enable "jumbo-build" in chromium use flags- emerge should be 2x times faster - and maybe ver70 is even 3x times faster with that, no idea why exaclty in v70 is much faster.
Its just normal ebuild from gentoo repository. |
| Code: | Wed Oct 3 01:46:05 2018 >>> www-client/chromium-69.0.3497.100
merge time: 3 hours, 47 minutes and 36 seconds. |
its no ryzen, but thats acceptable enough for me lol |
|
| Back to top |
|
|
gigel
Guru
Joined: 14 Jan 2003
Posts: 370
Location: .se/.ro
|
| Posted: Wed Oct 10, 2018 8:21 pm Post subject: |
|
|
i always put my laptop to hibernate, but still i think it is unaceptable
* www-client/chromium-67.0.3396.87
Emerged at: Sun Jun 24 18:56:00 2018
Build time: 5 days, 22 hours, 27 minutes, and 23 seconds
_________________
$emerge sux
|
|
| Back to top |
|
|
sao98021
Tux's lil' helper
Joined: 03 Apr 2012
Posts: 145
Location: Michigan
|
| Posted: Thu Oct 11, 2018 7:35 pm Post subject: |
|
|
| gigel wrote: | i always put my laptop to hibernate, but still i think it is unaceptable
* www-client/chromium-67.0.3396.87
Emerged at: Sun Jun 24 18:56:00 2018
Build time: 5 days, 22 hours, 27 minutes, and 23 seconds |
goodness gracious |
|
| Back to top |
|
|
zamlz
n00b
Joined: 22 Jul 2017
Posts: 42
|
| Posted: Mon Oct 15, 2018 5:52 pm Post subject: |
|
|
Sorry for the newb question, but how are you guys checking your emerge times for packages?
_________________
AI/ML/Robotics/Linux - zamlz |
|
| Back to top |
|
|
mir3x
Guru
Joined: 02 Jun 2012
Posts: 455
|
| Posted: Mon Oct 15, 2018 6:25 pm Post subject: |
|
|
Im using qlop from portage utils:
qlop -g chromium - to show each chromium merges.
qlop -t chromium - for average time for all emerges
'genlop' probably does something similar.
_________________
Sent from Windows |
|
| Back to top |
|
|
AJM
Apprentice
Joined: 25 Sep 2002
Posts: 195
Location: Aberdeen, Scotland
|
| Posted: Fri Oct 26, 2018 4:31 pm Post subject: |
|
|
Browsers are ridiculously bloated these days, and Chrome / Chromium has never been fast despite all the marketing nonsense.
Palemoon is the least bad option for me all round:
| Code: | | palemoon: 26 minutes, 23 seconds for 31 merges |
That's on a fairly elderly Core i5 2500K. I'm definitely not going to wait five days for a browser compile! The worst compile for me is Libreoffice at nearly 10 hours. |
|
| Back to top |
|
|
Muso
Veteran
Joined: 22 Oct 2002
Posts: 1052
Location: The Holy city of Honolulu
|
| Posted: Fri Nov 16, 2018 5:05 pm Post subject: |
|
|
Hearing the complaints about Chromium's build time, I had to see for myself. This desktop is running ~amd64 on a AMD FX-8320 Eight-Core @ 8x 3.5GHz with 16 gig of ram.
For comparison, here's the build times of the most recent rust, firefox, and libreoffice :
| Code: | genlop -t rust
* dev-lang/rust
Thu Nov 15 07:03:31 2018 >>> dev-lang/rust-1.30.1-r1
merge time: 1 hour, 2 minutes and 44 seconds.
|
| Code: | genlop -t firefox
* www-client/firefox
Tue Nov 13 09:26:42 2018 >>> www-client/firefox-63.0.1-r1
merge time: 43 minutes and 21 seconds.
|
So taken together, firefox & rust take around 1 hour and 45 minutes.
| Code: | genlop -t libreoffice
* app-office/libreoffice
Tue Nov 13 10:56:14 2018 >>> app-office/libreoffice-6.1.3.2
merge time: 1 hour, 28 minutes and 6 seconds.
|
Nearly 90 minutes for libreoffice
| Code: | genlop -t chromium
* www-client/chromium
Thu Nov 15 23:09:29 2018 >>> www-client/chromium-71.0.3578.30
merge time: 4 hours, 31 minutes and 47 seconds.
|
4 1/2 hours for Chromium (this is without the jumbo-build USE flag)
I now understand what people were talking about.
{EDIT}
Tried with the jumbo-build USE flag and after 90 minutes or so, my system locked. 
So -j9 with 16 gb of ram is not a good combination for that... ergo, I ordered 2 pairs of 8 gb dimms. They will be delivered on Wednesday. I'll try again when I am using 32 gb of ram.
{UPDATE}
Ram came in today, and using jumbo-build is a massive time saver :
| Code: | ╭─root@otherness /home/rasalom
╰─# genlop -t chromium
* www-client/chromium
Thu Nov 15 23:09:29 2018 >>> www-client/chromium-71.0.3578.30
merge time: 4 hours, 31 minutes and 47 seconds.
Wed Nov 21 14:10:46 2018 >>> www-client/chromium-71.0.3578.53
merge time: 1 hour, 27 minutes and 27 seconds.
|
_________________
"You can lead a horticulture but you can't make her think" ~ Dorothy Parker
2021 is the year of the Linux Desktop! |
|
| Back to top |
|
|
AlienPenguin
n00b
Joined: 08 Sep 2004
Posts: 12
Location: Pisa, Italy
|
| Posted: Mon Dec 03, 2018 12:37 pm Post subject: |
|
|
Do you have any special env setting to build chromium 70.0.3538.110?
Since 70 i am not able anymore to use the USE jumbo-build (which was working fine with previous (<70) versions) now i exhaust all the memory (32gb ram and 8gb swap)
these were my previous compilation times:
In March is when i switched to jumbo-build
In July when i got the new ryzen 2700
then with latest chromium i was not able to use jumbo-build anymore... compiling now without it... (still compiling  )
| Quote: |
Wed Feb 21 17:13:55 2018 >>> www-client/chromium-64.0.3282.167
merge time: 4 hours, 8 minutes and 27 seconds.
Mon Mar 12 16:25:49 2018 >>> www-client/chromium-65.0.3325.146
merge time: 2 hours, 18 minutes and 6 seconds.
Fri Jun 22 20:39:43 2018 >>> www-client/chromium-67.0.3396.87
merge time: 2 hours, 24 minutes and 57 seconds.
Sat Jul 14 21:32:56 2018 >>> www-client/chromium-67.0.3396.87
merge time: 45 minutes and 57 seconds.
Tue Jul 31 12:43:27 2018 >>> www-client/chromium-68.0.3440.75
merge time: 1 hour, 11 minutes and 57 seconds.
Mon Aug 27 13:25:52 2018 >>> www-client/chromium-68.0.3440.75
merge time: 48 minutes and 42 seconds.
Fri Sep 14 12:50:10 2018 >>> www-client/chromium-69.0.3497.81
merge time: 1 hour, 21 minutes and 1 second.
Fri Sep 28 18:55:27 2018 >>> www-client/chromium-69.0.3497.100
merge time: 1 hour, 8 minutes and 8 seconds.
Wed Oct 24 17:28:04 2018 >>> www-client/chromium-70.0.3538.67
merge time: 1 hour, 1 minute and 25 seconds.
|
|
|
| Back to top |
|
|
sao98021
Tux's lil' helper
Joined: 03 Apr 2012
Posts: 145
Location: Michigan
|
| Posted: Wed Dec 05, 2018 3:14 am Post subject: |
|
|
| Muso wrote: |
{UPDATE}
Ram came in today, and using jumbo-build is a massive time saver :
|
not sure why it was an issue for you before, i'm building it with only 8 |
|
| Back to top |
|
|
Muso
Veteran
Joined: 22 Oct 2002
Posts: 1052
Location: The Holy city of Honolulu
|
| Posted: Wed Dec 05, 2018 3:23 am Post subject: |
|
|
| sao98021 wrote: | | Muso wrote: |
{UPDATE}
Ram came in today, and using jumbo-build is a massive time saver :
|
not sure why it was an issue for you before, i'm building it with only 8 |
8 cores, -j9 in make.conf, and it was eating 3 gigs per core.
_________________
"You can lead a horticulture but you can't make her think" ~ Dorothy Parker
2021 is the year of the Linux Desktop! |
|
| Back to top |
|
|
gorg86
Guru
Joined: 20 May 2011
Posts: 315
|
| Posted: Wed Dec 05, 2018 8:42 am Post subject: |
|
|
chromium-71.0.3578.30 took ~4h on my machine (FX-8350) with -j8, chromium-41.0.2272.76 just took ~1h.
I wonder how long a Talos Secure Workstation with those dual SMT4 CPUs would need. |
|
| Back to top |
|
|
pjp
Administrator
Joined: 16 Apr 2002
Posts: 20485
|
| Posted: Wed Dec 05, 2018 8:01 pm Post subject: |
|
|
| Muso wrote: | after 90 minutes or so, my system locked.
So -j9 with 16 gb of ram is not a good combination for that... ergo, I ordered 2 pairs of 8 gb dimms. They will be delivered on Wednesday. I'll try again when I am using 32 gb of ram. |
Just to compile Chromium? 
_________________
Quis separabit? Quo animo? |
|
| Back to top |
|
|
Anon-E-moose
Watchman
Joined: 23 May 2008
Posts: 6148
Location: Dallas area
|
| Posted: Wed Dec 05, 2018 8:29 pm Post subject: |
|
|
| gorg86 wrote: | chromium-71.0.3578.30 took ~4h on my machine (FX-8350) with -j8, chromium-41.0.2272.76 just took ~1h.
I wonder how long a Talos Secure Workstation with those dual SMT4 CPUs would need. |
It's insane for a browser to take longer to compile than the whole dev toolchain including libs or emacs with all bells and whistles.
_________________
UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
| Back to top |
|
|
Muso
Veteran
Joined: 22 Oct 2002
Posts: 1052
Location: The Holy city of Honolulu
|
| Posted: Wed Dec 05, 2018 10:16 pm Post subject: |
|
|
| pjp wrote: | | Muso wrote: | after 90 minutes or so, my system locked.
So -j9 with 16 gb of ram is not a good combination for that... ergo, I ordered 2 pairs of 8 gb dimms. They will be delivered on Wednesday. I'll try again when I am using 32 gb of ram. |
Just to compile Chromium? |
Chromium compile locked my system with -j9 and jumbo-build, so 16gb of ram was insufficient. I originally assumed 16 would be plenty, but I was wrong. I also switched to liquid cooling because of Gentoo. Where as before idle was at 30°C and peaking around 80°C with the stock fan, now it idles around 15°C and peaks out around 43°C.
As I've mentioned before, Gentoo is making Amazon, Newegg, and Visa happy.
_________________
"You can lead a horticulture but you can't make her think" ~ Dorothy Parker
2021 is the year of the Linux Desktop! |
|
| Back to top |
|
|
ChrisJumper
Advocate
Joined: 12 Mar 2005
Posts: 2400
Location: Germany
|
| Posted: Sun Dec 09, 2018 6:08 pm Post subject: |
|
|
I have not enough ram for chromium to use jumbo.... and no it did not build fast: ;D
64.0.3282.140 - merge time: 5 hours, 18 minutes and 9 seconds.
64.0.3282.167 - merge time: 9 hours, 14 minutes and 39 seconds.
68.0.3440.75 - merge time: 7 hours, 46 minutes and 20 seconds.
70.0.3538.67 - merge time: 11 hours, 38 minutes and 3 seconds.
No, i will not use chromium again! ;D
Without jumbo builds it did not lock the system. |
|
| Back to top |
|
|
sao98021
Tux's lil' helper
Joined: 03 Apr 2012
Posts: 145
Location: Michigan
|
| Posted: Mon Dec 10, 2018 12:29 am Post subject: |
|
|
i'm in the same boat as you guys now, this is the first time my i7 with 8gb of ram started locking up building with jumbo build, sucks because i only found out about using it like at the time of the last release, meaning i only was able to utilize it once before now i cant even build it anymore xD
oh well, it was nice while it lasted
last working build = | Code: | Installed versions: 70.0.3538.67^d(01:49:37 AM 10/20/2018)(cups hangouts jumbo-build pic proprietary-codecs suid widevine -component-build -custom-cflags -gnome-keyring -kerberos -neon -pulseaudio -selinux -system-ffmpeg -system-icu -system-libvpx -tcmalloc
|
and the release that killed chromium deployment on this box = | Code: | | [ebuild U #] www-client/chromium-71.0.3578.80::gentoo |
without jb enabled, it shows | Code: | Would you like to merge these packages? [Yes/No] y
>>> Verifying ebuild manifests
>>> Running pre-merge checks for www-client/chromium-71.0.3578.80
* Checking for at least 3 GiB RAM ... [ ok ]
* Checking for at least 5 GiB disk space at "/var/tmp/portage/www-client/chromium-71.0.3578.80/temp" ... [ ok ]
>>> Running pre-merge checks for dev-util/electron-1.6.18
* Checking for at least 3 GiB RAM ... [ ok ]
* Checking for at least 5 GiB disk space at "/var/tmp/portage/dev-util/electron-1.6.18/temp" ... [ ok ]
|
note that building this failed with jb disabled, after about 7 hours i got a weird "chromedriver" error way way late in the build process resulting in death, this wraps up my time with chromium, i'll be moving on.. even package mask wouldn't stick and wanted me to upgrade chromium every time, several avenues of masking it actually... to make my life easier, simply uninstalled.
Last edited by sao98021 on Mon Dec 10, 2018 12:01 pm; edited 3 times in total |
|
| Back to top |
|
|
Muso
Veteran
Joined: 22 Oct 2002
Posts: 1052
Location: The Holy city of Honolulu
|
| Posted: Mon Dec 10, 2018 12:37 am Post subject: |
|
|
| Code: | genlop -t chromium
* www-client/chromium
Thu Nov 15 23:09:29 2018 >>> www-client/chromium-71.0.3578.30
merge time: 4 hours, 31 minutes and 47 seconds.
Wed Nov 21 14:10:46 2018 >>> www-client/chromium-71.0.3578.53
merge time: 1 hour, 27 minutes and 27 seconds.
Sun Nov 25 10:42:55 2018 >>> www-client/chromium-71.0.3578.62
merge time: 1 hour, 31 minutes and 1 second.
Thu Nov 29 11:51:18 2018 >>> www-client/chromium-71.0.3578.62
merge time: 1 hour, 38 minutes and 36 seconds.
Thu Nov 29 12:02:36 2018 >>> www-client/chromium-71.0.3578.62
merge time: 7 minutes and 28 seconds.
Thu Nov 29 23:31:29 2018 >>> www-client/chromium-71.0.3578.62
merge time: 6 minutes and 48 seconds.
Tue Dec 4 10:43:13 2018 >>> www-client/chromium-71.0.3578.62
merge time: 1 hour, 39 minutes and 32 seconds.
Fri Dec 7 08:12:55 2018 >>> www-client/chromium-71.0.3578.80
merge time: 50 minutes and 42 seconds.
|
First one w/out jumbo-build, and the last 4 with both ccache and jumbo-build.
_________________
"You can lead a horticulture but you can't make her think" ~ Dorothy Parker
2021 is the year of the Linux Desktop! |
|
| Back to top |
|
|
pun_guin
Apprentice
Joined: 06 Feb 2018
Posts: 204
|
| Posted: Tue Dec 11, 2018 9:31 am Post subject: |
|
|
| AJM wrote: | | Browsers are ridiculously bloated these days |
It depends on what you need. www-client/netsurf is mostly fine, unless you rely on "web applications" for serious work.
_________________
I already use the new Genthree. |
|
| Back to top |
|
|
forrestfunk81
Guru
Joined: 07 Feb 2006
Posts: 567
Location: münchen.de
|
| Posted: Wed Dec 12, 2018 9:46 am Post subject: |
|
|
The jumbobuild for chromium-71.0.3578.80 also locked my system.
32 Gig RAM
16 Gig swap
i7-6820HQ
MAKEOPTS="-j9 -l8"
Unfortunately I need this browser for work and I don't want to get all the precompiled Google stuff on my laptop.
_________________
# cd /pub/
# more beer |
|
| Back to top |
|
|
mir3x
Guru
Joined: 02 Jun 2012
Posts: 455
|
| Posted: Wed Dec 19, 2018 2:40 pm Post subject: |
|
|
| forrestfunk81 wrote: | The jumbobuild for chromium-71.0.3578.80 also locked my system.
32 Gig RAM
16 Gig swap
i7-6820HQ
MAKEOPTS="-j9 -l8"
Unfortunately I need this browser for work and I don't want to get all the precompiled Google stuff on my laptop. |
Thats a bit strange, I have 48 Gigs RAM, 0 swap(even disabled in kernel, CONFIG-SWAP=n) but: 2G on tmpfs in /tmp , 16G tmpfs on /var/tmp/portage and 3 Gigs for my own ccache (outside portage) compiles
and MAKEOPTS="-j16" and it never locked for me. Anyway your ram + swap is already 48 Gigs ( and I guess at least 5 gigs is used by portage in my tmpfs- merge says - Checking for at least 5 GiB disk space at "/var/tmp/portage/www-client/chromium-71.0.3578.80/temp")
EDIT: it seems im using clang to compile
I have in /etc/portage/package.env/default:
www-client/chromium clang
and in /etc/portage/env/clang
CC="clang"
CXX="clang++"
CFLAGS="-march=znver1 -O2 -pipe"
CXXFLAGS="${CFLAGS}"
LDFLAGS="-Wl,-O2 -Wl,--as-needed"
Seems I switched like 2 years when it failed to compile with gcc7.x and forgot ...
EDIT2:
oops, seems Im using custom installed clang (zapcc) unless portage uses some env to find clang, my clang reports:
clang -v
| Code: | clang version 5.0.0 (trunk) (https://github.com/yrnkrn/zapcc c2b11ba7d65eb36a595f8da5044e39868d8d825b) built on Jun 20 2018 08:04:52
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Selected GCC installation: /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Selected multilib: .;@m64 |
Zapcc has his own command so I guess its probably just pure clang 5.0, not real zapcc.
EDIT3:
I disabled clang env and tried with gcc and it failed to compile (died in lack of ram), when it died free -g -s1 reported that used was 42G, buff/cache was 4 ( during compile it was 7), and was something in shared.
_________________
Sent from Windows |
|
| Back to top |
|
|
sao98021
Tux's lil' helper
Joined: 03 Apr 2012
Posts: 145
Location: Michigan
|
| Posted: Wed Dec 19, 2018 6:20 pm Post subject: |
|
|
| mir3x wrote: |
EDIT3:
I disabled clang env and tried with gcc and it failed to compile (died in lack of ram), when it died free -g -s1 reported that used was 42G, buff/cache was 4 ( during compile it was 7), and was something in shared. |
thats interesting |
|
| Back to top |
|
|
vovan47
n00b
Joined: 21 Nov 2018
Posts: 41
|
| Posted: Wed Dec 26, 2018 6:22 am Post subject: |
|
|
| forrestfunk81 wrote: | The jumbobuild for chromium-71.0.3578.80 also locked my system.
32 Gig RAM
16 Gig swap
i7-6820HQ
MAKEOPTS="-j9 -l8"
Unfortunately I need this browser for work and I don't want to get all the precompiled Google stuff on my laptop. |
Hi, what is your "jumbo_file_merge_limit" value? I have only 16 GB of ram with no swap, and I've tuned env settings for chrome as suggested in this thread and build succeded.
It failed with default settings though (it seems it's 200).
BTW, my CPU is modest (Intel Core i5-5200U, 4 threads), but build took only 3,5 hours:
| Code: | acer ~ # genlop -t chromium
* www-client/chromium
Tue Dec 25 22:11:26 2018 >>> www-client/chromium-71.0.3578.80
merge time: 3 hours, 24 minutes and 14 seconds. |
[Moderator edit: changed [quote] tags to [code] tags to preserve output layout. -Hu] |
|
| Back to top |
|
|
|
Gentoo Chat
