[Slackbuilds-users] atlas3.10.3 build fails due to throttling

[Rich Shepard]

On Sat, 25 Feb 2017, B Watson wrote:

> This is fresh in my mind, I just had to do this on my laptop yesterday.

   Thanks to both of you for the answer. I missed seeing it on the SBo page.
I don't recall having this issue when I installed/upgraded atlas on my
32-bit workstation.

> 'performance' still allows the CPU to be throttled, even though the
> comments in rc.cpufreq imply that it doesn't. I ended up using the
> cpufreq-set command in rc.local.

   Huh. Perhaps I should try this on my Dell Latitude E5410 with 4 cores
before moving to the next step.

> It would really be nice if there were a simple option to cpufreq-set
> that means "disable throttling, run at max speed all the time", but
> there isn't one: you can do it, but you have to include the frequency
> on the command line.
> Also, the -r (all hardware-related CPUs) switch seems to be broken. So
> you have to repeat the command for each core. So my rc.local has:
>
> cpufreq-set -c 0 -r -f 1.60GHz
> cpufreq-set -c 1 -r -f 1.60GHz

> The above relies on the userspace governor being available, it's built in
> (not a module) in both the huge and generic kernels.

   Since I don't regularly use atlas (at least, not that I'm aware of using;
I think GRASS is the only tool that wants in sometimes), can I block
throttling to build and install atlas, then unblock it afterwards?

Rich