CPU usage during compilation

[d.healey]

When I'm compiling I've noticed my CPU drops to 1Ghz (or there about) and the cores are running at 100%. Is this normal? What's everyone else's experience?

[iamlamprey]

Mine only get to 14% during the earlier compile stages, and spike to 40ish% at Generating Code on an oldish i7

[d.healey]

@iamlamprey And what speed does it run at?

[iamlamprey]

@d-healey Sits around 4ghz

[d.healey]

@iamlamprey Thanks, something freaky going on with my CPU...

[iamlamprey]

@d-healey Are the temps freaking out too?

[d.healey]

@iamlamprey Nope 40C

[iamlamprey]

@d-healey very weird, could maybe be an IPP thing? shooting in the dark at this point

[d.healey]

@iamlamprey

Not using IPP. I think it's a crappy CPU

[Lindon]

@d-healey I've spent a fair while thinking about getting another machine - so I spent another fair while looking at the Task Manager and performance manager in Windows as I run a compile(I'd like to find out if I'm CPU, memory or disk bound) , and there's all sorts of strangeness's going on.....CPU does spike at 100% here (i5 family but on windows) but so does memory and the disk (tho its not SSD so hey...)

[DanH]

@Lindon Mac Mini 2018 i7 here, cpu and temp always go way up when compiling. Only takes about 5 mins to compile though and its a very big plugin. Don't know if that's good or not...

[d.healey]

@DanH Doesn't help me

[ospfeigrp]

i have just built scriptnode and compiled a plugin on neon latest linux dist with dual xeon 2680 v3 it's a 24 core systemwith 32 gb ddr4 ram and still incredibly slow, on the same hardware running win 10 seems to fly but on a linux distro seems slow for some reason

[d.healey]

@ospfeigrp Did you enable all threads? i.e -j 44 (assuming 2 threads per core) ?

[ospfeigrp]

@d-healey nope, i did not thanks for that. so i would use:

make CONFIG=Release -j 48

Edit: i just compiled the plugin version of hise scriptnode with -j40 and it finished in around one minute

[d.healey]

@ospfeigrp I usually leave a few threads available for the system to do other things but use all 48 if you want

[ospfeigrp]

@d-healey thanks, I just try recompiling HISE standalone with -j 40 and it's very slow around "Linking HISE standalone - App" this time it took 8 minutes for the standalone.

[d.healey]

Linking is always single threaded with gcc/g++

[d.healey]

This might be a solution worth investigating for multi-threaded linking - https://lld.llvm.org/

[d.healey]

I found what was causing my CPU issues. The CPU was power throttling. I've increased the power limits and now I'm getting much better clock speed when compiling.