#22608: migrations slow (due to double working?)
-------------------------------------+-------------------------------------
Reporter: davids | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version:
Component: Migrations | 1.7-beta-2
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 andrewgodwin):
I suspect there is definitely some possible reuse, but when I tried some
optimisations in that area before it got very hard to debug (as the bugs
are side-effects of one thing affecting something else called four
migrations later, for example).
I suspect we could at least cache the project states for each migration,
if not start doing incremental renders (i.e. starting with the previous
cached state not from zero) to make things faster (basically, bring in
some memoization/dynamic programming). I just didn't have the time or
energy to do that during the main release cycle.
--
Ticket URL: <https://code.djangoproject.com/ticket/22608#comment:9>
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.f4b182744c5e85c5e21d524c98fac942%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
