On 4/18/06, Jason Chu <[EMAIL PROTECTED]> wrote: > 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.
Yes, we noticed this during the sprint. I agree that this should be an option and it should default to off. > 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. Are you using XML()? I've gathered that that is slower than creating an elementtree yourself outside of Kid. > I don't know where else to look for optimizations. Any ideas? I believe there's a branch that David Stanek and Mike Pirnat were working on during the sprint. I don't believe it's done, though. It was doing some pretty aggressive changes. Kevin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
