Changes between Version 6 and Version 7 of ProfilingDjango

Timestamp:

Jul 30, 2007, 5:58:02 AM (18 years ago)

Author:

Michael Twomey <micktwomey@…>

Comment:

Showing an alternative profiling approach using WSGI and wsgiref

ProfilingDjango

@@ -13 +13 @@
 
 You can also use [http://code.djangoproject.com/browser/django/trunk/django/bin/profiling/gather_profile_stats.py gather_profile_stats.py] in the Django distribution to aggregate the generated profilings and open them with pstats.Stats
+
+== Using WSGI to profile ==
+
+An alternative approach is to run django from a boring WSGI server and profile that. For example using wsgiref you can create a really simple WSGI server for running django:
+
+{{{
+from wsgiref.simple_server import make_server
+from django.core.handlers.wsgi import WSGIHandler
+httpd = make_server('', 8000, WSGIHandler())
+httpd.serve_forever()
+}}}
+
+Run this using:
+
+{{{
+$ DJANGO_SETTINGS_MODULE=mysite.settings python myserver.py 
+}}}
+
+To profile this run using cProfile (or profile):
+
+{{{
+$ DJANGO_SETTINGS_MODULE=mysite.settings python -m cProfile myserver.py 
+}}}
+
+The default invocation will print the profile stats when you kill the server, it's probably more useful to write to a file and use pstats to read it:
+
+{{{
+$ DJANGO_SETTINGS_MODULE=mysite.settings python -m cProfile -o mysite.profile myserver.py 
+... lots of requests ...
+
+$ python
+>>> import pstats
+>>> s = pstats.Stats("mysite.profile")
+>>> s.sort_stats("time").print_stats(20)
+}}}
+