On 27 heinä, 18:58, Jeremy Dunck <jdu...@gmail.com> wrote: > Can I get a review of the branch? 25% performance improvement of > Model.__init__ in stock django seems worth landing. :)
I did some work to add new benchmarks to djangobench. In my tests the speedup for the init hooks approach was nearly 60% when both pre/post init signals were in use in the project. Currently this happens when there are at least one ImageField and one GenericForeignKey used in the project. The test is fetching 500 objects from DB by the .iterator() method. We should do something to this issue. If the init hooks approach is the way to go needs to be decided. The caching of signal receivers gives the same speedup. Some more info in ticket #18627. - Anssi PS: for another possible nice speedup see ticket https://code.djangoproject.com/ticket/16759 which is about removing the use of __deepcopy__ from queryset cloning. There is potential for major speedups using that approach. Just one example: model.save() +50% speedup. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
