> There are plenty of scenarios where using more jobs than processor threads
results in faster builds: it all depends You say that because you have tested
it or because you believe it? I have tested it, But let's bust this
ludicrous idea and show us a test that disproves me. Here is slightly improved
test script > However, -j without any limit works the way it does because
it is intended to be used in conjunction with -l. I don't necessarily use
it as I tried and have not seen any difference, but if you explain what it does
I can prepare a test to actually examine it. But anyway I don't disagree
that the number of processor threads is a
good default metric. I don't disagree with some heuristic, based on
number of available threads, deciding what is best. I'm not the first one
to propose that[1], it turns out. There is something in it making people try
it. Only difference is - I don't propose to make new command line option;
rather to utilize existing one. -- 1. lists.gnu.org
https://lists.gnu.org/archive/html/bug-make/2011-01/msg00020.html -- Regards
