On 4/18/06, Jason Chu <[EMAIL PROTECTED]> wrote:
Yeah that can probably be easily added to TurboKid.
I ran a profiler over my app today (again, getting ready for release)
and found that kid takes a significant time doing its processing.
One thing that sped things up was turning off balanced_blocks. I think
we really should have a config file option for that one.
Yeah that can probably be easily added to TurboKid.
I'm finding now that ElementStream._pull, _coalesce, and _track are the
functions that are taking the most time total, but they're pretty
speedy on individual calls.
I don't know where else to look for optimizations. Any ideas?
As Kevin said in another message, we are working on some significant changes in the pycon2006 branch. There are only two unit tests failing at this point. I can't guarantee that the changes will make things much faster, but it does simplify the logic quite a bit. So from there we can start cutting away until we get to blazing speed!
I may just end up committing the broken branch so that others can help me out...I am going on vacation for a week so I don't expect to have much internet access.
--
David
http://www.traceback.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears
-~----------~----~----~----~------~----~------~--~---
