i'd also like something like that to have better context. for
example, there are some views that have to finish quickly, and others
that could take longer. the database logs don't discriminate between
those, so it's not easy to see which queries are more important to
optimize.
and of course, it's not always easy to know which ORM produced which
SQL. knowing which Python code produced each SQL means a lot less
guesswork.
--
Javier
--
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-d...@googlegroups.com.
To unsubscribe from this group, send email to django-develop...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
There are times when the ORM produces SQL that is not what I expect,
and I often don't realize this until I go and look at the slow query
log, which is usually after the project is already in some stage of
production or at least staging.
Thus, I do think there is some room for a simple performance tool to
help with this situation, although Alex's point that performance
logging is an industry unto itself it sound. Is there a well-defined
bite that can be chewed?
--
Justin Holmes
Head Instructor, SlashRoot Collective
SlashRoot: Coffee House and Tech Dojo
60 Main Street
New Paltz, NY 12561
845.633.8330