The django application I am working on is very slow on the server-side, and I want to know why.
The essence is to identify which code-parts of processing one request take most time.
The app runs with mod_wsgi on Apache, here is what I tried:
- django-timelog: the information logged is too unspecific and high-leveled. I want to know which functions and parts of a view require most time. (moreover, analyze_timelog doesn't work here)
- django-debug-toolbar with profiling from http://backslashn.com/post/505601626/ - too fine-grained:
I do not want to know that 138752 calls to python2.6/posixpath.py:129(islink) take 0.858 seconds. I want to know in which views / functions it happens.
- profiling with wsgiref, like described in https://code.djangoproject.com/wiki/ProfilingDjango#no1 - looks like (and probably is?) exactly the same output as the django-debug-toolbar with profiling: too fine-grained, I want to get an overview, not the pure low-level calls.
What is your preferred way to analyze/profile the performance of django-applications?
thanks,
Michael
Wednesday, October 12, 2011
Profiling Django
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment