On Thu, 27 Jan 2011 16:30:30 +0200, Nikos Chantziaras wrote: > > Using --jobs does a better job of making use of your CPU because one > > package can use it fully for compiling while another is configuring. > > And what about the last package? The time you gained for faster > configure and install (which don't take too much time anyway) is wasted > again on the last package.
So on a 20 package world update, only 19 are faster while the 20th runs at the same speed? Where's the loss there? Even if the last were slower, it would be worth it. Note that I never use --jobs without an argument, 2 by default, although I could let emerge decide how many parallel processes to run. -- Neil Bothwick Top Oxymorons Number 47: Act naturally
signature.asc
Description: PGP signature
