On 14:24 Sat 06 Dec , Alastair Tse wrote: [...] > However, that python startup time is negligible compared to calling > "import portage" where it loads the portdb from disk. For instance, the > newest portage calls portageq continuously, and every instance of it > does "import portage" which is really slow on my machine. When I say > slow, that is a bit more than 2 seconds (5 seconds before disk cache). > But if it runs that for every package I have in world, then that is > 461*2 ~ 920seconds just for calling "import portage". [...]
Unless it creates a new python process every time -- calling "import portage" multiple times within a python runtime will only load the portage library once. Which, from looking at ebuild.sh it appears to reload the portage library constantly (in the case I think you meant to describe), which implies bad design and another reason (as drobbins stated) portage's performance hit pertains to a reliance on bash. Again, another reason working on portage modularisation pertains to greater speed and better design... ;) -- -------------------------~ ----------Jason-A-Mobarak-~ -aether-at-gentoo-dot-org-~ -------------------------~ -- [EMAIL PROTECTED] mailing list
