On Wednesday, 6 December 2017 21:01:25 GMT Grant Edwards wrote: > On 2017-12-06, Mick <michaelkintz...@gmail.com> wrote: > > I discovered that building Chromium with gcc-6.4.0 is taking an > > inordinately> > > longer time on a laptop with 1st gen i7 and 4G of RAM, e.g.: [snip ...]
> Did the CPU throttling stuff somehow get broken when you updated to > gcc-6.4.0? After updating a bunch of stuff a month or two back, I > noticed that builds suddently took 4X as long. I finally realized > that I had broken the CPU throttling feature and my laptop was always > running at 400MHz and not ramping up to 2.<whatever> GHz when doing > things like compiling large packages. Hmm ... I have not changed anything related to CPU throttling I can remember. Which reminds me, perhaps I should 'make clean' my kernel now that I have switched to gcc-6.4.0? i7z shows turbo mode kicks in too and hyperthreading is on (attached). Under turbo it jumps up to 2.8GHz. So cpu throttling is probably not the cause of my problem, unless it throttles more now than it used to do before? :-/ -- Regards, Mick
Cpu speed from cpuinfo 1595.00Mhz
cpuinfo might be wrong if cpufreq is enabled. To guess correctly try estimating
via tsc
Linux's inbuilt cpu_khz code emulated now
True Frequency (without accounting Turbo) 1595 MHz
CPU Multiplier 12x || Bus clock frequency (BCLK) 132.92 MHz
Socket [0] - [physical cores=4, logical cores=8, max online cores ever=4]
TURBO ENABLED on 4 Cores, Hyper Threading ON
Max Frequency without considering Turbo 1727.92 MHz (132.92 x [13])
Max TURBO Multiplier (if Enabled) with 1/2/3/4 Cores is 21x/18x/13x/13x
Real Current Frequency 2564.92 MHz [132.92 x 19.30] (Max of below)
Core [core-id] :Actual Freq (Mult.) C0% Halt(C1)% C3 % C6 %
C7 % Temp VCore
Core 1 [0]: 1666.27 (12.54x) 12.5 5.72 22.8 58.4
0 62 0.0000
Core 2 [1]: 1615.74 (12.16x) 11.1 6.62 12.8 69.3
0 62 0.0000
Core 3 [2]: 1747.37 (13.15x) 14.5 5.95 13.9 64.3
0 62 0.0000
Core 4 [3]: 2564.92 (19.30x) 99.4 0 0 0
0 72 0.0000
C0 = Processor running without halting
C1 = Processor running with halts (States >C0 are power saver modes with cores
idling)
C3 = Cores running with PLL turned off and core cache turned off
C6, C7 = Everything in C3 + core state saved to last level cache, C7 is deeper
than C6
Above values in table are in percentage over the last 1 sec
[core-id] refers to core-id number in /proc/cpuinfo
'Garbage Values' message printed when garbage values are read
signature.asc
Description: This is a digitally signed message part.
