| 1 |
On Wednesday, 6 December 2017 21:01:25 GMT Grant Edwards wrote: |
| 2 |
> On 2017-12-06, Mick <michaelkintzios@×××××.com> wrote: |
| 3 |
> > I discovered that building Chromium with gcc-6.4.0 is taking an |
| 4 |
> > inordinately> |
| 5 |
> > longer time on a laptop with 1st gen i7 and 4G of RAM, e.g.: |
| 6 |
[snip ...] |
| 7 |
|
| 8 |
> Did the CPU throttling stuff somehow get broken when you updated to |
| 9 |
> gcc-6.4.0? After updating a bunch of stuff a month or two back, I |
| 10 |
> noticed that builds suddently took 4X as long. I finally realized |
| 11 |
> that I had broken the CPU throttling feature and my laptop was always |
| 12 |
> running at 400MHz and not ramping up to 2.<whatever> GHz when doing |
| 13 |
> things like compiling large packages. |
| 14 |
|
| 15 |
Hmm ... I have not changed anything related to CPU throttling I can remember. |
| 16 |
Which reminds me, perhaps I should 'make clean' my kernel now that I have |
| 17 |
switched to gcc-6.4.0? |
| 18 |
|
| 19 |
i7z shows turbo mode kicks in too and hyperthreading is on (attached). Under |
| 20 |
turbo it jumps up to 2.8GHz. So cpu throttling is probably not the cause of |
| 21 |
my problem, unless it throttles more now than it used to do before? :-/ |
| 22 |
|
| 23 |
-- |
| 24 |
Regards, |
| 25 |
Mick |
Archives