| 1 |
No, it's not just you, running "emerge -uNDvp world" takes slightly |
| 2 |
over 18 minutes on my laptop (i5 M 430 @ 2.27GHz) - and when there |
| 3 |
was lot to update I had to wait over 1hr to just get the list of |
| 4 |
packages. I wonder if there's some profiling tool for portage. |
| 5 |
Also: |
| 6 |
time FEATURES=-xattr emerge owncloud -v |
| 7 |
real 6m31.202s |
| 8 |
user 2m42.057s |
| 9 |
sys 2m1.541s |
| 10 |
|
| 11 |
time FEATURES=xattr emerge owncloud -v |
| 12 |
real 30m15.632s |
| 13 |
user 22m44.369s |
| 14 |
sys 5m30.129s |
| 15 |
|
| 16 |
5 times longer - for something that's essentially copying files. |
| 17 |
|
| 18 |
|
| 19 |
On 26 January 2014 15:35, Nikos Chantziaras <realnc@×××××.com> wrote: |
| 20 |
> Anyone else noticed this yet? Some portage update seems to have made "emerge |
| 21 |
> -uDN @world" perform about 10 times slower than before. It used to take |
| 22 |
> seconds, now it takes about 4 minutes only to tell me that there's nothing |
| 23 |
> to update. And it does that every time, even directly in succession and with |
| 24 |
> the caches warm. |
| 25 |
> |
| 26 |
> Is it just me? |
| 27 |
> |
| 28 |
> |
Archives