Changes between Version 10 and Version 11 of ProfilingDjango


Ignore:
Timestamp:
12/03/2010 03:37:23 AM (5 years ago)
Author:
sebastian_noack
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProfilingDjango

    v10 v11  
    106106=== Middleware ===
    107107
    108 [http://www.djangosnippets.org/snippets/186/ Profiling Middleware] and [http://www.djangosnippets.org/snippets/605/ Extended Profiling Middleware] print profile results for method, additionally groups results by files and by modules. Add the "&prof=" query parameter and you'll see the profiling results in your browser.
     108[http://www.djangosnippets.org/snippets/186/ Profiling Middleware] and [http://www.djangosnippets.org/snippets/605/ Extended Profiling Middleware] print profile results for method, additionally groups results by files and by modules. Add the "&prof=" query parameter and you'll see the profiling results in your browser. Unfortunately, these are both items on Django Snippets, so you should treat them as being untested abandonware, or, more charitably, example code.
    109109
    110 Unfortunately, these are both items on Django Snippets, so you should treat them as being untested abandonware, or, more charitably, example code.
     110There is another unofficial [http://www.no-ack.org/2010/12/yet-another-profiling-middleware-for.html profiling middleware], that attaches the profiler stats enclosed by a comment at the bottom of each HTML, XML and JSON document. That is useful in particular when profiling AJAX requests or when you want to watch the actual content and the profiler stats at the same time.
    111111
    112112[http://code.google.com/p/django-profiling/ django-profiling] seems to be another variant of the profiling middleware, which declares itself superseded by [http://code.google.com/p/django-logging/wiki/Overview django-logging], which declares itself unmaintained.
Back to Top