Hi TurboGears users,

I am trying to profile my (TurboGears) application using the CherryPy
profiling option. Unfortunately I have some trouble figuring out what
is happening.

It seems like the _build_dispatcher method in functions.py (which I
guess is a RuleDispatch file) is always responsible for most of the
CPU usage. Is this because some voodoo is happening in TurboGears/
RuleDispatch which prevents the profiler from seeing what functions
are really spending my precious CPU cycles;-)

Any suggestions on how to proceed? Maybe I need to place profiling
code inside my controller methods (but that is a bit cumbersome)?

Best regards,
Jesper

Example profile:

         2345 function calls (2294 primitive calls) in 0.504 CPU
seconds

   Ordered by: cumulative time

   ncalls  tottime  percall  cumtime  percall
filename:lineno(function)
        1    0.000    0.000    0.504    0.504 profile:0(<bound method
Request._run of <cherrypy._cphttptools.Request object at 0x126f644c>>)
        1    0.000    0.000    0.504    0.504 _cphttptools.py:92(_run)
        1    0.000    0.000    0.476    0.476 _cphttptools.py:
251(main)
        1    0.000    0.000    0.472    0.472 <string>:2(nwp)
        1    0.000    0.000    0.472    0.472 controllers.py:
347(expose)
        1    0.000    0.000    0.452    0.452 strategy.py:
214(__init__)
        2    0.452    0.226    0.452    0.226 functions.py:
330(_build_dispatcher)
        1    0.000    0.000    0.452    0.452 strategy.py:196(mkNode)
        1    0.000    0.000    0.452    0.452 <string>:
4(run_with_transaction)
        3    0.000    0.000    0.016    0.005 filters/__init__.py:
111(applyFilters)
...
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to