We have a very big Django project with > 100 apps and > 300 models.
We had some massive issues with Django 1.8 and migrations, which would take forever and just take all the computer memory after a while.
Now with Django 1.9 things improved, however we are again back with some extremely bad performances and massive memory usages (up to 8GB of RAM for example), sometimes just to run ONE single migration.
It's not even entirely deterministic though sometimes killing the process and doing it again just works.
I'm attaching the profile graph (done wtith gprof2dot) from running "./manage migrate" and one thing that clearly looks bad is that *render* for example is called 44355 times, which is definitively not normal.
Any idea about about what we can do about this and what could be the problem?
I have the impression that it's related with the amount of models and how they are interconnected, and mabye some caching would avoid all this extra computation.
Noone else has similar issues?
Thanks
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5b67eccf-d48f-4926-86ec-4bd2a8427dcb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment