On Sat, Sep 26, 2009 at 04:02:22PM +0200, Michael Budde wrote: > I've attached a small patch that removes some debug output from the > `be --complete'
On Sat, Oct 17, 2009 at 11:51:59AM +0200, Bruno Bord wrote: > See as an attached file a patch opening a new bug about performance. Whoa, what sort of time warp did these drop out of? :p. I think Michael's patch is no longer applicable. Bruno's bug looks similar to Jakub Wilk's Debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559295 addressed in [email protected] although speed tweaking is always useful... On my 3.40GHz P4 for my current be.wtk branch, `be list' gives wk...@thor:be.wtk$ time ./be list ... real 0m3.902s user 0m0.168s sys 0m0.040s After the first call (once everything is in memory?), calls to `be list` only take about 1.2s. This seems reasonable to me, but the current VCS backends won't scale well to thousands of bugs. I think the solution to this is either to follow Ditz, and cache closed/fixed bugs in an "archive" directories where we won't query them unless specifically asked, or to generate and cache indexes rather than performing searches on demand. Anyhow, the current BE should be faster than 5 seconds, so do we still want to merge Bruno's bug? -- 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
pgpAbJfN7Qlz9.pgp
Description: PGP signature
_______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
