From: Keith.S.Thompson+u@gmail.com   
      
   antispam@fricas.org (Waldek Hebisch) writes:   
   [...]   
   > Assuming that you have enough RAM you should try at least using   
   > 'make -j 3', that is allow make to use up to 3 jobs.  I wrote   
   > at least, because AFAIK cheapest PC CPU-s of reasonable age   
   > have at least 2 cores, so to fully utilize the machine you   
   > need at least 2 jobs.  3 is better, because some jobs may wait   
   > for I/O.   
      
   I haven't been using make's "-j" option for most of my builds.   
   I'm going to start doing so now (updating my wrapper script).   
      
   I initially tried replacing "make" by "make -j", with no numeric   
   argument.  The result was that my system nearly froze (the load   
   average went up to nearly 200).  It even invoked the infamous OOM   
   killer.  "make -j" tells make to use as many parallel processes   
   as possible.   
      
   "make -j $(nproc)" is much better.  The "nproc" command reports the   
   number of available processing units.  Experiments with a fairly   
   large build show that arguments to "-j" larger than $(nproc) do   
   not speed things up (on a fairly old machine with nproc=4).  I had   
   speculated that "make -n 5" might be worthwhile of some processes   
   were I/O-bound, but that doesn't appear to be the case.   
      
   This applies to GNU make.  There are other "make" implementations   
   which may or may not have a similar feature.   
      
   [...]   
      
   --   
   Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com   
   void Void(void) { Void(); } /* The recursive call of the void */   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)