| 1 |
On 01/27/2011 04:53 PM, Neil Bothwick wrote: |
| 2 |
> On Thu, 27 Jan 2011 16:30:30 +0200, Nikos Chantziaras wrote: |
| 3 |
> |
| 4 |
>>> Using --jobs does a better job of making use of your CPU because one |
| 5 |
>>> package can use it fully for compiling while another is configuring. |
| 6 |
>> |
| 7 |
>> And what about the last package? The time you gained for faster |
| 8 |
>> configure and install (which don't take too much time anyway) is wasted |
| 9 |
>> again on the last package. |
| 10 |
> |
| 11 |
> So on a 20 package world update, only 19 are faster while the 20th runs |
| 12 |
> at the same speed? Where's the loss there? Even if the last were slower, |
| 13 |
> it would be worth it. |
| 14 |
|
| 15 |
Given the amount of time unpack/configure/install of most packages needs |
| 16 |
(very short), my observation is that it would not be worth it. |
Archives