CherryPy has a profiler built in. Add this to your turbogears .cfg file: profiling.on=True profiling.path="profile"
Then you can start a web page to view the results. python /usr/lib/python/site-packages/cherrypy/lib/profiler.py ./profile inside your turbogears directory. Doesn't allow you to much control over the profiling, but profiler.py is simple enough to edit to your needs. Also note that profiling greatly reducing site performance so only do this on a development system. -Brian On 8/16/07, iain duncan <[EMAIL PROTECTED]> wrote: > > > > In this case (which is a worst case scenario for kid) we did not try > > Genshi because we needed at least an order of magnitude improvement in > > order to get this page to be fast enough for our client's demo and we > > didn't have much time. > > > > But from other cases, I can say that we've seen between 10% and 40% > > performance improvements moving from Kid to Genshi -- and Genshi's had > > quite a few speed improvements since then. > > > > And I should point out that you probably won't get the same crazy > > performance increases from using Mako on every page. > > > > In other smaller page tests with Mako we say between 20x and 50x > > render time improvements. > > > > But in most of the pages we've had to optimize recently, render time > > was already fast enough, and we were held up on database access or > > some other expensive action in our controllers or models. > > Thanks, that's good info. What do you guys use to profile on a page by > page basis? > > Iain > > > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
