Hi, Yes that worked well - I added a wrapper around the methods I wanted to profile, and added an extra method to dump out the profile data once I've run my load test.
I can also recommend RunSnakeRun for analysing Python profile dumps. On Oct 22, 1:31 am, David Gardner <[email protected]> wrote: > Not sure I can help much, but what I often do is profile an individual > problematic controller method, > and possibly also the template. > > In other words I usually have an idea of a particular method that I know > to be slow and I start and stop > the profiler within that controller method. Then if that fails to find > something, then I will run the profiler > inside the corresponding template. > > > > James wrote: > > Hey all, > > I'm trying to identify hotspots in a TG1.0 app, following these > > instructions > > here:http://docs.turbogears.org/1.0/RoughDocs/Optimization?highlight=(prof... > > > Unfortunately, the results I get from that trace only seem to show > > information on the startup of TurboGears - not the actual application > > server worker threads. > > > profile (and cProfile) are not able to handle multi-threaded apps > > properly, as far as I remember; is there anything I can do to profile > > the worker threads specifically? > > > Thanks! > > James > > -- > David Gardner > Pipeline Tools Programmer > Jim Henson Creature Shop > [email protected] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
