| 1 |
On Sat, 17 Jan 2015 19:35:09 +0800 Patrick Lauer wrote: |
| 2 |
> * Portage is too slow |
| 3 |
> On 'small' hardware emerge -upNDv @world can take enough time |
| 4 |
> to make updates prohibitive - on an 800Mhz machine it took me |
| 5 |
> about 3 days to figure out a solution to some silly blockers due to the |
| 6 |
> very slow change test cycle |
| 7 |
> Fix: Do some profiling and un-refactoring to remove useless code |
| 8 |
> Fix: Set up a reference system (CI) to catch future regressions |
| 9 |
|
| 10 |
There is some progress here. In portage-2.2.15 profile based |
| 11 |
optimizations are included (see bugs 529660, 530010). On my |
| 12 |
hardware (Athlon-XP, 2200 MHz and Intel Atom N270, 1600 MHz) they |
| 13 |
speed up dependency resolution by ~ factor 2. |
| 14 |
|
| 15 |
Of course it will be great to see further optimizations, though as |
| 16 |
far as I remember this will require more complicated changes. |
| 17 |
|
| 18 |
Best regards, |
| 19 |
Andrew Savchenko |
Archives