Hey,
We are in the process of migrating from Django 1.1 to Django 1.2.5 and
I'm investigating a performance slowdown in our unit tests. We see
about a 30% slowdown when running our unit test suite with 1.2.5
versus 1.1. I was just wondering if anyone else had noticed something
similar to this.
Here are some details of what I've investigated so far. I've compared
the time an individual unit test takes to run, as well as the entire
test suite and we consistently see 30-40% increase in the time of
execution with Django 1.2.5 compared to 1.1. It appears the slowdown
happens inside the Django database layer. I've timed tests that have
more complicated database queries as well as simple select statements
that return a large result set as well as a result of 1 and I notice
the difference in the time it takes the test to complete. I've
compared the SQL output from queries running with 1.1 and 1.2
wondering if the SQL was different between the two Django's, but the
SQL is relatively the same. Using cProfile and runsnake, I've been
investigating the profile dump and a difference I notice between 1.2
and 1.1 is that on 1.2, there seems to be more time spent in clone()
in django/db/models/queries.py and django/db/models/sql/queries.py
compared to Django 1.1.
I'm looking for any feedback that anyone has. Have you seen a similar
difference in performance with 1.2.5? Have you narrowed down to where
that would be occurring? I'd appreciate any suggestions that you
have. Our application is ramping up on traffic with the potential for
significant growth coming soon, so we are really concerned about our
performance moving forward.
Thanks in advance!
djeff
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
