Version 7 (modified by Michael Twomey <micktwomey@…>, 8 years ago) (diff)

Showing an alternative profiling approach using WSGI and wsgiref

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 Django profiling with hotshot and kcachegrind for more details.

Here's a similar solution for the internal development webserver. Apply the included patch to django/core/ and start Django with runserver. Each request will create a .prof file in your /tmp directory. You can then open a Python shell and print the statistics:

>>> import hotshot.stats
>>> stats = hotshot.stats.load("")
>>> stats.strip_dirs()
>>> stats.sort_stats('time', 'calls')
>>> stats.print_stats(20)

You can also use 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())

Run this using:

$ DJANGO_SETTINGS_MODULE=mysite.settings python 

To profile this run using cProfile (or profile):

$ DJANGO_SETTINGS_MODULE=mysite.settings python -m cProfile 

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 
... lots of requests ...

$ python
>>> import pstats
>>> s = pstats.Stats("mysite.profile")
>>> s.sort_stats("time").print_stats(20)

Attachments (5)

Download all attachments as: .zip

Back to Top