bzr is such a small (code size wise, compared to some other python beasts) that I don't think it's a concern, but nonetheless I'll bear it in mind in my future testing. <div>On 3/5/06, Diwaker Gupta <<a href="mailto:diwaker.lists@gmail.com">diwaker.lists@gmail.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> The memory overhead of Psyco is something to bear in mind. This is from the website: "The memory overhead of Psyco is currently large. I has been reduced a bit over time, but it is still an overhead. This overhead is proportional to the amount of Python code that Psyco rewrites; thus if your application has a few algorithmic "core" functions, these are the ones you will want Psyco to accelerate --- not the whole program." Diwaker On 3/5/06, Martin Pool <<a href="mailto:mbp@sourcefrog.net">mbp@sourcefrog.net</a>> wrote: > > On 2006-03-06 Mon, at 10:32 AM, Ivan Krstic wrote: > > > John Dong wrote: > >> Below is the quick patch I made; if psyco is installed, it'll use > >> it in > >> the unobtrusive background profiling mode. > > > > Using it in background profiling mode is rather inefficient, as psyco > > has to learn what to pseudo-JIT on every bzr invocation. It would be > > better to do some profiling and psyco a few specific code paths > > that can > > benefit from it, and where bzr spends a significant portion of its > > running time. > > > > If Rob and Martin support adding some psyco directives to bzr, this > > would be a neat and very quick little project for you to pick up. > > I have no objection. > > -- > > Martin Pool > > > > > -- Web/Blog/Gallery: <a href="http://floatingsun.net/blog">http://floatingsun.net/blog</a> </blockquote></div>