-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/22/2013 08:38 AM, Allan Wegan wrote: > > Has the bottleneck already been identified? Python should not be > much slower than other languages for solving mostly IO-based > problems.
When you emerge something with a bazillion files, the install wrapper (and thus the python interpreter) get launched that many times. It's the startup time that kills it. I tried to write a 'cp' wrapper once for a similar reason (it doesn't preserve posix ACLs), and it's not as easy as it sounds to just "rewrite it in C" or do the PAX markings after 'install'. The problem you run into is that it's very difficult to figure out where 'install' put the file without reimplementing all of 'install'. But we do have an advantage in portage: we sandbox things before moving them to the real filesystem, so portage actually knows all of the files that will got 'install'ed and where they'll wind up. If we sandbox the PAX markings as well, it should be possible to hit those files with paxctl-ng after they've been moved to the real root. I believe the sandbox option is what Anthony listed here as option #4: https://bugs.gentoo.org/show_bug.cgi?id=465000 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQIcBAEBAgAGBQJSZn3cAAoJEBxJck0inpOi/bQP/2w8+bDmVA6eFLa7Tc35vyxY 8B/N2Ya0Nu1VLG2mbmnEFUKiQxK6I3QNbYckeRqB3g5/6tp4Pp83s0xWQQbcygH+ NhOjCme92JVloYA+Ux8XgC1DF6Ys5cgMFhGpWN4ZH7lsufk21p4CPz5v0yODH32Z lFKqqokeh0EVfHKQYNa/nI65iW/Nz5Dbj1cKqhInZQM7z01fi7Dpy6ZLaQQ3hZyj 2GM8zXPqjGEgVmXf8oHDIbTOnD6//P5n3mWQb1thmb8wIXL7Uyx8lBNa2LkaoA86 q86GxcV6YYed5AEVDdwm+4IWF3bILrsaP4Vm5S5lpUvmfEZqoECwtfxoU2CUHcjO KK2+py10msyV4JUEGxGZCK/u3NJ9h1aQ4e/KvwTa9JBzVwzcaSS7fyHlGpkRFlgh 7vh7Ju91sWz0xH+Uwpt3mwGBPcYoG9LBndCGAgzKRF/uVPZoItX+X4mWo3/2DcEq FqnS6UeWQhew175jRD0TyV2sFODL9isfy37o36ZGLc6LxDShB9v1XQ5aF3VfrlhJ le8u3dC8PoFg4nTy3tL30gf3J65Ms4itdi9MoYrDAL0oNktPXx97erje1QobiViN rQYm4ZKPinEQDDFNP3d2OTXuk6hJclzYgfFxm+uz2EW+NRZn955IbkKmCIQq00I8 e7XMKUgkBOR5L/l5wra6 =kbgW -----END PGP SIGNATURE-----
