1 |
On Sun, 26 Jan 2014 16:35:43 +0200, Nikos Chantziaras |
2 |
<realnc@×××××.com> wrote: |
3 |
>Anyone else noticed this yet? Some portage update seems to have made |
4 |
>"emerge -uDN @world" perform about 10 times slower than before. It |
5 |
>used to take seconds, now it takes about 4 minutes only to tell me |
6 |
>that there's nothing to update. And it does that every time, even |
7 |
>directly in succession and with the caches warm. |
8 |
> |
9 |
>Is it just me? |
10 |
|
11 |
You don't say when your baseline was, but the complexity of resolving |
12 |
the package tree has increased quite a bit over the last year due to |
13 |
new features like automatic rebuilds of consumers after library updates. |
14 |
|
15 |
Another somewhat common cause of sudden slowdowns is how portage |
16 |
resolves conflicts (like packageA requiring an old version of libraryB), |
17 |
which is rather time-consuming. You can try adding --backtrack=0 to the |
18 |
emerge command to make it stop and print an error message when |
19 |
encountering a conflict rather than look for a solution. Then you can |
20 |
'help' out by manually resolving any conflicts by adding package |
21 |
versions to /etc/portage/package.mask . Preferably try this *after* |
22 |
running an update, so your system is up-to-date against your local |
23 |
version of the gentoo tree, otherwise "normal" simple-to-resolve |
24 |
conflicts might cause confusion. ;-) |
25 |
|
26 |
-- |
27 |
eroen |