Re: django 1.1 performance versus django 1.2 performance

Is there a way to identify which queries use cloning?

Is there a way rewrite those queries to avoid cloning overhead?

(If many of the queries use cloning then migrating one of my django
apps to 1.2.x may not be right for me.)

On Apr 25, 9:39 am, djeff <jafisc...@gmail.com> wrote:
> Russ,
>
> Thanks for the response.  You have confirmed what I'm seeing in the profile
> dump.  The cloning of a queryset is expensive and it is more expensive in
> 1.2 than with 1.1.  I really appreciate the feedback.  
>
> Jeff Fischer

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.