WSGI Application Profiler

This module provides a simple WSGI profiler middleware for findingbottlenecks in web application. It uses the profile orcProfile module to do the profiling and writes the stats to thestream provided (defaults to stderr).

Example usage:

  1. from werkzeug.contrib.profiler import ProfilerMiddleware
  2. app = ProfilerMiddleware(app)
  • class _werkzeug.contrib.profiler.MergeStream(*streams_)
  • An object that redirects write calls to multiple streams.Use this to log to both sys.stdout and a file:
  1. f = open('profiler.log', 'w')
  2. stream = MergeStream(sys.stdout, f)
  3. profiler = ProfilerMiddleware(app, stream)
  • class _werkzeug.contrib.profiler.ProfilerMiddleware(_app, stream=None, sort_by=('time', 'calls'), restrictions=(), profile_dir=None)
  • Simple profiler middleware. Wraps a WSGI application and profilesa request. This intentionally buffers the response so that timings aremore exact.

By giving the profile_dir argument, pstat.Stats files are saved to thatdirectory, one file per request. Without it, a summary is printed tostream instead.

For the exact meaning of sort_by and restrictions consult theprofile documentation.

0.9 新版功能: Added support for restrictions and profile_dir.

参数:

  • app – the WSGI application to profile.
  • stream – the stream for the profiled stats. defaults to stderr.
  • sort_by – a tuple of columns to sort the result by.
  • restrictions – a tuple of profiling strictions, not used if dumpingto profile_dir.
  • profile_dir – directory name to save pstat files
  • werkzeug.contrib.profiler.makeaction(_app_factory, hostname='localhost', port=5000, threaded=False, processes=1, stream=None, sort_by=('time', 'calls'), restrictions=())
  • Return a new callback for werkzeug.script that starts a localserver with the profiler enabled.
  1. from werkzeug.contrib import profiler
  2. action_profile = profiler.make_action(make_app)