On Wed, Jan 28, 2009 at 7:01 AM, Edward K. Ream <[email protected]> wrote:
> > > I'll look into this, but I don't see any great problem with reading my > local leoPy.leo. > There is a bug in profile_leo/cProfile: on XP p = pstats.Stats(name) fails if name is a unicode string. The workaround is to convert name to a plain string. I'll up this fix shortly. Here are the results I get from loading LeoPyRef.leo: 190143 0.629 0.000 1.048 0.000 leoNodes.py:1314(hasNext) 154515 0.640 0.000 6.319 0.000 leoNodes.py:1795(next) 154452 1.992 0.000 5.291 0.000 leoNodes.py:1812(moveToThreadNextUnique) This appears to absolve moveToThreadNextUnique of blame. Leo makes approximately the same number of calls to all three methods, and the time spent in moveToThreadNextUnique thus does not seem particularly out of line. It looks like you have a very slow machine :-) Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
