FYI, another profiler. (I mentioned repoze.profiler earlier in the thread)
-------- Original Message --------
Subject: Re: ProfileMiddleware logging
Date: Thu, 30 Oct 2008 16:24:56 +0000
From: Stephen Emslie <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
fwiw, I'm in the early stages of building a web interface for
profiling wsgi apps in the same vein as Ian's excellent debugger. The
idea is to make some of the functionality of the pstats module a
little more accessible as a piece of middleware.
If you're not afraid of trying out new code then 0.1dev is available
on the cheese shop: http://pypi.python.org/pypi/WSGIProfile
I've also started a little documentation at
On Thu, Oct 30, 2008 at 4:08 PM, Ian Bicking <[EMAIL PROTECTED]> wrote:
> Pavel Skvazh wrote:
>> I'm having problems integrating it..
>> Anyway, isn't paste.profile supposed be bale to log everything it
>> to the console to the log file?
>> Probably I've missed something along the lines, but it looks like it
>> list of my packages, which makes very little sense.
>> from paste.debug.profile import ProfileMiddleware
>> app = ProfileMiddleware(app, log_filename='/profile.log')
>> app = RoutesMiddleware(app, config['routes.map'])
>> app = SessionMiddleware(app, config)
>> app = CacheMiddleware(app, config)
>> No matter if I plug it first or last, it logs everything the way it's
>> to into the console and something meaningless to the log file.
> The log file is just some stats that is then parsed by hotshot.stats --
> you could potentially parse it entirely separately. But I think it also
> clears it every request.
> I'm afraid there's no configuration in it for actually printing stats
> elsewhere or aggregating statistics.
Repoze-dev mailing list