I was checking out the status of BE on Debian and I ran across this bug complaining about the speed of `be`: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559295
Doing a little profiling, I found that most of the time it takes to process `be` goes into building all the test suites. I added TESTING to libbe/__init__.py to avoid building those tests unless they're needed. This cut the execution time for `be` about in half. I also reduced the number of Popen() calls that happen when initializing and loading a BugDir with a Popen()-based backend (which is all of them except vcs.VCS). This reduced the execution time for `be list` about in half. Another possible optimization for the bzr backend would be to move bzr from Popen() calls to bzrlib. This would almost certainly speed things up for the bzr backend. On the other hand, someone would have to learn enough about bzrlib to replace the current Bzr._u_invoke_client() calls. Similar optimizations should be possible for hg, the other Python-based backend. If anyone has other ideas for speeding things up that don't require too much voodoo, let us know :). -- This email may be signed or encrypted with GPG (http://www.gnupg.org). The GPG signature (if present) will be attached as 'signature.asc'. For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt
pgpzoOB0FdDFd.pgp
Description: PGP signature
_______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
