Summary: | www-client/chromium: complication slowdown | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alex Efros <powerman-asdf> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alex Efros
2017-12-11 14:04:09 UTC
I feel you; I have seen chromium go from 20 minutes up to 5 hours on my 6 core AMD chip. There's really not much we can do since the developers keep piling on code. If you want a pre-compiled version of chromium, I suggest www-client/google-chrome, which I also update regularly and use on a daily basis. (In reply to Mike Gilbert from comment #1) > If you want a pre-compiled version of chromium, I suggest > www-client/google-chrome, which I also update regularly and use on a daily > basis. I believe google-chrome isn't the same as chromium - chromium should have much less unconditional google-tracking inside - this is the reason I prefer chromium. This crazy trend continues, now chromium compiles 3x slower than 1 year ago and 20x slower than firefox today. I've read chromium developers/testers say they build it on Windows machines (powerful ones, 32+ cores and a lot of RAM) in a minutes! I just can't believe it's normal to compile it that long on Gentoo. Maybe there are some gcc options should be tuned to speed up it, or we should use different compiler, or enforce using ccache or something. I'm about to give up on using chromium at all. And in any case I'm not going to move to google-chrome, too much google-tracking inside. Another reason which makes me thing there is something wrong in ebuild itself - I've played with MAKEOPTS=-j8 - changes between -j4 and -j8 result in visible change of average CPU load from 100% to 50%, but makes no more than 5-10% difference in build speed. How is this possible? Chromium developers generally do incremental builds -- they rarely build all files more than once. This is not something we can do in an ebuild. |