Comment 4 for bug 808930

From IRC:

<abentley> danilos: I think the way to close this bug is to optimize bzr.
 danilos: I would start by downloading the branch locally and profiling the script.
<abentley> danilos: it is already using the fastest bzrlib operations I know of. I wrote the script, and I also wrote the Graph operations, several years before that.
<abentley> danilos: it's possible the algorithm could be improved. it's also possible that we have to switch to C or Pyrex to get that performance.
 danilos: Or we may need to implement a greatest-distance-from-origin cache in order to get good performance.
 danilos: jam has also done a lot of work in this area, and may have advice.

(note that the above OOPSes are not available yet because it seems our OOPS scanner is not scanning ackee OOPSes yet)