On Fri, 2003-12-05 at 11:46, Bob Miller wrote: > Second, is there anything wrong with Python as an implementation > language? If you think Python is too slow, think again. On nearly > every portage operation I do, the CPU is mostly idle -- it's the disk > that's thrashing (according to gkrellm). The key to improving > portage's performance is to get it to open fewer files.
Well, the main thing hurting python's performance is actually bash. In particular, right now we need to use bash to extract metadata reliably from ebuilds. Bash is the single largest performance impediment we have. Without the need for a python <-> bash interface, dep calculation would always be nearly instananeous. Everything else that portage does is so fast compared to the actual compilation or bz2 unpack steps that it really doesn't need to be any faster. Except maybe startup time as Aron mentioned. Regards, Daniel
signature.asc
Description: This is a digitally signed message part
