I’ve become somewhat of a Django ninja during my time as GradeSolve’s developer (okay, a Django hacker…). One of the things that I have noticed as I have written several thousand lines of Django code is that SQL queries tend to be made pretty regularly–often, a little too regularly. Some of GradeSolve’s pages were loading a little slowly for my tastes, so I decided to do some basic SQL profiling to see where the trouble was.
The issue there was that django-debug-toolbar didn’t want to play nice, and I lacked the motivation to try to get it working. Instead, I re-invented the wheel a little bit and write a simple piece of middleware to print out the SQL execution time and number of SQL queries made for a particular request. Obviously, this is going to go away in the production version of GradeSolve (which is being released in eight days!), but for the time being, I like the extra information on my debug console.
Anyway, here’s the middleware class. Stick this in one of your project’s files:
from django.db import connection class SqlPrintMiddleware(object): def process_response(self, request, response): sqltime = 0 # Variable to store execution time for query in connection.queries: sqltime += float(query["time"]) # Add the time that the query took to the total # len(connection.queries) = total number of queries print "Page render: " + unicode(sqltime) + "sec for " + unicode(len(connection.queries)) + " queries" return response
Now, in your settings.py file, add the path to the middleware class. For example, if your project’s name is gradesolve and your file’s name is middleware.py, your middleware classes setting would end up looking like:
MIDDLEWARE_CLASSES = ( # ... 'gradesolve.middleware.SqlPrintMiddleware', # ... )
Happy (very simple) profiling!