When doing performance audits, an annoying feature of Pyramid is that it's not very easy to pinpoint where the slow part is.
I'd like to suggest some sort of logging facility for the internal request lifecycle there are a handful of things that I think could provide useful metrics, either displayed via a debugtoolbar widget, or logged elsewhere via tween. i don't think this would be possible without hooks directly into pyramid though. off the top of my head, these are the things I think would be useful: - time spent on request setup (parsing cookies, loading sessions, etc) - time spent on auth decorators - time spent within a request dispatch - time spent within pyramid.renderers functions while time spent within a request would be inclusive of rendering, it would be simple to subtract the rendering time time spent on rendering calls would probably need to be logged as an array (it's possibly to have multiple calls to `render`) the reason why this is something that i'm interested in, is that the various templating languages currently supported by pyramid allow raw python, so it's possible for slow or blocking code to sneak into them. i just wanted to start some dialog or brainstorming on this. -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.
