1 |
On Thu, Apr 28, 2005 at 06:40:23PM +0200, Heinrich Wendel wrote: |
2 |
> Hi, |
3 |
> |
4 |
> Portage is slow? How to make it faster? By removing unused ebuilds! |
5 |
Define "faster". All this would do is cut down on a couple of stats |
6 |
per pkg; the # of ebuilds per pkg isn't a huge issue, the scanning of |
7 |
vdb and Config initialization is what is damned slow. :) |
8 |
|
9 |
> I wrote a little script to check which ebuilds in portage aren't used |
10 |
> anylonger, here the result: |
11 |
> |
12 |
> Total packages checked: 9076 |
13 |
> Total ebuilds checked: 18662 |
14 |
> Total ebuilds to remove: 4643 |
15 |
|
16 |
Dropping every ebuild that isn't the highest version for the mismash |
17 |
of arches isn't really valid. Granted, people *could* stand to do |
18 |
cleansing of old versions in the tree, but the versions they choose to |
19 |
support/offer is completely up to the ebuild dev. |
20 |
|
21 |
> Of course the script can't detect every ebuild situation, so take the numbers |
22 |
> with care. But still it shows that 1/4 of all ebuilds could be removed. This |
23 |
> would improve portage performance by at least 1/4 |
24 |
Again, define what aspect of portage performance. The only thing less |
25 |
ebuilds cuts down on is the avg runtime of a cp_list call; cache is |
26 |
keyed, so lookup is *typically* constant. |
27 |
~brian |
28 |
-- |
29 |
gentoo-dev@g.o mailing list |