Allan Sandfeld Jensen wrote:
> It only launches one ninja process, and ninja guesses the number threads
> itself by using cpuinfo (unless you control it with NINJAFLAGS), but that
> can't get load to 60. I would guess the load is not from CPU, but maybe memory
> load, if you start swapping other
On Saturday 19 March 2016, René J.V. Bertin wrote:
> Hi,
>
> This seems a bit silly to ask, but I'm seeing extremely high load averages:
> 60.74 53.07 41.45 building QtWebEngine (about 8100 files in). That's on a
> 2 core, 2 thread i7, with the build started with make -j4 . I'm indeed
> seeing mor
Hi,
This seems a bit silly to ask, but I'm seeing extremely high load averages:
60.74 53.07 41.45 building QtWebEngine (about 8100 files in).
That's on a 2 core, 2 thread i7, with the build started with make -j4 . I'm
indeed seeing more than 4 concurrent clang processes and nothing else that
ta
