Changes between Version 7 and Version 8 of ProfilingDjango

Timestamp:

Sep 15, 2009, 5:42:24 AM (15 years ago)

Author:

Antti Kaihola

Comment:

Added links to snippets and apps providing profiling tools

ProfilingDjango

@@ +1 @@
+= Profiling Django =
+
+[http://code.google.com/p/django-command-extensions/ django-command-extensions] provides a `runprofileserver` command for running the development server with hotshot/profiling tools enabled. It has the ability to export [http://kcachegrind.sourceforge.net/ KCacheGrind] compatible profile files.
+
+[http://www.mysoftparade.com/blog/django-profile-sql-performance/ django-profile.py] is a script that can be used to profile any Django-powered web-site and find how many SQL-queries are used per page, how heavy html-pages are, etc.  See also [http://www.djangosnippets.org/snippets/461/ django snippet 461].
+
+[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.
+
+[http://code.google.com/p/django-profiling/ django-profiling] seems to be another variant of the profiling middleware.
+
+----
+
 {{{django.core.handlers.profiler-hotshot}}} provides profiling support for Django when using mod_python. Hotshot generates logs that can be also used by aplication like kcachegrind. Read [http://www.rkblog.rk.edu.pl/w/p/django-profiling-hotshot-and-kcachegrind/ Django profiling with hotshot and kcachegrind] for more details.