#22608: Migrations optimizer slow (due to double working?)
--------------------------------------+------------------------------------
Reporter: David S | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Ramiro Morales):
This might be of interest to the OP and people which contributed to this
discussion particularly those which have posted reports of of their big
Django projects with many migrations:
There is more work on this migrations efficiency front:
* Ticket: #29243
* Pull request at GitHub: https://github.com/django/django/pull/9804
* Post to the django-dev mailing list asking for test of the proposed
changes (includes a profiling script): https://groups.google.com/d/msg
/django-developers/PT86wX-oHKo/ZNRxt_E8BwAJ
--
Ticket URL: <https://code.djangoproject.com/ticket/22608#comment:24>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.3a5aa6bff428968a5afd4211f9228f17%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
