On 01/27/2011 04:53 PM, Neil Bothwick wrote:
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.
Given the amount of time unpack/configure/install of most packages needs
(very short), my observation is that it would not be worth it.
