On Wed, Apr 7, 2010 at 12:08 PM, Brian Neal <bgn...@gmail.com> wrote:
> I am on trunk, somewhere around revision 127xx and just updated to
> 12936. A couple of my views render this one particular template, which
> used to take less than a second to see a response. Now it is taking
> almost a minute. The Django debug toolbar reports nothing out of the
> ordinary in terms of SQL queries. Something like 12 queries in 6.42
> ms. But user CPU time is nearly 1 minute.
>
> I started removing junk from my template until it started responding
> normally, and I isolated it down to a {% url %} tag. Well, I don't
> think it was just one, maybe a few of them combined was adding up to a
> minute.
>
> <a href="{% url news.views.category category=story.category.id,page=1
> %}">
>
> Anyone else seeing this? Thoughts?Are you running on SVN trunk? If so, it's possible that you're seeing the effects of #13275 [1]. This is a major regression that was introduced recently to solve a different problem (#12945, which was in turn a fix for #12072). This problem is on the 1.2 critical list, so it needs to be fixed before 1.2 is released. [1] http://code.djangoproject.com/ticket/13275 > Maybe unrelated, but I also noticed that after I updated, I had to > change this: > > {% url bio-members_full type="user",page="1" %} > > to this: > > {% url bio-members_full type='user',page=1 %}" > > (switch to single quotes in the kwargs to pass a string literal) or I > got a template syntax error. This sounds like you may have found an additional regression case caused by the same chain of tickets. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
