1 |
On 2017-12-06, Mick <michaelkintzios@×××××.com> wrote: |
2 |
|
3 |
> I discovered that building Chromium with gcc-6.4.0 is taking an inordinately |
4 |
> longer time on a laptop with 1st gen i7 and 4G of RAM, e.g.: |
5 |
> |
6 |
> Wed Sep 27 17:36:53 2017 >>> www-client/chromium-61.0.3163.100 |
7 |
> merge time: 6 hours, 40 minutes and 50 seconds. |
8 |
> |
9 |
> Thu Nov 9 17:44:58 2017 >>> www-client/chromium-62.0.3202.89 |
10 |
> merge time: 8 hours, 12 minutes and 30 seconds. |
11 |
> |
12 |
> -->switch to gcc-6.4.0 |
13 |
> |
14 |
> Mon Dec 4 11:39:36 2017 >>> www-client/chromium-62.0.3202.89 |
15 |
> merge time: 20 hours, 2 minutes and 4 seconds. |
16 |
> |
17 |
> Wed Dec 6 18:41:13 2017 >>> www-client/chromium-62.0.3202.94 |
18 |
> merge time: 22 hours, 47 minutes and 35 seconds. |
19 |
|
20 |
Did the CPU throttling stuff somehow get broken when you updated to |
21 |
gcc-6.4.0? After updating a bunch of stuff a month or two back, I |
22 |
noticed that builds suddently took 4X as long. I finally realized |
23 |
that I had broken the CPU throttling feature and my laptop was always |
24 |
running at 400MHz and not ramping up to 2.<whatever> GHz when doing |
25 |
things like compiling large packages. |
26 |
|
27 |
-- |
28 |
Grant Edwards grant.b.edwards Yow! I'm using my X-RAY |
29 |
at VISION to obtain a rare |
30 |
gmail.com glimpse of the INNER |
31 |
WORKINGS of this POTATO!! |