On Tuesday, 14 April 2015 at 12:07:18 UTC, Russel Winder wrote:
On Tue, 2015-04-14 at 08:53 +0000, Atila Neves via
Digitalmars-d wrote:
[…]
The "-j" option should be there for tweaking only, by default
I expect a modern tool to just use as many threads as I have
cores. Which of course is exactly what Ninja does.
N-1 not N on a system you are using as a workstation. N on a
compiler
server, no problem.
Waf chooses N and it makes the workstation unusable whilst the
compilation is happening.
[…]
Sounds like your scheduler is messing up.
Compiling is CPU intensive when UI isn't. Meaning the compiling
process should burns its CPU time while UI process is mostly
idle. Meaning UI thread should take over when it needs to, as per
most scheduler policies.
